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/_shared/review-pipeline-phases.md

@@ -9,14 +9,14 @@ parameters and reference this doc rather than duplicating the shared mechanics.
 legitimately uses "auditor"/"Re-audit" terminology. All generic descriptions
 use `{REVIEWER_OR_AUDITOR}`.
 
-**Output model — two findings sinks** ([org-internal #1988] Tier 1 migration): raw per-dimension
+**Output model — two findings sinks** ([TT-1988] Tier 1 migration): raw per-dimension
 reviewer findings have ONE of two sinks, chosen per skill. The **synthesis**
 (human gate) and **commit status** are ALWAYS Tier 2 (Gitea) regardless of the
 findings sink.
 
 | Sink | Skills | Reviewer writes findings to | Synthesizer reads findings from |
 |---|---|---|---|
-| `tier1-local` (migrated) | `review-code`, `review-artifact` (live targets: review-dag, audit-process; the roadmap/design-space/plan targets were archived 2026-08-21, [org-internal #3072] phase 3) | `<runs-root>/{slug}/reviews/{stage}/round{N}/findings-{DIMENSION_CODE}.json` (validated by `core/schemas/reviewer-output.schema.json`) | the local finding files (no Gitea call) |
+| `tier1-local` (migrated) | `review-code`, `review-artifact` (live targets: review-dag, audit-process; the roadmap/design-space/plan targets were archived 2026-08-21, [TT-3072] phase 3) | `<runs-root>/{slug}/reviews/{stage}/round{N}/findings-{DIMENSION_CODE}.json` (validated by `core/schemas/reviewer-output.schema.json`) | the local finding files (no Gitea call) |
 | `tier2-comment` (fallback) | _(none — all targets migrated)_ | Gitea PR/issue comment via `工单评论 API（见 TERMINOLOGY）` (Pattern 5) | `工单评论 API（见 TERMINOLOGY）` (Pattern 3) |
 
 Migration complete — every review/audit skill now outputs `tier1-local`; the
@@ -61,7 +61,7 @@ in `_shared/gitea-write-patterns.md`.
    `stage` = `{REVIEW_TYPE}`, `produced_by` = `Orchestrator`, `schema` = the
    review-status `$id`).
 
-1. **Tool-availability probe** (defense-in-depth, [org-internal #2115] RC1 / [org-internal #2126]). Before
+1. **Tool-availability probe** (defense-in-depth, [TT-2115] RC1 / [TT-2126]). Before
    dispatching any {REVIEWER_OR_AUDITOR}, verify reviewers will be able to read
    wiki artifacts (requirements / design / plan / prior-review reports). A
    reviewer that cannot read its inputs aborts or hallucinates — catch this ONCE
@@ -74,7 +74,7 @@ in `_shared/gitea-write-patterns.md`.
       reachable; anything else — timeout, connection refused, 5xx — is
       unreachable). If reachable → continue to step 2.
     - **Fallback path** (when REST is unreachable, e.g. a
-      cross-repo scenario [org-internal #2115]): verify the **local wiki clone** at
+      cross-repo scenario [TT-2115]): verify the **local wiki clone** at
      `<wiki-clone-root>/{repo}-wiki/` is readable —
      `glob(pattern="*.md", path="<wiki-clone-root>/{repo}-wiki/")`. If the clone
      is readable → continue to step 2; reviewers use the local clone (see
@@ -266,7 +266,7 @@ Otherwise:
    - The {REVISION_ROLE} MUST NOT receive the full text of all findings inline —
      use finding-file path / comment references only to avoid context explosion.
    - Convergence status: blockers/majors remaining vs. previous round.
-   - **Revision survival ([org-internal #2601]) — primary path**: the task tool's completion
+   - **Revision survival ([TT-2601]) — primary path**: the task tool's completion
      output includes a `task_id`; passing it back resumes the SAME
      {REVISION_ROLE} subagent session instead of creating a fresh one. Round 1:
      persist the returned `task_id` with the round's working-notes entry (it
@@ -322,24 +322,24 @@ After the {REVISION_ROLE} completes revision:
   `core/schemas/review-status.schema.json`).
 - `review-code` skill: **2** default / **3** high-risk (a BLOCKER survived a
   round, or the diff touches a frozen cross-session contract) —
-  `<instance-root>/workflow-routing.yaml` `review.max_rounds` ([org-internal #3567], process-diet
+  `<instance-root>/workflow-routing.yaml` `review.max_rounds` ([TT-3567], process-diet
   P0b). At budget without convergence: STOP, register the remaining
   BLOCKER/MAJOR findings as TD registry rows, then compute the verdict
   with the shared three-tier ladder (`core/schemas/synthesis.schema.json`
   `overall_verdict` + `core/skills/_shared/review-orchestrator-rules.md`
   rule 3): FAIL if any BLOCKER or FAIL dimension remains, else WARN,
-  PASS only if every remaining dimension is PASS ([org-internal #4786]:
+  PASS only if every remaining dimension is PASS ([TT-4786]:
   the prior binary "else PASS" wording silently upgraded WARN-eligible
   outcomes to PASS; a PASS round has already stopped at the convergence
   table above, so the residual tail lands WARN or FAIL). The debt is
   carried by those TD registry rows
   (see `review-code/SKILL.md` Phase D). This
-  supersedes the 2026-08-25 [org-internal #3380] calibration (p50=2, p95=5, n=66): the runs
+  supersedes the 2026-08-25 [TT-3380] calibration (p50=2, p95=5, n=66): the runs
   past round 3 are the marathon tail this budget exists to cut; their residue
   flows to the TD registry instead of reviewer rounds. Ledger:
   `docs/workflow-refactor/thresholds-ledger.md`.
 
-Rationale for `review-artifact` = 3 (evaluated in [org-internal #1969], replacing the prior blanket
+Rationale for `review-artifact` = 3 (evaluated in [TT-1969], replacing the prior blanket
 default of 5): (1) the Round-3 Escalation Guardrail below already detects
 non-convergence at the start of round 3; (2) the INFO-disposition rule below
 removes spurious WARN rounds previously caused by non-blocking INFO findings;
@@ -350,8 +350,8 @@ reaches round 4 — its round budget is 2/3, see the binding above.)
 
 **Provisional, not empirically validated**: the four safeguards make `review-artifact`=3
 defensible, but it has no fresh run-data yet. Treat it as a hypothesis to
-confirm via the retrospective signal ([org-internal #1834]; gate-trim's landing machinery was
-retired, [org-internal #3072] phase 3 — the check is observational, not a trim proposal): if
+confirm via the retrospective signal ([TT-1834]; gate-trim's landing machinery was
+retired, [TT-3072] phase 3 — the check is observational, not a trim proposal): if
 live `review-artifact` runs frequently hit round 3 still improving yet are
 forced to stop at WARN/FAIL, bump it back to 4.
 
@@ -379,8 +379,8 @@ block convergence and NEVER drive a reviser round.
 **Round-3 Escalation Guardrail** (applies to the `review-artifact` skill's
 live targets — the process audit target AND the review-dag single-gate
 target; the roadmap / design / plan targets were archived 2026-08-21,
-[org-internal #3072] phase 3). `review-code` does NOT use this guardrail; it uses its round
-budget ([org-internal #3567], see the `{MAX_ROUNDS}` binding above).
+[TT-3072] phase 3). `review-code` does NOT use this guardrail; it uses its round
+budget ([TT-3567], see the `{MAX_ROUNDS}` binding above).
 
 At the start of round 3, if the combined blocker+major count is still >50% of
 round 1's count, STOP the loop and surface to the user:
@@ -391,7 +391,7 @@ round 1's count, STOP the loop and surface to the user:
 > (a) Return to upstream — for the `process` audit target, escalate to the
 > octopus maintainer for a process-level redesign (the legacy producer skills
 > `roadmap` / `requirements-elicitation` / `design` / `plan-iterations` were
-> archived 2026-08-21, [org-internal #3072] phase 3 — `<instance-root>/archive/`), then restart this
+> archived 2026-08-21, [TT-3072] phase 3 — `<instance-root>/archive/`), then restart this
 > review at round 1.
 > (b) Continue iterating — accept that more rounds may be needed (capped by
 > `{MAX_ROUNDS}`).
@@ -406,7 +406,7 @@ review and escalate to a human, or (b) continue into round 4 — via the
 `question` tool. The guard means "escalate with a choice", NOT "force-stop".
 The choice is UNCONDITIONAL at the round-3→4 transition — instance skills may
 narrow when an escalation *variant* (e.g. a design-level decision) fires, but
-never narrow the choice gate itself. The call MUST be optionized ([org-internal #3378]):
+never narrow the choice gate itself. The call MUST be optionized ([TT-3378]):
 two options — `Stop & escalate to a human` (first, when recommended) /
 `Continue into round 4` — with `stage` set to the running skill's stage so
 auto-approval applies in autonomous mode; free-text asking is a spec
@@ -414,12 +414,12 @@ violation.
 Instance: review-dag D4 option-b (`review-artifact/SKILL.md` §"Round-3
 Escalation Guardrail interaction") — the sole live instance, its D4 round cap
 (≤4) being the only budget that reaches round 4 (`review-code` is capped 2/3,
-[org-internal #3567]).
-Rationale (retro 2026-08-21 / [org-internal #3050]): unattended late-round loops drift into
+[TT-3567]).
+Rationale (retro 2026-08-21 / [TT-3050]): unattended late-round loops drift into
 review marathons — the choice forces the design-level stall to surface to a
 human at round 4 instead of round 6.
 
-**Efficiency optimization**: From round 2 onward ([org-internal #2598]), only spawn
+**Efficiency optimization**: From round 2 onward ([TT-2598]), only spawn
 {REVIEWER_OR_AUDITOR}s for dimensions that had FAIL, WARN, or UNRESOLVED in
 the previous round. Every 2 rounds, run a full {DIMENSION_COUNT}-reviewer
 sweep to catch regressions. From round 2 onward reviewer input is also
@@ -486,7 +486,7 @@ not the round-1 full set.
     `REQUEST_REVIEW` registration to be recorded, and only THEN ask the human
    to approve. Approving before the reviewer is registered produces
    `official: false` on the approval — the gate treats the PR as unapproved
-   and the approval must be re-done. ([org-internal #1931]: audit R2→R3 re-loop + re-approve,
+   and the approval must be re-done. ([TT-1931]: audit R2→R3 re-loop + re-approve,
    ~30min wasted on exactly this ordering.)
 
 4. Present the final report to the user and obtain approval via the `question`