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/headless-session-ops/reference/ticket-recipe.md

@@ -1,4 +1,4 @@
-> Extracted from headless-session-ops/SKILL.md (Launch a session for a specific ticket (#N)) — moved verbatim 2026-08-26, ticket [org-internal #3480].
+> Extracted from headless-session-ops/SKILL.md (Launch a session for a specific ticket (#N)) — moved verbatim 2026-08-26, ticket [TT-3480].
 
 ## Launch a session for a specific ticket (#N)
 
@@ -7,13 +7,13 @@ work a tracked issue. Compose the seed prompt **from the issue itself** so the
 new session starts with real context, and launch it on **the current session's
 model**.
 
-0. **Owner check (MANDATORY pre-step, [org-internal #1803]).** Before creating anything,
+0. **Owner check (MANDATORY pre-step, [TT-1803]).** Before creating anything,
    verify no other live session already owns this ticket or code area —
-   duplicate ownership is how [org-internal #1744]/[org-internal #1753] collided. The check spans four
+   duplicate ownership is how [TT-1744]/[TT-1753] collided. The check spans four
    data sources; any live claim → **ABORT the launch and report the
    conflict**.
 
-   **Mechanized ([org-internal #3667])**: `bash script/session-conflicts.sh <N>` runs the
+   **Mechanized ([TT-3667])**: `bash script/session-conflicts.sh <N>` runs the
    session-title scan (a), the branch scan (d), and the open-PR check (c)
    in one read-only pass (exit 4 = conflict, `--json` for a machine
    summary); the assignee/claim check (b) is `claim.sh`'s compare-and-swap
@@ -23,7 +23,7 @@ model**.
    **a. Session-title scan (live session check).** The listing endpoint
    returns at most `limit` (default 100) sessions — on busy repos (300+ live
    sessions in one directory) that silently truncates and the scan misses
-   owners ([org-internal #3190]). Non-range listing responses carry `X-Total-Count` (full
+   owners ([TT-3190]). Non-range listing responses carry `X-Total-Count` (full
    filter population, untruncated) and `X-Has-More: true` (only when the
    page is truncated). Scan procedure: fetch page 1, and when
    `X-Has-More: true` is present re-fetch once with `limit=$TOTAL` — treat
@@ -57,7 +57,7 @@ model**.
      the launch and report the conflict** (issue comment naming the owning
      session id). Do not launch a second session for the same ticket.
 
-   **b. Assignee / claim check ([org-internal #2297]).** Read the issue via
+   **b. Assignee / claim check ([TT-2297]).** Read the issue via
    `工单 API（见 TERMINOLOGY）get(owner, repo, index: N)` (or `GET /api/v1/repos/$OWNER/$REPO/issues/$N`):
    - If `assignee` is set and is **not** the launching agent → **ABORT** and
      report (the ticket is already claimed).
@@ -68,7 +68,7 @@ model**.
    `GET <gitea-base-url>/api/v1/repos/issues/search?q="#N"&type=pulls&state=open`
    (API source) — and **ABORT** if an open PR already covers the ticket.
 
-   **d. Remote branch check ([org-internal #2297]).** A local branch is invisible to other
+   **d. Remote branch check ([TT-2297]).** A local branch is invisible to other
    sessions — check the remote too:
    `git ls-remote origin 'workflow/*'` and scan for a branch tail covering `#N`.
    Also check the repo side locally: `git worktree list` +
@@ -76,7 +76,7 @@ model**.
 
    - A stale hit (session idle for hours / clearly abandoned) → do NOT
      hand-post a takeover comment (retired admin workaround — unauditable);
-     dead-claim takeover is mechanized ([org-internal #3668]): `bash script/claim.sh
+     dead-claim takeover is mechanized ([TT-3668]): `bash script/claim.sh
      takeover <ticket> <branch> --session-id <id>`. It enforces the
      evidence gate (branch ABSENT on origin AND (session 404 OR comment at
      least CLAIM_TAKEOVER_STALE_DAYS old)) and exits 10 when the evidence
@@ -87,13 +87,13 @@ model**.
      §"Dead-claim takeover" (claim.sh header is normative).
      The runtime counterpart of this check is `core/rules/session-scope-guard.md`
      ("One task, one owner"), injected into every session's prompt.
-   - **Backend hard guard ([org-internal #1989]):** `POST /session` hard-rejects duplicate-ticket
-     session creation with HTTP 400. The backend guard is **on by default ([org-internal #2350])**;
+   - **Backend hard guard ([TT-1989]):** `POST /session` hard-rejects duplicate-ticket
+     session creation with HTTP 400. The backend guard is **on by default ([TT-2350])**;
      set `enabled: false` in config to opt out. It fails open ONLY on defect
      paths (DB / config errors), never as a configured disable. The front-end
      soft check above is now backed by this backend hard check for defense in
      depth.
-   - **Claim-first ([org-internal #2297]).** Claiming a ticket is one atomic 3-step action:
+   - **Claim-first ([TT-2297]).** Claiming a ticket is one atomic 3-step action:
      (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 (`git push -u origin workflow/...`). The claim is valid ONLY when all
@@ -101,7 +101,7 @@ model**.
      session until all three steps are done (see
      `core/rules/session-scope-guard.md` §"Claim-first"). If a collision HAS
      already happened, follow `rules/ownership-collision-runbook` (wiki, L2 on-demand).
-   - **Provisioning after claim ([org-internal #3642]) is ONE command** — claim + worktree +
+   - **Provisioning after claim ([TT-3642]) is ONE command** — claim + worktree +
      Tier-1 runs scaffold:
      `bash script/claim-provision.sh <N> workflow/<branch>` (runs claim.sh with
      exit codes passed through, attaches the session worktree to the claimed
@@ -123,7 +123,7 @@ model**.
    - restate the **goal** in one sentence;
    - list the **constraints** and **acceptance criteria**;
    - cite every **wiki artifact path** / related issue referenced in the body
-     (e.g. `{epic-slug}/dag`, `{epic-slug}/dag-nodes/{node-id}`, `[org-internal #1691]`);
+     (e.g. `{epic-slug}/dag`, `{epic-slug}/dag-nodes/{node-id}`, `[TT-1691]`);
    - tell the new agent to follow the right pipeline skill for the work type
      (implement / bugfix / design / …).
      Write it to a file (handles newlines):
@@ -141,16 +141,16 @@ your change — classify (pre-existing/flaky), file a BF/FT issue per
 core/rules/session-scope-guard.md, and continue this task. Do NOT fix
 unrelated failing tests in place.
 
-## 完成回报协议 (mandatory, [org-internal #2374])
+## 完成回报协议 (mandatory, [TT-2374])
 
 完成、阻塞、或移交时，向编排会话回报：
   POST <BASE>/session/<LAUNCHER_SID>/prompt_async?directory=<DIR>
-  （编排目录未知时可用全局路由 POST <BASE>/prompt_async，body 携 sessionID，[org-internal #4307]）
+  （编排目录未知时可用全局路由 POST <BASE>/prompt_async，body 携 sessionID，[TT-4307]）
   body: {"agent":"builder","model":{...},"parts":[{"type":"text","text":"<report>"}]}
 <report>: [#N] [<node-or-slug>] status=done|blocked|handoff branch=<ref> [pr=#<PR>] verify=<changed+typecheck> risk=<high|low> summary=<one line>
 约束：worker 只推分支不开 PR（PR 由编排串行开）；交付推送前 test:changed+typecheck 须绿。若再遇配额/用量上限错误，立即回报 status=blocked reason=quota-exhausted summary=<provider 与重置提示>（branch=<ref> 必带）后停止，勿自行换模型重试。
 回报失败（非 2xx / 连接拒绝）→ 在本 issue（或父 Epic）发同内容评论兜底。
-决策边界（[org-internal #2378]）：遇方向性决策点 → status=blocked 回报，勿调 question。
+决策边界（[TT-2378]）：遇方向性决策点 → status=blocked 回报，勿调 question。
 EOF
    ```
 
@@ -179,4 +179,4 @@ EOF
 
 6. **Add the completion-report block to the seed prompt** (see next section) so
    the worker reports back when it finishes or blocks — without it, this
-   orchestrator has no push channel and must poll forever ([org-internal #2374]).
+   orchestrator has no push channel and must poll forever ([TT-2374]).