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/a07-f002-normalize.txt

@@ -0,0 +1,47 @@
+# 계약이 적힌 두 곳
+  /**
+   * Accepts a case-insensitive canonical UUID string and returns the canonical 36-character
+   * lowercase form; {@code null} input returns {@code null}.
+   *
+   * @throws IllegalArgumentException on a malformed UUID
+   */
+  public static String normalize(String input) {
+    if (input == null) {
+      return null;
+    }
+    return UUID.fromString(input).toString();
+  }
+#   README
+- `normalize(String)` — **D3**: 대소문자 무관 canonical UUID 입력을 받아 canonical 36자 소문자
+  형태로 반환. 형식 오류 UUID 에는 `IllegalArgumentException`. `null` 입력은 `null` 반환.
+
+# 같은 파서를 쓰는 형제 메서드
+  public static UUID toUuid(String uuidString) {
+    return UUID.fromString(uuidString);
+  }
+
+# 명세의 거부 케이스
+24:    def "normalize 는 형식이 잘못된 UUID 를 거부한다"() {
+25-        when:
+26-        UuidCodec.normalize("not-a-uuid")
+27-
+28-        then:
+29-        thrown(IllegalArgumentException)
+30-    }
+#   명세 전체의 거부 단언 수 : 1
+
+# 같은 저장소의 UUID 스칼라는 그 계약을 코드로 지킨다
+      Pattern.compile(
+          "[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}");
+
+  public static UUID parse(String value) {
+    if (value == null || !CANONICAL.matcher(value).matches()) {
+      throw new CoercingParseValueException("invalid UUID");
+    }
+    try {
+      return UUID.fromString(value);
+#   그 관문을 지나는 곳
+    55:  public static UUID parse(String value) {
+    72:      return parse(text).toString();
+    90:        return parse(text);
+    99:        return parse(stringValue.getValue());