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)

2026-09-25 00:09:37 +08:00
parent d6567b1842
commit 88204a90c8
74 changed files with 1417 additions and 1358 deletions
@@ -11,16 +11,16 @@ point and see exactly what is done, in progress, and deferred.

 | When | Who | What |
 |------|-----|------|
-| After the DAG artifact is frozen (`review-dag` PASS + freeze confirmation per `analyze-dag/SKILL.md` §Output & Lifecycle step 2, [org-internal #3379]) | Aggregator agent | Convert the source Epic's draft acceptance criteria into a formal checklist; annotate requirement-covered items `_(DAG frozen: {epic-slug}/dag v1)_` |
+| After the DAG artifact is frozen (`review-dag` PASS + freeze confirmation per `analyze-dag/SKILL.md` §Output & Lifecycle step 2, [TT-3379]) | Aggregator agent | Convert the source Epic's draft acceptance criteria into a formal checklist; annotate requirement-covered items `_(DAG frozen: {epic-slug}/dag v1)_` |
 | After each iteration commit (`implement` Phase 4.5) | Developer | Check off items delivered by this iteration |
 | After a PR is created | Developer | Append a `## 当前状态` live-status section (or update it) with PR number + mergeable; in an Epic task list, append the PR reference to the corresponding row |
 | After code review converges (`review-code` PASS, Phase E) | Orchestrator | Check off review-related items; annotate `_(reviewed: round N PASS)_`; update the `## 当前状态` review row; label the PR `ready-to-merge` — keep-mergeable automation takes over (hand-written keep-mergeable commits are retired) |
 | On CI key state transitions (first green / failure / cumulative goal reached) | Verifier or Developer | Update the process-type AC (e.g. "N consecutive green runs") progress note in the issue; record the run number |
 | At `verify` Phase 5.6 (final sweep before PASS) / issue close | Closing agent (Verifier on the primary path; otherwise the last role that closes the issue) | Final sweep — every remaining item gets annotated; **archive-at-close**: fold `## 当前状态`, then mark the `## 工件索引` comment archived per the artifact-index-guards rule guard #3 (see「归档动作」below) |

-> Historical ([org-internal #3072] phase 3): the requirements/design/plan exit sync points
-> were archived with their skills (detail: Tier-2 reference page
-> `rules/issue-checklist-sync-detail`, reachable via the ticket backend).
+> Historical ([TT-3072] phase 3): the requirements/design/plan exit sync points
+> were archived with their skills (detail: instance detail page
+> `rules/issue-checklist-sync-detail`, in the consuming instance).

 Between sync points the checklist stays as-is. **PR / review / CI
 transitions** MUST also be visible via the live status note below — the
@@ -32,12 +32,12 @@ For flows with externally visible transitions between skill exits —
 standalone bugfix, incident response, long-running reviews — maintain a short
 live status table near the top of the issue body, updated in place via the
 ticket-backend issue-update API at the transition moment (closes the
-stale-issue gap [org-internal #1668]/[org-internal #1689]]).
+stale-issue gap [TT-1668]/[TT-1689]]).

 All roles use the literal heading `## 当前状态` (no suffix). If an issue carries
-a legacy variant (e.g. `## 当前状态 (live)` from [org-internal #1668]), normalize it to
+a legacy variant (e.g. `## 当前状态 (live)` from [TT-1668]), normalize it to
 `## 当前状态` at the first transition touched. Example table + legacy-variant
-list: Tier-2 reference page `rules/issue-checklist-sync-detail`, reachable
+list: instance detail page `rules/issue-checklist-sync-detail`, reachable
 via the ticket backend.

 Rules:
@@ -57,15 +57,15 @@ Rules:
 - At verify PASS / issue close, fold the table's content into checklist
  annotations and remove the section (see the「归档动作」section below).

-### Automated sync ([org-internal #1833], timer-polled since [org-internal #2813])
+### Automated sync ([TT-1833], timer-polled since [TT-2813])

 PR / review / CI status-row transitions are automated by the `status-sync`
 poller (deployed as a host timer, every 5 min; event sources + latency table
-on the Tier-2 reference page `rules/issue-checklist-sync-detail`, reachable
+on the instance detail page `rules/issue-checklist-sync-detail`, reachable
 via the ticket backend). Roles do NOT hand-write those three row types. A PR
-body may carry several close refs (batch PRs, [org-internal #3731]
+body may carry several close refs (batch PRs, [TT-3731]
 `land-batch`): rows fan out to EVERY referenced issue
-(`parseClosesFixesWide` — [org-internal #3867], merged 2026-08-31) — Chinese 关闭/修复 refs
+(`parseClosesFixesWide` — [TT-3867], merged 2026-08-31) — Chinese 关闭/修复 refs
 drive rows too, even though the ticket backend never auto-closes those
 keywords. The remaining sync points (checklist annotations at skill exits,
 `## 当前状态` creation, deferral/pending marking, section fold-at-close) are
@@ -80,8 +80,7 @@ deduplicated `[status-sync-cron]` issue.
 Pipeline mode has natural sync points at skill exits; standalone bugfix and
 incident flows do NOT — the only boundaries are commit → PR → review → CI →
 merge, and EACH is a sync point with the same annotations as the progressive
-table above (full table: Tier-2 reference page
-`rules/issue-checklist-sync-detail`, reachable via the ticket backend): fix
+table above (full table: instance detail page `rules/issue-checklist-sync-detail`, reachable via the ticket backend): fix
 commit → tick fix-delivered ACs `_(commit {sha}: file)_`; PR → open/update
 `## 当前状态`; review convergence → tick review ACs + review row; CI
 transitions → process-AC progress with run number; verify PASS / close →
@@ -108,7 +107,7 @@ For tickets routed through the DAG pipeline (see workflow-routing rule
  comment (single-comment invariant). The body aggregator table is kept as a
  historical snapshot at close and does NOT carry ARCHIVE.

-### Kind/MVP tickets — exemption ([org-internal #3061])
+### Kind/MVP tickets — exemption ([TT-3061])

 `Kind/MVP` tickets run the interactive no-pipeline mode: no stage exits →
 **nothing to sync**, no `## 当前状态` section (no PR/review/CI rows until
@@ -137,7 +136,7 @@ non-checklist content. PR / review / CI transitions ALSO go into the

 ### 归档动作（issue 关闭 = 归档）

-**生命周期 = 工单生命周期**（[org-internal #1929]）：文档生命周期与源 issue 绑定 —— verify PASS → issue 关闭 = 归档。Tier-2 工件库无独立生命周期。
+**生命周期 = 工单生命周期**（[TT-1929]）：文档生命周期与源 issue 绑定 —— verify PASS → issue 关闭 = 归档。Tier-2 工件库无独立生命周期。

 归档是 **显式动作**，由关闭 issue 的 agent 执行：主路径为 Verifier 在 `verify` Phase 5.6；路径跳过 verify 时（audit-only、文档类、standalone/bugfix）由关闭 issue 的 role 代为执行。无论哪个 actor，均遵循 artifact-index-guards 规则 guard #3（机制以共享 write-patterns Pattern 10 为准）。动作序列：

@@ -146,7 +145,7 @@ non-checklist content. PR / review / CI transitions ALSO go into the
 3. **标记 `## 工件索引` 归档**：按共享 write-patterns Pattern 10 Archive-at-close 原位 edit（机制以 Pattern 10 为准）。横幅日期以实际关闭日为准。
 4. **关闭 issue**：PR body 的 `Closes #N` 在 merge 时自动关闭；无 PR 的流程由 **关闭 issue 的 agent** 执行工单后端的 issue-close API 完成闭环。

-约束（[org-internal #1928] 设计约束；机制细节以共享 write-patterns Pattern 10 Archive-at-close 为准，此处不重复）：
+约束（[TT-1928] 设计约束；机制细节以共享 write-patterns Pattern 10 Archive-at-close 为准，此处不重复）：

 - **L 级大件（>~300 行）留 Tier-2 工件库不删除** —— 页面与位置列 URL 保持不动（稳定 URL 供历史与共享契约引用）。
 - **索引/状态/归档判定全部收敛到 issue** —— Tier-2 工件库无独立生命周期；归档标记只落在 `## 工件索引` 评论。