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>

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-feed-visibility-query-pattern.md

@@ -3,7 +3,8 @@ id: 635fcedd-d402-4297-bcf3-9fcdf4200d28
 kind: REFERENCE
 slug: feed-visibility-query-pattern
 title: Feed Visibility Query Pattern
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/635fcedd-d402-4297-bcf3-9fcdf4200d28/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-fetch-strategy-selection.md

@@ -3,7 +3,8 @@ id: db99cbc5-9123-4599-b368-39ff3170e81d
 kind: REFERENCE
 slug: fetch-strategy-selection
 title: Fetch Join · Batch · Projection 선택 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/db99cbc5-9123-4599-b368-39ff3170e81d/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-fetch-type-vs-fetch-strategy.md

@@ -3,7 +3,8 @@ id: 51095f6e-2cc8-439c-8648-065033614215
 kind: REFERENCE
 slug: fetch-type-vs-fetch-strategy
 title: Fetch Type과 Fetch Strategy 구분
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/51095f6e-2cc8-439c-8648-065033614215/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-keyset-pagination-design.md

@@ -3,7 +3,8 @@ id: 06788903-3dfa-4f70-b159-f1224384fd0b
 kind: REFERENCE
 slug: keyset-pagination-design
 title: Keyset Pagination 설계 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/06788903-3dfa-4f70-b159-f1224384fd0b/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-nplus1-quantitative-diagnosis.md

@@ -3,7 +3,8 @@ id: b0b55ac9-c0a3-4c01-ba84-0aa478923ace
 kind: REFERENCE
 slug: nplus1-quantitative-diagnosis
 title: JPA N+1 정량 진단 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/b0b55ac9-c0a3-4c01-ba84-0aa478923ace/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-postgresql-query-plan-measurement.md

@@ -3,7 +3,8 @@ id: e8c2e9ea-cd87-46f8-9469-849dbd433d86
 kind: REFERENCE
 slug: postgresql-query-plan-measurement
 title: PostgreSQL Query Plan 측정 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/e8c2e9ea-cd87-46f8-9469-849dbd433d86/edit"

docs/n+1liner/tech-log-studio/jpa-feed-query-performance/reference/reference-top-n-per-group-selection.md

@@ -3,7 +3,8 @@ id: bf5f2462-0e94-4723-bdc8-f7dd709b2dbb
 kind: REFERENCE
 slug: top-n-per-group-selection
 title: Top-N-per-group 선택 기준
-topic: JPA 피드 조회 성능
+topic: jpa-feed-query-performance
+topicName: JPA 피드 조회 성능
 project: Liner N + 1문제
 status: 게시 전
 studio: "https://hyeonworks.com/studio/documents/bf5f2462-0e94-4723-bdc8-f7dd709b2dbb/edit"