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/tech-log-studio/_meta/editorial-backlog.md

@@ -0,0 +1,65 @@
+# 사람이 읽고 정해야 남는 것
+
+자료가 뒷받침하는 것은 다 채웠다. 아래는 자료에 없어서 쓰면 지어내는 것이 된다.
+하나를 끝내면 이 파일에서 지운다.
+
+## 관계가 비어 있다
+
+`root-tree.md` 는 949개 노드 중 374개에만 관계를 적었다. 나머지 575개 중 204개는 트리가
+적은 규칙 — 「근거 사건은 같은 `source` 의 finding 이 소유한다」 — 으로 채웠다. 남은 것은
+같은 분석 리프에 짝이 될 기록이 없는 경우다.
+
+Studio 는 Decision 만 관계를 필수로 요구한다. 비어도 게시된다. 다만 관계 없는 기록은 다른
+기록에서 도달할 수 없다.
+
+- case 125건
+- concept 239건
+- reference 5건
+- question 2건
+
+## Question 에 가정·제약이 없다
+
+이 칸은 확인하지 않고 전제한 것을 적는 자리다. 원본이 적지 않았으므로 지어내지 않는다.
+그 질문을 다시 읽고 무엇을 전제했는지 정해야 채워진다.
+
+- 가정 없음 14건
+  - tech-log-studio/contract-domain-and-bounds/question/openquestion-messaging-claim-check-f05.md
+  - tech-log-studio/declaration-and-document-drift/question/openquestion-messaging-inbox-jdbc-postgresql-f04.md
+  - tech-log-studio/drift-direction/question/openquestion-widen-doc-contract-assertions.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-core-api-f01.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-core-api-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-kafka-share-experimental-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-policy-f02.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-reliability-api-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-schema-json-f03.md
+  - tech-log-studio/schema-and-data-contracts/question/openquestion-messaging-cloudevents-f04.md
+  - tech-log-studio/schema-and-data-contracts/question/openquestion-messaging-schema-protobuf-f03.md
+  - tech-log-studio/security-policy-enforcement/question/openquestion-messaging-security-f03.md
+  - tech-log-studio/transport-and-provider-semantics/question/openquestion-messaging-observability-f03.md
+  - tech-log-studio/transport-and-provider-semantics/question/openquestion-messaging-spring-cloud-stream-bridge-f02.md
+- 제약 없음 14건
+  - tech-log-studio/contract-domain-and-bounds/question/openquestion-messaging-claim-check-f05.md
+  - tech-log-studio/declaration-and-document-drift/question/openquestion-messaging-inbox-jdbc-postgresql-f04.md
+  - tech-log-studio/drift-direction/question/openquestion-widen-doc-contract-assertions.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-core-api-f01.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-core-api-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-kafka-share-experimental-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-policy-f02.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-reliability-api-f03.md
+  - tech-log-studio/runtime-reachability-and-composition/question/openquestion-messaging-schema-json-f03.md
+  - tech-log-studio/schema-and-data-contracts/question/openquestion-messaging-cloudevents-f04.md
+  - tech-log-studio/schema-and-data-contracts/question/openquestion-messaging-schema-protobuf-f03.md
+  - tech-log-studio/security-policy-enforcement/question/openquestion-messaging-security-f03.md
+  - tech-log-studio/transport-and-provider-semantics/question/openquestion-messaging-observability-f03.md
+  - tech-log-studio/transport-and-provider-semantics/question/openquestion-messaging-spring-cloud-stream-bridge-f02.md
+- 선택지 없음 1건
+  - tech-log-studio/drift-direction/question/openquestion-widen-doc-contract-assertions.md
+
+## 평문 칸에 백틱이 있다
+
+본문을 뺀 모든 칸은 평문이라 백틱이 글자 그대로 보인다. 368개 칸이 그렇다. 지우면 되지만
+식별자를 어떻게 드러낼지는 칸마다 다르므로 한 번에 훑고 정한다.
+
+```bash
+grep -rn '^## \(문제\|결론\|검증 환경\|재현 조건\|목적\|규칙\)' -A5 tech-log-studio/*/*/*.md | grep '`'
+```