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/writing-tech-log-records/references/tech-log-tree-contract.md

@@ -73,7 +73,7 @@ section it names exists, and the diagram stage cannot translate the anchor into
 
 ## Topics
 
-Each Topic has `topic` (its key), `title`, **`readerQuestion`**, and `kinds` with the five
+Each Topic has `topic` (its key), `title`, **`readerQuestion`**, and `kinds` with the six
 record kinds.
 
 ```json
@@ -81,13 +81,13 @@ record kinds.
   "topic": "oauth-oidc-auth-boundary",
   "title": "OAuth 자격증명과 세션의 보관 경계",
   "readerQuestion": "자격증명과 세션을 누가 보관하고, 누가 API 요청을 만들며, 보호 자원은 무엇을 신뢰하는가?",
-  "kinds": { "case": [], "concept": [], "reference": [], "question": [], "decision": [] }
+  "kinds": { "case": [], "concept": [], "setup": [], "reference": [], "question": [], "decision": [] }
 }
 ```
 
 Every node in the Topic must help answer the reader question. Two Topics do not share a
 question; one Topic does not need two. Empty kinds are allowed — do not manufacture nodes
-to fill all five.
+to fill all six.
 
 ## Candidates
 
@@ -178,6 +178,26 @@ be stale.
 A Concept exists because a Case, Decision, or Question needs it to be understood. Absence,
 call-counts, unwired subsystems, analysis scope, and coverage ledgers are not Concepts.
 
+### Setup
+
+`slug` · `readiness` · `source` · `classification` · `pinned-versions` · `relations`.
+
+Setup is the one kind that does not report a finished result. It is a procedure a reader
+runs on their own machine, so `pinned-versions` states the versions the procedure was
+established on — the same job `basis-version` does for a Concept, except there is more than
+one of them. There is no verification date for this kind.
+
+A Setup node also needs a project. `SETUP` and `PROJECT_DECISION` are the two kinds Studio
+refuses to save without one; a Topic is optional, and a Setup with no Topic reads as that
+project's shared configuration.
+
+`verify-tech-log-tree.py` checks this kind like the others: `REQUIRED_FIELDS["setup"]` names
+the six fields above and `GENERATABLE["setup"]` is `READY`. The kind list those tables are
+keyed on lives in `techlog.KINDS`, which also decides which `<topic>/<kind>/` folders
+`build-tech-log-tree.py` scans. Add a kind in one place and the tables that key off it go
+quiet rather than failing — a kind missing from `REQUIRED_FIELDS` is not an error, it is a
+node nobody asks anything of.
+
 ### Reference
 
 `slug` · `readiness` · `source` · `classification` · `scope` · `exceptions` · `relations`.