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/style_profile.mjs

@@ -53,7 +53,13 @@ export function profile(raw) {
   for (const s of sents) {
     if (/(습니다|았습니다|었습니다)[.!]?$/.test(s)) kinds.add('습니다');
     if (/입니다[.!]?$/.test(s)) kinds.add('입니다');
-    if (/(했다|이다|였다|된다|한다)[.!]?$/.test(s)) kinds.add('한다');
+    // 한다체 안에도 어미는 여럿이다. 한 덩어리로 세면 잘 쓴 한다체 글이 1점을 받고,
+    // 점수를 올릴 길이 물음·청유밖에 남지 않아 없던 화자가 생긴다. 실제로 그렇게 됐다.
+    if (/(한다|된다|만든다|넘긴다|받는다)[.!]?$/.test(s)) kinds.add('한다');
+    if (/(했다|였다|됐다|되었다|았다|었다)[.!]?$/.test(s)) kinds.add('했다');
+    if (/(아니다|없다|같다|다르다|이다)[.!]?$/.test(s)) kinds.add('이다');
+    if (/(못한다|않는다|않았다|못했다)[.!]?$/.test(s)) kinds.add('부정');
+    if (/(뿐이다|때문이다|까지다|것이다)[.!]?$/.test(s)) kinds.add('설명');
     if (/(겠습니다|보겠습니다)[.!]?$/.test(s)) kinds.add('겠습니다');
     if (/\?$/.test(s)) kinds.add('물음');
     if (/(봅시다|보자|맙시다|주세요)[.!]?$/.test(s)) kinds.add('청유');