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/project-kickoff/SKILL.md

@@ -8,7 +8,7 @@ description: >
   project scaffolding. Do not use for application-level configuration —
   this skill covers the octopus project lifecycle, not user application code.
 triggers:
-  # High-discrimination phrases only ([org-internal #4525]): bare "setup"/"init"/"配置" fire
+  # High-discrimination phrases only ([TT-4525]): bare "setup"/"init"/"配置" fire
   # on any configuration mention, and the skill gate folds the previous
   # assistant turn on approval turns — one stray "配置" in a reply re-fires
   # the gate every turn. Keep triggers to phrases that name THIS workflow;
@@ -36,7 +36,7 @@ This skill activates when the user's text matches any of the trigger keywords:
 - `project setup` — asking how to set up a project in octopus
 - `项目初始化` / `项目配置` — asking how to initialize or configure an octopus project (Chinese)
 
-Generic "setup"/"init"/"配置" mentions are deliberately NOT triggers ([org-internal #4525]): they collide with everyday configuration talk, and the hard skill gate folds the previous assistant turn into its match text on approval turns — a passing "或配置x: false" in a reply would re-fire the gate every turn. `/init` note: `/init` generates AGENTS.md via LLM; kickoff uses the managed template from `octopus setup` — the Builder distinguishes based on context.
+Generic "setup"/"init"/"配置" mentions are deliberately NOT triggers ([TT-4525]): they collide with everyday configuration talk, and the hard skill gate folds the previous assistant turn into its match text on approval turns — a passing "或配置x: false" in a reply would re-fire the gate every turn. `/init` note: `/init` generates AGENTS.md via LLM; kickoff uses the managed template from `octopus setup` — the Builder distinguishes based on context.
 
 Typical user intents include: encountering a readiness prompt at session start, wondering how to initialize a project, or wanting to understand the kickoff workflow steps.
 
@@ -74,14 +74,14 @@ The kickoff workflow runs in four automated steps:
    - [2/5] **Scaffold** — Creates the `<instance-root>/` skeleton (`core/skills/` directory + default `octopus.jsonc` template if absent); domain skills content arrives via the [5/5] overlay pull
    - [3/5] **Config stub + MCP wiring** — Writes the `mcp.codegraph` block into `octopus.jsonc`
    - [4/5] **Codegraph init** — Initializes and builds the per-project `.codegraph/` index
-   - [5/5] **Skills remote + overlay pull** — Opt-in semantics ([org-internal #4370]); branches by flags when no `overlay.remotes` entry is configured:
+   - [5/5] **Skills remote + overlay pull** — Opt-in semantics ([TT-4370]); branches by flags when no `overlay.remotes` entry is configured:
      - no flags (interactive run) — **safe default**: nothing is written; a remediation hint is printed (pass `--skills-remote`, or edit `overlay.remotes`), and the readiness skills item stays not-ready
      - `--yes` — legacy behavior kept: writes the default skills remote, then pulls domain skills content (`octopus skills pull` equivalent)
      - `--skills-remote <owner/repo>` (+ optional `--skills-remote-base-url <url>`) — writes the specified remote instead (ref `main`; base URL defaults to `<instance-base-url>`), then pulls from it
      - `overlay.remotes` already configured — the write is skipped (idempotent; an explicit `--skills-remote` is ignored with a warning)
 4. **Post-kickoff verification** — Run `octopus kickoff --check-only` again. After a `--yes` or `--skills-remote` run it reports all 5 items as ready; after a no-flag interactive run it reports 4 of 5 — the skills item stays not-ready until a remote is configured (`--skills-remote`, `--yes`, or a manual `overlay.remotes` edit + `octopus skills pull`).
 
-### First-ticket hint ([org-internal #3061])
+### First-ticket hint ([TT-3061])
 
 For a brand-new project still validating its concept, open the FIRST ticket as
 `Kind/MVP` — the interactive no-pipeline mode (decision log + debt register in