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/auto-approve.md

@@ -40,9 +40,9 @@ UI's "auto-accept permissions" toggle (browser-local, not the project
 > fix this table. `merge-pr` is excluded from default/preset `stages` arrays
 > (not structurally blocked; explicitly adding it is not recommended).
 > Legacy stage retirement (12 → 5): the phase-3 retirement ruling doc
-> (Tier-2 reference, reachable via the ticket backend).
+> (instance detail (in the consuming instance)).
 
-Config shape: `"auto_approve": { "stages": ["review-code", "verify"], "stageless": false }` — `stages` empty (`[]`) = all manual; `stageless: true` also auto-approves questions called without a stage. Absent block defaults to `{ stages: ["review-code", "verify", "audit-process"], stageless: false }`; the removed `enabled` field migrates on load (mapping: Tier-2 reference page `rules/auto-approve-detail`). Presets (`safe`/`full`/`off`/`show`): same reference page — `full` never includes `merge-pr`.
+Config shape: `"auto_approve": { "stages": ["review-code", "verify"], "stageless": false }` — `stages` empty (`[]`) = all manual; `stageless: true` also auto-approves questions called without a stage. Absent block defaults to `{ stages: ["review-code", "verify", "audit-process"], stageless: false }`; the removed `enabled` field migrates on load (mapping: instance detail page `rules/auto-approve-detail`). Presets (`safe`/`full`/`off`/`show`): same reference page — `full` never includes `merge-pr`.
 
 ### Stage matching behavior
 
@@ -55,7 +55,7 @@ Config shape: `"auto_approve": { "stages": ["review-code", "verify"], "stageless
 Check logic: the harness 内建的问询与自动批准判定模块
 (resolveAutoApproveDecision).
 
-### Live-gate degradation chain ([org-internal #3531])
+### Live-gate degradation chain ([TT-3531])
 
 An auto-approved question is NOT consumed instantly: L1 — a live human
 watching the session (SSE declaration / fresh presence ping) answers within
@@ -73,7 +73,7 @@ before the gate runs (iron law).
 
 ### Mandatory destructive list (业务决策类问询强制清单)
 
-Origin: [org-internal #3223] — a stage whitelist auto-answered two
+Origin: [TT-3223] — a stage whitelist auto-answered two
 irreversible production data changes because nothing marked them
 `destructive`. A stage whitelist grants "execution gates may proceed
 uninterrupted"; it must NEVER grant "business decisions may be
@@ -87,8 +87,7 @@ is never a substitute for human confirmation of these categories.**
 1. **Merge / release landing** — merging a PR to main, cutting a tag or
    release, deploying/promoting to production (server-side auto-merge is a
    human-configured policy robot, never agent self-answer latitude; kill
-   switch: the auto-merge-low-risk runbook, Tier-2 reference via the ticket
-   backend).
+   switch: the auto-merge-low-risk runbook, instance detail (in the consuming instance)).
 2. **Production database writes** — upsert/update/delete against production
    data stores, production data migrations, live-data backfills.
 3. **Billing / plan changes** — plan or tier migration, pricing/concurrency