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/ticket-lifecycle.md

@@ -1,6 +1,6 @@
 > Core 中立版（Increment 2 改写）。术语对照见 core/adapters/TERMINOLOGY.md；本组织实例表述见 dogfood 对应文件。
 
-## Ticket Lifecycle — registry-first filing, claim-to-promote ([org-internal #3002] G1)
+## Ticket Lifecycle — registry-first filing, claim-to-promote ([TT-3002] G1)
 
 Bugs worth fixing start life as a **registry row**, not an independent ticket.
 This extends the two-tier-artifacts philosophy to the ticket queue: a
@@ -25,20 +25,20 @@ is how the 2026-08 backlog formed.)
   ```
 
 - **TD-NNN** is allocated at REGISTRATION via the ledger mutex
-  [org-internal #3322]: the 配额账本脚本 (`td-alloc` 形态, `bash <alloc-script>
+  [TT-3322]: the 配额账本脚本 (`td-alloc` 形态, `bash <alloc-script>
   <count> <source-slug> [--ticket N]`) takes a contiguous range from the TD
   allocation ledger (a standing tracker issue) — append-only `**td-alloc**`
   comments, earliest-comment-id wins on collision. **ANY allocation — manual
   included — must land a td-alloc comment on the ledger BEFORE the registry
   row is written** (script, tool API, or web UI). Hand-computed `max + 1`
   without a ledger comment is FORBIDDEN (parallel-session races,
-  [org-internal #3322]). The id is **reserved for life**: promotion reuses
+  [TT-3322]). The id is **reserved for life**: promotion reuses
   it, never renumbers. Run the alloc script's `--check` (reconciliation)
   when the last check predates this batch, and in retrospectives.
 - **De-duplication** queries the TD index (same-source rows) plus open
   promoted issues (cross-source); index matching replaces title-keyword
   matching (keyword dedup once produced 18 fragments from one source).
-- **Query-failure ruling ([org-internal #3383]: fail-open, visible)**: if the
+- **Query-failure ruling ([TT-3383]: fail-open, visible)**: if the
   dedup query itself errors (backend API failure — NOT "queried and found no
   match"), retry once; on second failure file anyway, marking the comment
   `dedup-unverified` for retro/reconciliation sweep. Fail-closed rejected:
@@ -63,7 +63,7 @@ source.
 ### PR 准入（pr-admission，TD-678）
 
 会话交付物 = 分支 + 报告；开 PR 属编排职权，按容量串行一次一张、双绿并入
-再开下一张（[org-internal #3864] 管合并出口、本节管 PR 入口）。交付推送前置
+再开下一张（[TT-3864] 管合并出口、本节管 PR 入口）。交付推送前置
 本地验证（`<test-cmd:changed>` + `<typecheck-cmd>` 绿；实例命令绑定见
 core/adapters/TERMINOLOGY.md）。编排不可达可自开，PR 正文标
 `uncoordinated`。细则与门控项：pipeline-gate 清单 PR 准入节。
@@ -75,7 +75,7 @@ occurrence: evidence (run, commit, failing output, failure rate) attaches as
 comments on the family's **umbrella ticket** (ticket-backend issue), keyed by
 failure signature (error signature + affected surface, not just
 `file::test-name` — one root-cause family may span several tests; precedents
-[org-internal #2585], [org-internal #2925]). Filing a new ticket when the
+[TT-2585], [TT-2925]). Filing a new ticket when the
 signature already matches an existing family (open or closed) is forbidden —
 attach evidence instead. A family umbrella is closed when its signature no
 longer reproduces.