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)

2026-09-25 00:09:37 +08:00
parent d6567b1842
commit 88204a90c8
74 changed files with 1417 additions and 1358 deletions
@@ -232,7 +232,7 @@ review findings not actionable upstream]`.
   archive-at-close; (b) the committed archive bundles
   `<runs-root>/archive/{slug}.json`, where per-review round counts are
   reconstructed from the documented `reviews/{stage}/round{N}/` layout in
-   `index.artifacts[].path` ([org-internal #2591] — the archive source is what makes M3
+   `index.artifacts[].path` ([TT-2591] — the archive source is what makes M3
   durable instead of structurally emptying as runs close). Available once
   any run has closed.
   - Rework fraction: 🟢 <15% / 🟡 15–30% / 🔴 >30%.
@@ -245,7 +245,7 @@ or upstream design unclear]`.
   - 🟢 cache_read/input > 10:1 / 🟡 3–10:1 / 🔴 < 3:1.
   - < 3:1 → `[SIGNAL: cache hit <3:1 — context re-read, code-graph-first
 not followed]`.
-   - **Compact frequency ([org-internal #2601] pilot data)**: report the token-telemetry
+   - **Compact frequency ([TT-2601] pilot data)**: report the token-telemetry
     "Compactor Activity" line (compactor messages/tokens in window) and the
     zero-compact share of short runs (bugfix / DAG task) — the capacity-driven compaction
     pilot metrics. A rising zero-compact share with NO late-stage
@@ -259,7 +259,7 @@ not followed]`.
   - < 1:1 → `[SIGNAL: explore/execute <1:1 — workers doing explorers' job,
 exploration skipped or under-delegated]`.

-### 2.8 Gate defect-escape analysis (single metric, [org-internal #3061])
+### 2.8 Gate defect-escape analysis (single metric, [TT-3061])

 Gates earn their cost by what they CATCH, and the honest test is what slips
 past them: a gate that runs clean while the same defect resurfaces downstream
@@ -297,7 +297,7 @@ status` CLI or commit-status inspection. Final reports at
   downstream sources for an escape.
 3. Tally per `gate_id`: `clean_runs`, `escapes`, `escape_rate`.
 4. Reading (thresholds are this skill's own policy — the `gate_trim:` block
-   they once deferred to was retired 2026-08-21, [org-internal #3072] phase 3; nothing
+   they once deferred to was retired 2026-08-21, [TT-3072] phase 3; nothing
   trims gates anymore, so the trim-candidate branch below is gone):
   - `escape_rate ≥ 0.3` → the gate is
     **UNDER-POWERED**: route the escape causes into §2.9 pre-flight
@@ -305,12 +305,12 @@ status` CLI or commit-status inspection. Final reports at
     propose trimming it.
   - `escape_rate < 0.3` → healthy; report the numbers, no further verdict.

-**DAG single-gate exclusion ([org-internal #2267])**: `review-dag` is structurally
+**DAG single-gate exclusion ([TT-2267])**: `review-dag` is structurally
 non-trimmable (`dag.route.single_gate.never_trim: true` — self-contained in
 the `dag:` block); `verify` and `merge-pr` were `never_trim` in the retired
 `gate_trim` block and stay untouchable by convention.

-**keep_gates exclusion (TD-390, [org-internal #3061]) — RETIRED with gate_trim**: the
+**keep_gates exclusion (TD-390, [TT-3061]) — RETIRED with gate_trim**: the
 rule that a trim candidate's gate must not be a member of the target route's
 `keep_gates` guarded a landing field (`sizing.tiers.*.additional_skip`)
 that no longer exists. Historical record: wiki `rules/gate-trim`.
@@ -331,10 +331,10 @@ runs for a gate → report the raw numbers with
 - [NOTE: insufficient sample for gate X] where clean runs < 5.
 - UNDER-POWERED gates (escape_rate ≥ 0.3) feed §2.9 pre-flight — never a
  unilateral trim: the only exit is a furlough entry in
-  `<instance-root>/gate-ledger.yaml` (evidence + reopen condition, [org-internal #3607]).
+  `<instance-root>/gate-ledger.yaml` (evidence + reopen condition, [TT-3607]).
 ```

-### 2.9 Pre-flight defect-prevention analysis ([org-internal #2599])
+### 2.9 Pre-flight defect-prevention analysis ([TT-2599])

 First-round FAIL/WARN findings are the pipeline's cost multiplier: every
 multi-round review pays for them twice (review round + revision round).
@@ -348,13 +348,13 @@ code.
 reports for the cycle's tickets (`{slug}/reviews/{stage}/final/report` —
 round-1 findings with severity FAIL/WARN, their dimension codes, and the
 finding text for root-cause categorization) + the source issues'
-`Kind/*` labels. For DAG-routed Epics ([org-internal #2905] 方案 3), two further
+`Kind/*` labels. For DAG-routed Epics ([TT-2905] 方案 3), two further
 read-only sources feed the `REQ × late-discovery` root cause (step 1):
 (a) **DAG oversize-signal events** — `node_split` / registry-row additions
 recorded on the Epic's issue timeline / `## DAG 状态` whose trigger is a NEW
 requirement rather than a refactor; (b) **demo-period feedback** —
 stakeholder comments naming functionality the frozen DAG never covered. For browser-evidence
-cycles ([org-internal #4499], contract `browser-evidence-4486/shared/evidence-ref-v1` §3), a
+cycles ([TT-4499], contract `browser-evidence-4486/shared/evidence-ref-v1` §3), a
 third read-only
 source: (c) **browser session rows** — per browser-debug session
 `{session_id, outcome: evidence-captured | env-unavailable | replay-failed,
@@ -373,7 +373,7 @@ Rows are currently Task-DAG cycle products by default (the helper's
 Bug- or Feature-cycle session to its own landing slot). The replay
 success-rate baseline (N-03 BENCH) is exposed as a consumable metric — a SEEDED CONVENTION (fixture-authored outcomes, channel health),
 NOT a live-browser trend baseline. Mechanical helper:
-`<harness-package>/scripts/browser-retro-tally.ts`. Boundary rules ([org-internal #4499]
+`<harness-package>/scripts/browser-retro-tally.ts`. Boundary rules ([TT-4499]
 AC-3): out-of-enum or empty categories fall into an explicit `other` bucket
 with provenance (recorded, never silently swallowed, never a crash); rows
 missing replay/attribution fields yield structured errors in the tally
@@ -395,10 +395,10 @@ late-discovery` — 冻结后才被发现的需求 (a requirement that surfaced
   oversize signal or demo comment — count it from sources (a)/(b) above,
   not only from review findings.
 2. Tally per **route-class** — `Bug`, `Feature-DAG`, `Epic-DAG-route`,
-   `Task-DAG` (Kind/Feature routes to the DAG pipeline since [org-internal #3061] Phase 2 /
+   `Task-DAG` (Kind/Feature routes to the DAG pipeline since [TT-3061] Phase 2 /
   TD-388 — `Feature-legacy` survives only as a historical bucket for tickets
   closed before 2026-08-20; the Size dimension is retired from retro keying,
-   [org-internal #3061]: DAG-routed tickets derive depth instead of carrying `Size/*`
+   [TT-3061]: DAG-routed tickets derive depth instead of carrying `Size/*`
   (spec-06), and `Kind/Bug` carries no ladder). First-round hit count
   and distinct-ticket count per cause per class.
 3. A cause is a **pre-flight candidate** when ALL hold (thresholds from
@@ -408,7 +408,7 @@ late-discovery` — 冻结后才被发现的需求 (a requirement that surfaced
     A qualifying `Epic × DAG-route` cause (e.g. `REQ × late-discovery`) lands
     on `<instance-root>/workflow-routing.yaml` `dag.route.preflight` — NOT
     `routes.Kind/Epic.preflight` (legacy-roadmap-era landing; the legacy route
-     was archived [org-internal #3072] phase 3) ([org-internal #2905] 方案 3). The analyze-dag skill reads
+     was archived [TT-3072] phase 3) ([TT-2905] 方案 3). The analyze-dag skill reads
     `dag.route.preflight` before decomposition.
 4. Aging: for causes ALREADY landed in `routes.{Kind}.preflight` or
   `dag.route.preflight`, count
@@ -423,7 +423,7 @@ Sample-sufficiency guard mirrors 2.8: zero qualifying tickets → emit

 | route-class    | Cause (checklist-qualified dim × root-cause) | 1st-round hits | tickets                     | qualify?                         |
 | -------------- | ------------------------------------------- | -------------- | --------------------------- | -------------------------------- |
-| Bug            | code-review.md COR × unhandled-null         | 5              | 4 ([org-internal #2400] [org-internal #2429] [org-internal #2471] [org-internal #2488]) | ✅ PROPOSE                       |
+| Bug            | code-review.md COR × unhandled-null         | 5              | 4 ([TT-2400] [TT-2429] [TT-2471] [TT-2488]) | ✅ PROPOSE                       |
 | Bug            | code-review.md STY × wrong-import-order     | 6              | 2                           | ⛔ tickets <3                    |
 | Feature-DAG    | code-review.md TST × missing-boundary-test  | 3              | 3                           | ⛔ hits <5                       |
 | Epic-DAG-route | REQ × late-discovery        | 5              | 3 (#27xx #28xx #29xx)       | ✅ PROPOSE → dag.route.preflight |
@@ -433,7 +433,7 @@ Sample-sufficiency guard mirrors 2.8: zero qualifying tickets → emit
 - Landed-item aging: `cor-unhandled-null clean streak 5 ≥ aging 5` → REMOVAL row.
 ```

-### 2.10 Derived-ticket health ([org-internal #3061])
+### 2.10 Derived-ticket health ([TT-3061])

 Derived tickets (TD promotions, BF umbrellas, FT tickets) are the pipeline's
 exhaust. Unmanaged they accumulate into flush cycles (2026-08 evidence: 122
@@ -477,7 +477,7 @@ this probe checks whether the system DIGESTS what it records:
 - rows marked [COLD] this cycle: {list or "none"}
 ```

-### 2.11 Threshold calibration tally ([org-internal #3380])
+### 2.11 Threshold calibration tally ([TT-3380])

 Process prose constants (round caps, D1–D4 thresholds, preflight knobs,
 escape-rate cutoffs, quotas — full index:
@@ -665,7 +665,7 @@ Each item MUST specify:
 - Action items that modify SKILLs or templates are applied immediately (the
  Retrospective Lead can edit `<instance-root>/` files).
 - Action items MUST NOT be vague ("try harder", "be more careful").
- **Layering question** (injection-budget ruling item 3, [org-internal #3547]): every action
+- **Layering question** (injection-budget ruling item 3, [TT-3547]): every action
  item that encodes a lesson as a process constraint MUST answer **"which
  layer carries this lesson?"** — options in ascending per-turn cost, pick
  the cheapest that actually enforces it:
@@ -682,7 +682,7 @@ Each item MUST specify:
     corpus — do not casually re-grow it; the rule-GC report in that same check
     flags aging L1 rules for L2 retirement).

-**TRIM PROPOSAL rows — RETIRED ([org-internal #3072] phase 3, 2026-08-21)**: the
+**TRIM PROPOSAL rows — RETIRED ([TT-3072] phase 3, 2026-08-21)**: the
 gate-trim landing machinery (`gate_trim.action` →
 `sizing.tiers.{Size}.additional_skip` / `routes.{Kind}.skip` /
 `auto_approve.stages`) was removed with the `gate_trim:` and `sizing:`
@@ -691,12 +691,12 @@ Gate health findings flow exclusively through §2.8's escape-rate verdict
 (UNDER-POWERED → §2.9 pre-flight) and ordinary action items. Historical
 spec: wiki `rules/gate-trim` (L2).

-**PRE-FLIGHT PROPOSAL rows** (from Phase 2.9 defect-prevention, [org-internal #2599]): format
+**PRE-FLIGHT PROPOSAL rows** (from Phase 2.9 defect-prevention, [TT-2599]): format
 the What cell as
 `Add pre-flight '{id}' to {Kind} ({hits} first-round FAIL/WARN hits, {tickets} tickets — {evidence})`
 and the Where cell as
 `<instance-root>/workflow-routing.yaml` `routes.{Kind}.preflight` — or, for causes
-keyed `Epic × DAG-route` (e.g. `REQ × late-discovery`, [org-internal #2905] 方案 3),
+keyed `Epic × DAG-route` (e.g. `REQ × late-discovery`, [TT-2905] 方案 3),
 `<instance-root>/workflow-routing.yaml` `dag.route.preflight` (consumed by
 analyze-dag before decomposition).
 Aging removal rows: `Remove pre-flight '{id}' from {Kind} (clean streak {N} ≥ aging threshold)`.