docs(agents): PD #14 — a generator-certified regeneration clears the queue with zero approvals

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#14067

Prime Directive #14 told every seat to pre-request a pinned maintainer approval before
queueing even a pure regeneration, and justified it with a parenthetical that is no longer
true on main: the queue guard's merge_group leg now installs the generator toolchain,
so the byte-equality lift does evaluate at queue time. Left as written, the directive
kept sending seats to the maintainer for the exact approval the 2026-09-01 ruling removed.

Maintainer ruling this implements (2026-09-01, verbatim and untranslated):

纯生成的指针行(spec 源变更后再生成的 references/_index.md) 不需要我审核吧

The sentence, before and after

Before (AGENTS.md L304-306 at merge base 3795c5f5d, verbatim):

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).

After (AGENTS.md L304-306 at 244e3ae4f, verbatim):

Hand-authored governed content needs that approval; a PR whose only governed paths are register rows the queue leg regenerates byte-exact clears with zero approvals (2026-09-01) — an uncertified recompute, drift or a hand-authored sibling keeps it governed.

Nothing in it was invented. The criteria are the queue guard's own pinned case names —
with-the-toolchain-installed-a-PURE-REGENERATION-merge-group-CLEARS-with-zero-approvals-and-zero-api-calls,
plus the three shapes that still refuse: a-recompute-that-does-not-certify-still-REFUSES-the-same-merge-group-fail-closed
(no-toolchain and drift) and a-hand-authored-skills-file-beside-a-certified-regeneration-is-still-REFUSED.

The two facts that did not change are both still there, untouched by this diff:
a governed diff still lands only on an authorized approval pinned to the current head
(L301-304, GOVERNED_APPROVERS, commit_id = that sha), and no agent seat submits that
approval under any account (L306-308).

Premise verified on today's origin/main

Both halves checked first-hand at merge base 3795c5f5d, before writing:

• AGENTS.md L304-306 still carried the stale parenthetical (quoted above, byte-exact).
• .github/workflows/governed-surface-guard.yml now installs: Setup pnpm +
  pnpm install --frozen-lockfile, every toolchain step continue-on-error, and its own
  comment states the intent — "Both legs install." The guard header's ⭐ block says the same
  ("THE JOB INSTALLS DEPENDENCIES"), and the --self-test pins the wiring.
• PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's line citation from the card (L304-305) is still accurate; the sentence had not
  materially moved since the card was written, so no re-scoping was needed.

Net zero, measured before writing

The ratchet pins AGENTS.md at 1162 with headroom 0, so the replacement had to reflow
inside the count. Measured with the gate's own wrapLine at MAX_LINE_BYTES = 120 before
any edit:

measurement	value
PD #14 landing paragraph L296-312, lossless rewrap	17 lines → 17 lines (headroom 0)
reflow region L304-312 (the tail from the edited sentence)	9 lines → 9 lines (headroom 0)
replaced fragment	194 B → 259 B (+65 B)
widest resulting line	120 B (budget 120 B)
AGENTS.md total	1162 → 1162 lines

The +65 B is absorbed entirely by the slack in the region's last line, which was 57 B.
The ceiling is not byte arithmetic — greedy wrapping breaks on words, so it was found by
measuring real candidate strings: a 257 B candidate spilled to a 10th line while the chosen
259 B one fits. Candidates at +67 B and above spill; the chosen wording is at the measured
maximum that keeps the count.

Gate verdict line, quoted:

✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).

Companion ledger comment: KEPT as history, with a dated supersession marker

scripts/pm/check-skill-line-ratchet.mjs L402-414 is the ledger entry for the 1158 → 1162
bump, and its parenthetical carried the same "installs no dependencies" phrasing.

Decision: keep the history, mark it superseded — do not update it to today's facts.
Rationale: that entry exists to record why +4 lines was priced, and the rider it prices
cost +2 precisely because the queue leg then installed nothing. Rewriting it to describe
today's mechanism would erase the reason the bump was justified, which is the one thing the
ledger is for. But a bare present-tense claim is exactly what this card is about, so leaving
it unmarked invites the next reader to take it as live. The parenthetical is now:

