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/clean-architecture-backend-template/final/evidence/raw/a10-f004-pub-sub-bound.txt

@@ -0,0 +1,28 @@
+MAX_KEY_BYTES = 512
+
+[구성 요소의 상한] 토큰 64, 식별자 128, 슬롯 태그 128
+  namespace.prefix() 길이 : 194
+
+[채널] 구성 요소를 최대로 채운 렌더
+  PubSubChannel        렌더 388 바이트  여유 124
+  ShardedPubSubChannel 렌더 388 바이트  여유 124
+
+[키] 같은 규칙을 받은 조각들, 슬롯 태그 하나가 더 붙는다
+  태그 없음 -> 렌더 388 바이트
+  태그 있음 -> rendered key is 519 bytes and exceeds the configured 512
+
+[기본 이름공간] 설정 기본값 local:sample-service:shared
+  prefix 길이 : 27
+  채널 렌더   : 221 바이트
+  태그 붙인 키 : 352 바이트
+
+[패턴] 접미가 토큰 규칙을 받지 않는다 (이름공간은 위와 같은 최대치)
+  suffix 64   -> 생성됨, 렌더 259 바이트
+  suffix 317  -> 생성됨, 렌더 512 바이트
+  suffix 318  -> rendered key is 513 bytes and exceeds the configured 512
+
+[상한을 어디서 가져오는가]
+  RedisKeyRenderer : 생성자 인자 (1..512)
+  PubSubPattern    : RedisKeyRules.MAX_KEY_BYTES 상수
+  상한 256 렌더러에 키 -> rendered key is 388 bytes and exceeds the configured 256
+  같은 배포의 채널 388 바이트 -> 검사 없음