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/rules/issue-cross-linking.md

@@ -14,7 +14,7 @@ regression-test follow-up, or any parent/child breakdown — the issues MUST be
 cross-linked:
 
 - **Parent issue**: after creating all children, update the parent body so its
-  task list references each child by `#<number>` (e.g. `- [ ] [org-internal #1556] — [P0] ...`).
+  task list references each child by `#<number>` (e.g. `- [ ] [TT-1556] — [P0] ...`).
   The ticket backend renders these as clickable links and auto-generates a
   back-reference on each child's timeline.
 - **Child issue**: its body MUST contain a `## 父级 / Parent` section referencing
@@ -25,7 +25,7 @@ cross-linked:
 ### Issue ↔ Tier-2 artifact (pipeline traceability)
 
 When a production skill (`analyze-dag`, publishing the `{epic-slug}/dag`
-artifact; historically the pre-[org-internal #3072] producer skills) publishes
+artifact; historically the pre-[TT-3072] producer skills) publishes
 an artifact to the Tier-2 artifact library, the link to the source issue is
 only **half-built** — the library's index page links forward to the issue,
 but the issue has no link back to the library. A stakeholder opening the
@@ -44,7 +44,7 @@ After publishing, the skill MUST complete the reverse link on the source issue:
   reads the 工件索引 comment and fetches every CORE row's 位置 (shared
   read-patterns doc Pattern 6), instead of hard-coded library paths. Skills'
   re-read instructions therefore point at the index.
-- **Archive-at-close（归档动作, [org-internal #1929]/[org-internal #1928]）** — issue 关闭即归档；Tier-2 工件库无独立
+- **Archive-at-close（归档动作, [TT-1929]/[TT-1928]）** — issue 关闭即归档；Tier-2 工件库无独立
   生命周期。`ARCHIVE` is not just a per-row re-read priority: at issue close the
   whole index is marked archived by the closing agent (Verifier at `verify`
   Phase 5.6 on the primary path; otherwise the Orchestrator / last-role that
@@ -56,11 +56,11 @@ After publishing, the skill MUST complete the reverse link on the source issue:
 - **Sync the issue's checklist** per the issue-checklist-sync rule for the
   matching exit point (live: the DAG-freeze sync point after `review-dag`
   PASS; the legacy requirements-exit / design-exit / plan-exit points were
-  retired with their skills, [org-internal #3072] phase 3).
+  retired with their skills, [TT-3072] phase 3).
 - Skip if no source issue exists (no `Closes #N` / `Fixes #N` / roadmap chunk
   mapping ties this slug to an issue).
 
-**Size/S & Size/M exception ([org-internal #1832]) — RETIRED (2026-08-21, [org-internal #3072]
+**Size/S & Size/M exception ([TT-1832]) — RETIRED (2026-08-21, [TT-3072]
 phase 3)**: retired with the legacy producer skills and the `sizing:` block.
 Historical indexes pointing at in-issue artifacts (`位置 = #comment-{id}`)
 remain valid, readable locations; new artifacts publish where their live