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: e1e0e2a0-c6b6-45bf-be42-f697ba5e2fff
 kind: QUESTION
 slug: cardinality-estimate-after-analyze
 title: ANALYZE 이후 Cardinality Estimate는 어떻게 달라지는가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e1e0e2a0-c6b6-45bf-be42-f697ba5e2fff/edit"
@@ -3,7 +3,8 @@ id: 6cbe963f-86f8-4df6-be5a-900712970d01
 kind: QUESTION
 slug: concurrency-stability
 title: 실제 동시 트래픽에서도 이 구조가 안정적인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/6cbe963f-86f8-4df6-be5a-900712970d01/edit"
@@ -3,7 +3,8 @@ id: 5159c415-232d-424a-970a-b0db52746767
 kind: QUESTION
 slug: isolate-round-trip-and-row-volume
 title: Round Trip과 Row Volume을 독립 측정할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/5159c415-232d-424a-970a-b0db52746767/edit"
@@ -3,7 +3,8 @@ id: b099ca65-bf9f-4d61-814c-74722453fa3c
 kind: QUESTION
 slug: nullable-first-highlighted-at
 title: Highlight 없는 FeedItem을 허용할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/b099ca65-bf9f-4d61-814c-74722453fa3c/edit"
@@ -3,7 +3,8 @@ id: 5088ce14-b096-41d3-abba-64b7afb48bb9
 kind: QUESTION
 slug: promote-feed-visible-to-cqrs
 title: feed_visible을 Production CQRS로 승격할 것인가
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/5088ce14-b096-41d3-abba-64b7afb48bb9/edit"