(the queue leg then installed nothing, so the byte-equality lift never evaluated; SUPERSEDED 2026-09-01/#14067)

Also net zero: 97 → 111 chars, absorbed by reflowing the same 7 comment lines (L405-411,
7 → 7) at the block's existing 82-column width (L402-403 were already 82). That script is
not itself ratcheted; net zero here is the correction carve-out's discipline, not a gate.

Sibling coherence

A queued sibling card (#14059) will add a machine-readable enqueue-precondition line to the
pm-dispatch landing checklist. The new wording therefore states both halves in one breath
— hand-authored governed content ⇒ pinned approval, generator-certified-only ⇒ zero approvals
— so a seat reading the two texts side by side cannot construct a conflict between "approval
must precede enqueue" and "this class needs none". Noted here deliberately without a closing
keyword; that card stays open on its own.

Gates

Head 244e3ae4f. Derived union re-run after the final commit:
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands
(exit 0; change set derived by the tool itself from the merge base 3795c5f5d, 2 paths).
21 commands, exit codes captured before any pipe:

gate	exit
the 20 other derived commands (check:pm-governed-prose, check:pm-skill-ratchet, check:pm-governed-merges, check:pm-dispatch-gates, check:required-contexts, check:watch-hint-literal, check:entry-guard, check:parse-guard, check:docs-audit-scope, check:cli-command-ids, check:bash32-floor, check:agent-test-spelling, check:cross-package-test-inputs, check:pm-skill-id-lint, check:pnpm-filter-targets, check-ci-filter-parity, check-cross-package-test-inputs, check-required-contexts, check-shard-attestation, bare-root-worklist --self-test)	0
node scripts/check-test-completeness.mjs	3 — NOT MEASURED

check-test-completeness exit 3 is its documented PREREQUISITE NOT MET branch: it grades a
saved turbo run test log and the derived family names it with no argument. Its own text says
"⛔ It is not a red, and there is nothing here to fix." CI passes it a log; that path is
unreachable locally.

Named on the card, plus the ones this diff drags in, run separately (exit codes before pipes):

gate	exit	verdict line
node scripts/pm/check-skill-line-ratchet.mjs	0	✓ check-skill-line-ratchet: AGENTS.md is 1162 lines (ceiling 1162; headroom 0).
node scripts/pm/check-skill-line-ratchet.mjs --self-test	0	✓ check-skill-line-ratchet self-test: 111 cases pass.
pnpm check:pm-governed-prose	0	✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces … and claim no others.
node scripts/pm/check-governed-queue-guard.mjs --self-test	0	✓ check-governed-queue-guard self-test: 129 cases pass (…)
pnpm check:skill-frame-sync	0	✓ check-skill-frame-sync: 4 copies of the decision frame are structurally isomorphic across 3 files
pnpm check:nul-bytes	0	check-nul-bytes: OK (scanned 7715 text file(s) … no raw ASCII control bytes).
pnpm check:ratchet-remedy-authority	0	—
node scripts/check-published-list-mirrors.mjs	0	OK: 1 published list mirror(s) match their constants line for line.
node scripts/check-skills-token-ratchet.mjs	0	✓ check-skills-token-ratchet: 38 authored bundle file(s) within their ceilings

The edited script's own test suite is its --self-test (there is no separate vitest file
naming it); it is in the table above at 111 cases. Its three in-repo importers
(check-published-list-mirrors, check-skills-token-ratchet, check:pm-dispatch-gates) were
run as well.

Changeset

Publishes nothing from any package — the diff is AGENTS.md plus a comment in
scripts/pm/. Carrying skip-changeset, applied additively and read back.

Landing

AGENTS.md is a governed surface, so this is draft-only: no merge, no queue, no
auto-merge, no ready-flip from this seat. Landing is the maintainer's, by hand, or through the
queue on an authorized approval pinned to head 244e3ae4f.

Generated by Claude Code

---

Generated by Claude Code