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

@@ -63,14 +63,14 @@ Run each check against the live project. Stop and report failures.
    - No new HIGH or CRITICAL CVEs block the release.
    - Pre-existing HIGH/CRITICAL CVEs do NOT block but **MUST be filed as
      tech-debt** before the release lands. File them in TWO TIERS (batching
-     rule, [org-internal #3846] — a single release audit once fanned out to 14 TDs → 14 PRs →
+     rule, [TT-3846] — a single release audit once fanned out to 14 TDs → 14 PRs →
      56-84 CI runs on a saturated runner pool): Tier A below is the general
      mechanical-change batching rule; Tier B and the escape hatch follow it.
 
 <a id="phase-1-tier-a"></a>
 ### Tier A — 通用机械变更并单规则 / Universal mechanical-change batching rule
 
-Origin [org-internal #3846] (audit-batch pilot, generalized in place): the rule covers ANY
+Origin [TT-3846] (audit-batch pilot, generalized in place): the rule covers ANY
 single-source fan-out of mechanical changes, not just dependency audits.
 Two source types today: (a) dependency bump audits; (b) docs 批量修订
 (batch docs revisions).
@@ -81,7 +81,7 @@ Two source types today: (a) dependency bump audits; (b) docs 批量修订
   source are filed as ONE batch issue + ONE batch PR — never N×issue +
   N×PR. The batch body keeps one row per item (per-CVE / per-doc mapping),
   so per-item traceability is unchanged; work the batch as a single PR.
-- **(a) Dependency bump audits** (the [org-internal #3846] origin case): advisories whose
+- **(a) Dependency bump audits** (the [TT-3846] origin case): advisories whose
   remediation is a plain version bump (lockfile-only diff, no semver-major
   jump, no overrides/catalog surgery, no API or adapter fallout) are filed
   together via REST `POST .../issues` with
@@ -132,7 +132,7 @@ Two source types today: (a) dependency bump audits; (b) docs 批量修订
   along the reported pairs (or land the overlapping member 1:1) and re-run
   per group; `4` merge conflict / `5` transport/git error → fall back to
   1:1 PRs for the whole batch.
-- **Preflight hedge ([org-internal #3846])**: run `bun install --dry-run` before opening
+- **Preflight hedge ([TT-3846])**: run `bun install --dry-run` before opening
   a dependency-batch PR — the resolver accepting the composed version set
   is a cheap pre-CI rejection of impossible bump combinations.
 
@@ -292,7 +292,7 @@ Write to root `CHANGELOG.md` (prepend section).
 > the goal is identical (turn the tag into downloadable assets).
 
 The CI publish pipeline (`.gitea/workflows/publish.yml`) was **retired by
-[org-internal #2003]** (138/138 historical runs cancelled; the pipeline sat unused for 35+
+[TT-2003]** (138/138 historical runs cancelled; the pipeline sat unused for 35+
 days). Releasing octopus is now a **manual local process**. All former CI
 steps live in repo scripts, runnable from a maintainer machine with the right
 credentials in the environment.
@@ -358,11 +358,11 @@ credentials in the environment.
 ### Notes
 
 - **Windows code-signing** is not provisioned (no Windows runner / Azure
-  Trusted Signing); the CLI ships unsigned, as before ([org-internal #252]).
+  Trusted Signing); the CLI ships unsigned, as before ([TT-252]).
 - **Rollback**: if a step fails mid-release, the draft release + tag can be
   deleted and re-run; every script above is idempotent or safely re-runnable.
 - If a future CI pipeline replaces this manual flow, update this section and
-  reference [org-internal #2003] for the retirement rationale.
+  reference [TT-2003] for the retirement rationale.
 
 ---