docs(keycloak-session-store): remake all 28 diagrams through the techviz pipeline

The originating repository's SVGs were drawn by hand and every one of them
put a title, a subtitle and an explanation band inside the canvas. This
repository forbids both, so they could not be carried over — the whole set
was rebuilt through the skill's pipeline instead.

Each diagram went through prepare, references, prompt, a VizSpec 1.1 citing
document line ranges, lint, and render. All 28 pass lint and produce the
same eight formats the existing keycloak project has. Sentences moved out of
the canvas into <desc> and the paragraph beside each figure; the drawings
carry names only.

Two lint rules did real work rather than formatting work:

  edge-through-node                  caught arrows crossing an unrelated
                                     node and implying an adjacency that
                                     does not exist — four diagrams had to
                                     be restructured, not just relaid out
  evidence-outside-prepared-context  caught a diagram citing another
                                     section; its anchor moved from B-0 to
                                     B-1 so all three sections it draws on
                                     are inside the prepared context

lab-topology also had to change profile: its context offers a different
candidate set, and query-fanout with shard roles is what the section
actually shows — one entry point spreading to two Keycloak nodes.

The document now carries all 28 inline, one per claim that needed one, and
the section recording what was still missing is updated: the diagram gap is
closed, Studio records remain.

verify-pipeline.py passes. audit-records.py reports no issues.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.agents/skills/rewriting-technical-prose-naturally/scripts/check_prose.mjs

@@ -134,6 +134,24 @@ function positiveChecks(text, lines, docMode, rulesMode) {
     if (/까요\??$/.test(st) || /\?$/.test(st)) kinds.add('물음');
     if (/(봅시다|보자|맙시다|주세요)[.!]?$/.test(st)) kinds.add('청유');
   }
+  // 3-1. 문장을 「~것이 ~이다」로 닫는 버릇
+  //
+  // 사건을 서술하는 대신 그것이 무엇인지 이름 붙이고 끝낸다. 「확인한 자리다」·「~하는 실례다」·
+  // 「~라는 점이다」. 참고 여섯 편은 이 어미를 통틀어 세 번 쓴다(17386 1 · 22396 2). 한 문서에
+  // 이것이 몰려 있으면 사건을 적지 않고 분류만 한 것이다.
+  const namingEnd = [...text.matchAll(/[가-힣)\]`]\s*(자리|실례|경우|출발점|사실|이유|점|것|뿐|셈)(이다|입니다)[.!]?(?=\s|$)/g)];
+  const alwaysBad = namingEnd.filter((m) => /(자리|실례|출발점)/.test(m[1]));
+  for (const m of alwaysBad) {
+    out.push({ id: 'naming-instead-of-telling', sev: ERR, index: m.index,
+      excerpt: text.slice(Math.max(0, m.index - 30), m.index + m[0].length),
+      msg: '무슨 일이 있었는지 적는 대신 그것이 무엇인지 이름 붙이고 닫았습니다. 그 자리에서 실제로 일어나는 일을 동사로 적으세요.' });
+  }
+  if (!rulesMode && namingEnd.length >= 4) {
+    out.push({ id: 'naming-instead-of-telling', sev: ERR,
+      msg: `문장을 「~것이 ~이다」로 닫은 자리가 ${namingEnd.length}곳입니다(참고 여섯 편은 글 하나에 0~2회). `
+         + `분류하지 말고 그 자리에서 무엇이 일어나는지 적으세요.` });
+  }
+
   if (!rulesMode && sentences.length >= 8 && kinds.size <= 1) {
     out.push({ id: 'monotone-endings', sev: ERR,
       msg: `문장 ${sentences.length}개가 모두 같은 종결어미입니다. 문장이 하는 일이 다르면 어미도 달라집니다 — `