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/session-scope-guard.md

@@ -3,7 +3,7 @@
 ## Session Scope Guard (mandatory)
 
 > Enforcement layer: precheck-mechanized (injection-budget batch-2,
-> [org-internal #3667]) — pre-flight sources 1-3 below live in the repo's
+> [TT-3667]) — pre-flight sources 1-3 below live in the repo's
 > session-conflicts script, source 4 in the claim script's compare-and-swap.
 > This file is the normative definition, NOT part of any `agents_md`
 > injection whitelist since 2026-08-29 — do not re-add; the checks run at
@@ -11,8 +11,7 @@
 
 Standalone and ticket-seeded sessions run without a pipeline around them —
 no plan, no reviewer keeping them inside their work item. When such a
-session hits a test failure NOT caused by its own change ([org-internal
-[org-internal #1803]], via [org-internal #1753]/[[org-internal #1744]]), it tends to fix the foreign
+session hits a test failure NOT caused by its own change ([TT-1803], via [TT-1753]/[TT-1744]), it tends to fix the foreign
 failure in place (drifting off-task), and sessions seeded for the same issue
 collide on the same shared flaky test.
 
@@ -48,17 +47,17 @@ on ANY source → the ticket is already owned: ABORT (or, for a DEAD claim,
 take over via the mechanized channel below; otherwise coordinate on the
 issue), never silently start a second owner.
 
-**Mechanized ([org-internal #3667])**: the repo's session-conflicts script
+**Mechanized ([TT-3667])**: the repo's session-conflicts script
 (`<session-conflicts-cmd> <ticket>`) scans sources 1-3 in one read-only pass
 (exit 4 = conflict, matching the claim script; source 1 fail-opens visibly
-when the app API is down — the backend hard guard [org-internal #1989]
+when the app API is down — the backend hard guard [TT-1989]
 backstops); source 4 IS the claim script's compare-and-swap. Dead-claim
 takeover is mechanized in the claim script (see below); manual recipes:
 the headless-session-ops skill's ticket-recipe reference §0.
 
-**Dead-claim takeover ([org-internal #3668]).** A claim whose session is
+**Dead-claim takeover ([TT-3668]).** A claim whose session is
 gone (404 on the app API) and whose branch was never pushed is a DEAD claim
-— the [org-internal #3419] shape. Do NOT hand-edit the dead claim comment
+— the [TT-3419] shape. Do NOT hand-edit the dead claim comment
 (the retired admin workaround — unauditable); run the claim script's
 takeover subcommand (`<claim-takeover-cmd> <ticket> <branch> --session-id
 <id>`) instead. Evidence rule (the claim script's header is normative): a
@@ -77,8 +76,7 @@ ticket-driven work is to claim the ticket — one atomic action of THREE
 steps, valid ONLY when all complete: (1) set the issue assignee to the
 working account, (2) post a claim comment naming the workflow branch and
 session id, (3) push the workflow branch to remote (even an empty commit —
-a purely local branch is invisible to other sessions, [org-internal
-[org-internal #2280]/[org-internal #2282]]). Use the repo's claim wrappers (staged-transaction claim
+a purely local branch is invisible to other sessions, [TT-2280]/[TT-2282]). Use the repo's claim wrappers (staged-transaction claim
 script; exit codes and CAS semantics in its header; non-zero = NOT claimed)
 and the provision wrapper (adds the worktree + Tier-1 runs scaffold). The
 manual 3-step is the fallback where the scripts are unavailable, same
@@ -88,7 +86,7 @@ re-verification.
 branch's recent commits for `#<ticket>` — surfacing an equivalent
 implementation already on main *before* the merge rejection.
 
-**Merge-time review gate ([org-internal #2345]).** `pipeline/review-code` is
+**Merge-time review gate ([TT-2345]).** `pipeline/review-code` is
 a required status: merge needs it green OR the route-based exemption
 (Kind/* close routes skip review-code — posted by the repo's
 review-gate-exemption script). Read the commit-status endpoint for the PR
@@ -102,7 +100,7 @@ your chunk before starting.
 
 Two sessions owning the same issue or code area is never faster — it is the
 exact collision this rule prevents. If a collision HAS happened, follow the
-failure-path playbook at the ownership-collision runbook (Tier-2 reference
+failure-path playbook at the ownership-collision runbook (instance detail page
 page, reachable via the ticket backend).
 
 ### Scope