docs(keycloak-session-store): import the session-storage lab as a new project

The keycloak project ended with four open questions that design could not settle. A two-VM lab was built to answer them by measurement, and this is that material: 26 experiments, 125 raw command outputs, 22 browser captures. Follows the import procedure in README.md. source/ the originating repository verbatim — 78 documents, 28 SVGs, 8 manifests, plus .source-revision recording the commit final/ the SSOT document.md 729 lines written from the 29 experiment documents, not concatenated: what was predicted, what was measured, and where the measurement itself was wrong evidence/raw 125 outputs, flattened to <experiment>__<file> because the originals collided (01-baseline.txt appeared three times) and the audit only globs the top level evidence/meta one per raw file; command and exitCode are null and the README says why rather than inventing them evidence/browser 22 captures assets/ three diagrams through techviz .techviz/ their VizSpecs A separate project rather than an addition to keycloak: the B-layer answers that project's four questions, but the A, C and D layers are about cluster failure, SSO and operations, and one document.md should hold one subject. The four question records there can point here through 관계. Recorded rather than papered over: only three of the 28 diagrams were remade. The repository forbids hand-drawn SVG and forbids titles inside the canvas; all 28 originals carry both, so converting them is redrawing, not reformatting. They stay in source/ and the gap is written into the document. verify-pipeline.py passes. audit-records.py reports no issues. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-04 22:51:59 +09:00
parent 43bccd08a8
commit b2963105a8
5017 changed files with 372751 additions and 4943 deletions
@@ -3,7 +3,8 @@ id: c1158754-e3d2-47b8-bb41-81787c0ca84b
 kind: CASE
 slug: collection-fetch-join-in-memory-paging
 title: Collection Fetch Join Pagination의 In-memory Paging
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/c1158754-e3d2-47b8-bb41-81787c0ca84b/edit"
@@ -3,7 +3,8 @@ id: 32d0be7d-d88e-4760-8d91-35d3a233a99a
 kind: CASE
 slug: eager-toone-nplus1-without-access
 title: Fetch 타입이 아니라 조회 방식이 만든 ToOne N+1
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/32d0be7d-d88e-4760-8d91-35d3a233a99a/edit"
@@ -3,7 +3,8 @@ id: 7ed75172-fd56-42bf-956a-8f9fc1cca235
 kind: CASE
 slug: fetch-join-multibag-and-row-explosion
 title: Fetch Join으로 N+1을 해결하다 만난 MultiBag과 행 폭증
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/7ed75172-fd56-42bf-956a-8f9fc1cca235/edit"
@@ -3,7 +3,8 @@ id: 4c9c3b90-bc89-4300-9334-088ea95d37d8
 kind: CASE
 slug: projection-row-over-fetch
 title: Projection 이후에도 1,509행을 읽은 Row Over-fetch
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/4c9c3b90-bc89-4300-9334-088ea95d37d8/edit"
@@ -3,7 +3,8 @@ id: e6715e81-6dbd-4287-8e19-946c334f38fb
 kind: CASE
 slug: visibility-or-breaks-keyset-index
 title: Visibility OR이 Keyset Index를 깨뜨린 문제
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e6715e81-6dbd-4287-8e19-946c334f38fb/edit"