chore: 이전 세션이 남긴 변경을 커밋한다

이번 파이프라인 작업과 무관하게 작업 트리에 남아 있던 것을 그대로 올린다.
사용자가 「전부 커밋」으로 정했고, 이번 작업과 섞이지 않게 커밋만 나눴다.

대부분은 clean-architecture-backend-template 의 그림 정본 재배치다 —
final/assets/diagrams/<이름>/ 에 있던 것이 CLAUDE.md 가 적은 배치인
final/assets/<이름>/ 로 옮겨졌고 .techviz/<이름>/ 이 함께 들어왔다.
삽입 줄의 대부분(3.15M)이 그 .techviz context.json 이다.

그 밖에 ca-tmpl·document-haness 의 정리, .claude/agents/ 열한 개,
writing-practitioner-guides 스킬, .playwright-mcp 세션 산출물,
scripts/check-ssot-facts.py 와 그 시험이 들어 있다.

이 커밋의 내용은 내가 만든 것이 아니라 이전 세션이 남긴 것이고 검증하지 않았다.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.agents/skills/deriving-tech-log-root-tree/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: deriving-tech-log-root-tree
-description: Use when a completed or substantially completed docs project analysis must be decomposed into grounded Tech Log Topics and candidate Case, Concept, Reference, Open Question, and Decision records.
+description: Use when a completed or substantially completed docs project analysis must be decomposed into grounded Tech Log Topics and candidate Case, Concept, Setup, Reference, Open Question, and Decision records.
 metadata:
   version: "1.0.0"
   language: "ko-KR"
@@ -77,7 +77,9 @@ They do not hold candidates, and in a folded project they are gone.
 4. Pick **Decisions** from the explicit-decision section (§10).
 5. Pick **Questions** from the unresolved section (§11).
 6. Only now add the **Concepts** those four need in order to be understood. Concept is
-   derived backwards from the records that require it, never by sweeping headings.
+   derived backwards from the records that require it, never by sweeping headings. Add the
+   **Setups** the analysis actually supports in the same pass — the section below says which
+   ones those are.
 7. Give every candidate a disposition — `references/candidate-disposition.md` — and set
    `dispositionReview` to `CONFIRMED` only for the ones a person actually re-read.
 8. Group `PROMOTE` candidates into Topics. Write one reader question per Topic.
@@ -89,6 +91,20 @@ They do not hold candidates, and in a folded project they are gone.
     `python3 scripts/verify-tech-log-tree.py <project>` — errors must be 0. Build fills
     `ssotSha256`; verify errors when it is absent, so verifying before building always fails.
 
+## When a Setup belongs in the tree
+
+Add a **Setup** where the analysis records the commands and configuration values that stand
+an environment up and someone other than the author has to run them.
+
+Its test is not the one the other five take. They ask whether a claim is worth publishing on
+its own; this one asks whether a reader would type these lines. A reproduction that only
+re-obtains one measurement stays inside that Case's `재현 조건` field, and a procedure nobody
+but the author would run is that Case's environment section.
+
+Setup nodes need a project. A Topic is optional, and a Setup without one reads as that
+project's shared configuration. Instead of a verification date it carries `pinned-versions`
+— the versions the procedure was established on.
+
 ## Three fields the verifier requires and this procedure does not otherwise name
 
 Write them by hand. `verify-tech-log-tree.py` counts each as an error when missing.
@@ -141,12 +157,19 @@ Do not create one Topic per source file or module. A directory is not a Topic.
 - **Open Question** — no answer yet, the design turns on the answer, and there is a next
   verification and a closing criterion.
 - **Decision** — the project actually chose a direction, with grounds and an accepted cost.
+- **Setup** — a procedure the reader runs to stand the environment up. Carries
+  `pinned-versions` instead of a verification date, and always belongs to a project.
 
-The independence test decides all five:
+The independence test decides the first five:
 
 > Delete this record and fold it into a related Case or Concept as one section. If
 > understanding, decisions, and reuse are unchanged, it is not an independent record.
 
+Setup does not answer that question, because folding a procedure into a Case is exactly what
+this kind exists to stop — the commands end up in a plain-text `검증 환경` field where they
+cannot be copied. Ask instead who runs it. If only the author ever will, it is that Case's
+environment, not a record.
+
 Branches may be empty. Symmetry is not a quality goal. Neither is volume — a large
 denominator justifies a long `final/document.md`, not a long tree.