v0.1.5: standalone-readability pass — delink --strip provenance mode ([TT-NNNN]), Tier-2 dangling refs neutralized, verify/review-code giant skills split into reference/ on-demand files; guards now runtime-neutral (bun|node)

core/skills/analyze-dag/SKILL.md

@@ -3,7 +3,7 @@ name: analyze-dag
 description: >
   Use ONLY when an Epic is routed to the DAG ticket pipeline (Kind/Epic or
   Kind/Feature — both resolve to analyze-dag via the routes table directly,
-  [org-internal #3072] phase 3 / [org-internal #3061] Phase 2). The
+  [TT-3072] phase 3 / [TT-3061] Phase 2). The
   Analyst decomposes the Epic into a single task-DAG artifact — merging
   roadmap+requirements+design+plan into one graph (nodes = acceptance
   criteria, edges = contracts, topology = plan).
@@ -31,7 +31,7 @@ role: Producer
 analyze-dag is the **entry skill** of the DAG ticket pipeline
 (`dag.route.entry.skill`, spec-07 §2). For a DAG-routed Epic
 (`Kind/Epic`, or `Kind/Feature` — both resolve here via the routes table
-directly, [org-internal #3072] phase 3 / [org-internal #3061] Phase 2 / TD-388 —
+directly, [TT-3072] phase 3 / [TT-3061] Phase 2 / TD-388 —
 including BACKFILL mode for MVP graduates and big-bug relabels), it
 **replaces** `roadmap` + `requirements-elicitation` + `design` +
 `plan-iterations` and produces **ONE artifact**: the task DAG, published as
@@ -66,12 +66,12 @@ a topological order (the plan), then publishes the single graph.
 | 设计主导 | 主要风险是一个有 ≥2 个可行选项的架构/平台决策，而非任务分解；需要先做一次探索 | 将开放问题转 `prototype`（THROWAWAY spike）或设计探索；决策记录后重入 |
 | 外部契约未决 | scope 依赖未决的外部契约（第三方 schema、上游 API 未定） | 按 External-System Rule（见下文）解析或围栏；不可拆的残余隔离后再重入 |
 
-**反向拦截（Kind/MVP 降级建议，[org-internal #3061]）**：一个 `Kind/Feature` 工单在分解预检中
+**反向拦截（Kind/MVP 降级建议，[TT-3061]）**：一个 `Kind/Feature` 工单在分解预检中
 暴露"概念未稳"（scope 仍在探索、成功标准未定、决策日志会推翻节点划分）时，
 正确出口不是硬分解，而是建议改标签 `Kind/MVP` 先行交互式验证——概念稳定后
 经 backfill 模式（见下文）带着决策日志重入。
 
-### Phase 0 需求澄清（disqualifier 的结构化扩展，[org-internal #3061]）
+### Phase 0 需求澄清（disqualifier 的结构化扩展，[TT-3061]）
 
 预检不止于"能否分解"，还须证明"需求已澄清到可分解"。两项强制检查：
 
@@ -217,7 +217,7 @@ Rules:
 - `refs_by` is derived from the REQMAP "every requirement ≥1 node" criterion
   (missing coverage = a requirement with no node).
 
-## Breadth Coverage — 类目覆盖矩阵 + 排除账本 ([org-internal #2905] 方案 1)
+## Breadth Coverage — 类目覆盖矩阵 + 排除账本 ([TT-2905] 方案 1)
 
 The four-stage fold that produced the single DAG artifact kept requirement
 **depth** (REQMAP three-path coverage + falsifiable AC) but dropped legacy
@@ -271,7 +271,7 @@ sub-page `{epic-slug}/dag-coverage` using the same mechanics as AC sinking
 frozen copy) — purely organizational, NOT an oversize signal, no
 re-derivation.
 
-### Breadth probe nodes (P2, [org-internal #2905] 方案 2)
+### Breadth probe nodes (P2, [TT-2905] 方案 2)
 
 When a 待确认 category is cheapest to resolve empirically, a **probe node**
 is a legal task node at the granularity floor:
@@ -306,12 +306,12 @@ is a legal task node at the granularity floor:
   冻结副本（新增需求必然改变节点集合或 `req_refs`；需要新节点时全额按
   node_split 建单传播）。
 
-### Data layer — read `dag.route.preflight` BEFORE decomposition ([org-internal #2905] 方案 3)
+### Data layer — read `dag.route.preflight` BEFORE decomposition ([TT-2905] 方案 3)
 
 Before starting decomposition, analyze-dag MUST read
 `<instance-root>/workflow-routing.yaml` `dag.route.preflight` and, when the list is
 non-empty, verify each item as a producer self-check (the same injection
-contract `implement` applies for `routes.{Kind}.preflight`, [org-internal #2599] — landed
+contract `implement` applies for `routes.{Kind}.preflight`, [TT-2599] — landed
 items carry their retro evidence in `evidence`):
 
 1. Read the `dag:` block's `route.preflight` array (live yaml, repo root).
@@ -407,7 +407,7 @@ external contract). This is what lets the REQMAP "需求覆盖" (requirement
 coverage) check mechanically verify that external-integration requirements map
 to nodes. (The `ARCH 1.1` system-context diagram is discarded only for
 process-infrastructure-type Epics; product Epics get this alternative rule
-instead.) [org-internal #2905]: this rule is the 外部系统集成 category of the breadth
+instead.) [TT-2905]: this rule is the 外部系统集成 category of the breadth
 coverage matrix held at its original strength — see Breadth Coverage above.
 
 ## Exec-Resource Configuration (spec-07 §4 — mechanical destination of folded checklist rows)
@@ -433,7 +433,7 @@ observe:
    `> DAG 工件状态: draft`.
 2. After the single-gate (`review-dag`) PASS, the **aggregator agent** (main
    session / Orchestrator — not analyze-dag) asks the freeze confirmation
-   question ([org-internal #3379]), then on confirmation flips the page to
+   question ([TT-3379]), then on confirmation flips the page to
    `> DAG 工件状态: frozen` and stamps version `v1`. The confirmation is an
    OPTIONIZED `question` call (stage `review-dag`, never `destructive` —
    freeze is a process gate, not a business decision): options
@@ -454,7 +454,7 @@ observe:
    the version stamp `vN → vN+1` (no re-confirmation — only the initial
    freeze gates on a decision).
 
-## Backfill Input Mode (Kind/MVP graduation & big-bug relabels, [org-internal #3061])
+## Backfill Input Mode (Kind/MVP graduation & big-bug relabels, [TT-3061])
 
 When a `Kind/MVP` ticket graduates (relabel → `Kind/Feature` → Step 0 → this
 skill), the DAG is derived from **what was actually built**, not from greenfield
@@ -500,4 +500,4 @@ decomposition:
 - `dag-pipeline/spec-06` — dag_metrics derivation + thresholds
 - `dag-pipeline/spec-07` — dag.route landing row (entry skill, skip set, single-gate) + §4 landing list
 - `dag-pipeline/spec-08` — DAG artifact lifecycle / version stamp
-- `<instance-root>/archive/skills/roadmap/SKILL.md` — legacy route (archived 2026-08-21, [org-internal #3072] phase 3; this skill replaces it for all Epics)
+- `<instance-root>/archive/skills/roadmap/SKILL.md` — legacy route (archived 2026-08-21, [TT-3072] phase 3; this skill replaces it for all Epics)