Blocked-by: #14063
The stale sentence
AGENTS.md Prime Directive #14 (lines 304-305 on origin/main at 6643ba1) reads:
Even a pure-regeneration PR requests its pinned approval proactively, before queueing — the queue-time leg installs no dependencies and never evaluates the byte-equality lift (2026-08-29).
#14063 gives the merge_group job of Governed Surface Queue Guard a dependency install, so the byte-equality lift DOES evaluate at queue time: a spec PR carrying only its regenerated skills/*/references/_index.md now clears the queue leg with zero approvals. The maintainer ruled exactly that (2026-09-01, verbatim):
纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧
Left as written, the directive keeps sending seats to the maintainer for approvals the ruling just removed — the cost the ruling was about, surviving in the instruction file after the mechanism stopped requiring it.
Why it is not a rider on #14063
AGENTS.md is itself a governed surface, so folding this sentence into the workflow PR would fork that PR into the draft-only, maintainer-merge lane — the repo's own instruction is to split governed files into their own PR (「混合 diff 一条命中即整 PR 分叉」). Filed separately for that reason, not because it is optional.
What the amendment has to satisfy
- Net zero lines.
scripts/pm/check-skill-line-ratchet.mjs pins AGENTS.md at 1162 lines with headroom 0 by construction, so the replacement must reflow inside the same line count. - Keep the two facts that did NOT change: a governed diff still needs an authorized approval pinned to the current head to land through the queue, and an agent seat still never submits that approval.
- The new fact is narrow: a PR whose ONLY governed paths are register rows the generator certifies byte-exact needs no approval at queue time; anything hand-authored beside them still does.
- Companion note, non-governed and much smaller: the ledger comment in
scripts/pm/check-skill-line-ratchet.mjs (around line 407) carries the same "the queue leg installs no dependencies" parenthetical as a record of what that AGENTS.md edit said. It is history rather than a live claim, so it can stay — but whoever amends the prose should decide that deliberately rather than leave it to be re-derived later.
How to verify the amendment
node scripts/pm/check-governed-queue-guard.mjs --self-test already pins the behaviour the prose must describe: with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls, alongside the cases that still refuse (uncertified recompute, drift, a hand-authored sibling). pnpm check:pm-governed-prose and node scripts/pm/check-skill-line-ratchet.mjs are the two gates the edit itself has to keep green.
Found while implementing #14063; filed unassigned for triage.
Generated by Claude Code
Blocked-by: #14063
The stale sentence
AGENTS.mdPrime Directive #14 (lines 304-305 onorigin/mainat 6643ba1) reads:#14063 gives the
merge_groupjob ofGoverned Surface Queue Guarda dependency install, so the byte-equality lift DOES evaluate at queue time: a spec PR carrying only its regeneratedskills/*/references/_index.mdnow clears the queue leg with zero approvals. The maintainer ruled exactly that (2026-09-01, verbatim):Left as written, the directive keeps sending seats to the maintainer for approvals the ruling just removed — the cost the ruling was about, surviving in the instruction file after the mechanism stopped requiring it.
Why it is not a rider on #14063
AGENTS.mdis itself a governed surface, so folding this sentence into the workflow PR would fork that PR into the draft-only, maintainer-merge lane — the repo's own instruction is to split governed files into their own PR (「混合 diff 一条命中即整 PR 分叉」). Filed separately for that reason, not because it is optional.What the amendment has to satisfy
scripts/pm/check-skill-line-ratchet.mjspinsAGENTS.mdat 1162 lines with headroom 0 by construction, so the replacement must reflow inside the same line count.scripts/pm/check-skill-line-ratchet.mjs(around line 407) carries the same "the queue leg installs no dependencies" parenthetical as a record of what that AGENTS.md edit said. It is history rather than a live claim, so it can stay — but whoever amends the prose should decide that deliberately rather than leave it to be re-derived later.How to verify the amendment
node scripts/pm/check-governed-queue-guard.mjs --self-testalready pins the behaviour the prose must describe:with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls, alongside the cases that still refuse (uncertified recompute, drift, a hand-authored sibling).pnpm check:pm-governed-proseandnode scripts/pm/check-skill-line-ratchet.mjsare the two gates the edit itself has to keep green.Found while implementing #14063; filed unassigned for triage.
Generated by Claude Code