feat: 가상화 문서들 추가

.agents/skills/analyzing-codebase-for-tech-log/SKILL.md

@@ -11,7 +11,8 @@ Produce a highly detailed, source-traceable engineering analysis. This stage dis
 
 ## Required sequence
 
-1. **First read `<분석 대상 저장소>/analysis-queue.yaml`.** Before inspecting any project contents, apply `references/queue-contract.md`: reconcile newly discovered project directories, preserve queue order, and determine the single active project.
+0. **Fix the two roots before anything else.** `<분석 대상 저장소>` is the repository being analyzed — an absolute path outside this repository, given by the caller. `docs/<프로젝트>/` is inside *this* repository. Never write into the analyzed repository, and never read analysis state from it.
+1. **Read `<분석 대상 저장소>/analysis-queue.yaml` if it exists.** It exists only when several repositories are queued. Apply `references/queue-contract.md`: reconcile newly discovered project directories, preserve queue order, and determine the single active project. **If there is no queue, analyze the one repository the caller named and skip to step 3.** A missing queue is not a blocker — it means nothing is queued.
 2. If an `IN_PROGRESS` project exists, analyze only that project. If none exists, activate the first `PENDING` project in queue order. Never preempt an active project because a new project appeared.
 3. For the selected `<분석 대상 저장소>`, check the nearest `AGENTS.md` or equivalent repository instructions.
 4. Record Git revision and `git status` when Git is available. Never modify or reset user source as part of analysis.

.agents/skills/analyzing-codebase-for-tech-log/references/evidence-contract.md

@@ -2,7 +2,7 @@
 
 ## Primary evidence first
 
-Store command output, logs, generated query plans, benchmark results, browser observations, and other primary material under `docs/<프로젝트>/evidence/raw/` before creating presentation assets.
+Store command output, logs, generated query plans, benchmark results, browser observations, and other primary material under `docs/<프로젝트>/final/evidence/raw/` before creating presentation assets.
 
 ## Terminal evidence
 
@@ -15,7 +15,7 @@ For a command used as evidence, retain:
 - raw stdout/stderr;
 - source revision when relevant.
 
-Render terminal UI with `./tools/terminal-evidence/render_terminal.py`.
+Render terminal UI with `scripts/terminal-evidence/render_terminal.py`.
 
 The visual asset is explanatory. The raw evidence is the provenance.
 

.agents/skills/analyzing-codebase-for-tech-log/templates/analysis/00-project-overview.md

@@ -2,7 +2,7 @@
 
 ## 분석 기준 revision
 
-- repository: `/shared/codebase/<project>`
+- repository: `<분석 대상 저장소의 절대 경로>`
 - revision: `<git revision or non-git snapshot note>`
 
 ## Build and module map

.agents/skills/analyzing-codebase-for-tech-log/templates/state.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 2,
   "project": "<project>",
-  "codebasePath": "/shared/codebase/<project>",
+  "codebasePath": "<분석 대상 저장소의 절대 경로>",
   "gitRevision": null,
   "analysisStatus": "NOT_STARTED",
   "analysisCycle": 1,