AGENTS.md: a rule's provenance cites the ADR / ruling record first, the commit sha second, never a bare tracker number — and runtime strings carry no numbers (ruling batch #195 item 3 letter C+D on #19123)

[os-project-manager]

Path: AGENTS.md :14 (the provenance sentence) | Tier H — RULED (batch #195 item 3 letter C+D on #19123, maintainer 「同意」) | graded by domain:skills#2

Filed by the director seat, summon #25 (session_012GcsUbuqFGBibkEDMRC1eE), executing ruling batch #195 item 3 letter C+D on #19123 (maintainer 「同意」). ⛔ Filed bare: domain:*, priority:* and type are triage's production. Landing: AGENTS.md (Tier H — draft PR, human merge) ⇒ the skills lane.

What changes

AGENTS.md today says a rule's provenance lives in the PR that landed it. #19123 measured that 11.7%–15.1% of one week's merged-PR numbers are already deleted from GitHub (no 301; the commit → PR association is empty), so that convention points readers at objects this repository does not control and has measured itself destroying.

Replace that sentence with the order the ruling sets:

1. A load-bearing internal anchor cites the ADR / ruling record when one exists (stable, in-repo, carries the narrative).
2. Otherwise it cites the commit sha in this repository's history. A PR number may follow as a convenience link, ⛔ never as the citation.
3. Runtime strings (refusal messages, prescriptions, anything printed to an author) carry no tracker numbers: the lesson is written into the text — the rule scripts/check-doc-authoring.mjs already enforces for every other package under the maintainer's words 「处理 issue 时犯的错应该总结成经验,保留 issue id没有意义」 ([finding] A tracker id sits in packages/core's plugin-registration refusal message — the ruled audience, in a package check-doc-authoring Rule 3's scanned root (packages/spec/src) cannot reach #13179).

Acceptance

• The sentence is replaced, not appended to; no second convention survives beside it.
• The fifteen measured lines in packages/spec are the spec seat's ([Decision] 承重出处该用什么形式:同一周已合并 PR 编号有 11.7–15.1% 今天已 404,而本仓源码正以它作凭据 #19123 stays in that lane); this card is the convention text only.
• Enforcement reach into packages/spec/scripts/** is [finding] check-doc-authoring 的两条腿都够不到 packages/spec/scripts/** —— 一条印给作者的拒绝消息里带着 404 的编号,而门禁是绿的 #19124, ⛔ not this card.
• Clause-②: no.

Dedupe words: AGENTS.md provenance convention · cite ADR or commit sha not PR number · tracker number decay 404 · runtime strings no issue id · #19123

---

Generated by Claude Code

[os-steve]

Lane first-touch grading (skills seat self-triage) — by the domain:skills seat 2 (session_017ETYWqMQD4qMtZzAGovWNi, seat post #19287) at 2026-09-20T22:31Z; premise re-read on origin/main 57ceb9d at 2026-09-20T22:27Z, thread read to its last comment in the same act. Second grading batch of this shift (the first, 16 cards, at 2026-09-20T21:42Z); grading is the seat's mechanical duty each fire (lanes/skills.md :22–:24), dispatch order stays the seat's value assessment under the maintainer's standing order.

finding → pm:queue · priority:p2 · docs.

• Class (b), RULED: re-read on 57ceb9d — AGENTS.md :14 still reads 「a rule's provenance lives in the PR that landed it」; the ruling replaces it with the order ADR / ruling record → commit sha (a PR number only as a convenience link) and 「runtime strings carry no tracker numbers」 (the check-doc-authoring rule generalised, the maintainer's 「保留 issue id没有意义」).
• Priority p2: the maintainer ruled it; [Decision] 承重出处该用什么形式:同一周已合并 PR 编号有 11.7–15.1% 今天已 404,而本仓源码正以它作凭据 #19123 measured 11.7–15.1 % of one week's PR numbers already gone. Next take after the two dispatched this fire (a Tier H PR waits on the maintainer's click either way).
• Serial: PR docs(agents): say how a return-delivered durability seam is declared #19214 (claude/issue-16233-…, draft) edits AGENTS.md (+20 / −10, the return-delivered seam declaration) — a different region ⇒ region-parallel under 甲, the later lander merges once. Not in MANDATORY_TIER_GLOBS (default tier); Tier H landing: draft + in-seat record + ACCEPT, the maintainer merges.
• Path: line prepended to the body.

---

Generated by Claude Code

[os-steve]

Claim: PM loop round 1 (skills seat 2 at #19287 — R1; the seat's own value assessment under the maintainer's orders in this session, verbatim 「当前任务处理完就只处理高优先级任务。」 and 「你应该自己评估哪些issue适合优先处理。」, 2026-09-20 — the maintainer's ruling on how a rule cites its provenance (batch #195 item 3 letter C+D, 「同意」), still contradicted by AGENTS.md :14)
Session: session_017ETYWqMQD4qMtZzAGovWNi
Branch: claude/issue-19294-provenance-cites-record-then-sha
Worktree: objectstack-issue-19294
Domain: domain:skills
Seat: domain:skills#2
File surface: AGENTS.md — the provenance sentence at :14 (「a rule's provenance lives in the PR that landed it」) and, only if the same convention is restated elsewhere in the file (grep provenance / PR that landed), those sentences; ⛔ not packages/spec (the fifteen measured lines are #19123's, the spec seat's), ⛔ not scripts/check-doc-authoring.mjs (its reach into packages/spec/scripts/** is #19124), ⛔ no other governed file.
Container & model: S in size, S in judgment, mode:subagent, default tier — dispatch-gates --tier --repo objectstack-ai/objectstack AGENTS.md: no path-derived mandate (Tier H by the register: draft PR, in-seat record + ACCEPT, the maintainer's click).
Clause-②: no
Thread-read: 5753146951
Ruling-ref: the maintainer's ruling batch #195 item 3 letter C+D on #19123 (「同意」), as the director recorded it on the card body; lane grading 5753146951 (class (b) RULED, p2 · docs). The seat's reading for the dev: REPLACE the sentence, ⛔ not append — the order is (1) the ADR / ruling record when one exists, (2) otherwise the commit sha in this repository's history, a PR number only as a convenience link and never as the citation, (3) runtime strings (refusal messages, prescriptions, anything printed to an author) carry no tracker numbers — the lesson is written into the text, the rule check-doc-authoring already enforces (the maintainer's 「处理 issue 时犯的错应该总结成经验,保留 issue id没有意义」); no second convention survives beside it; the sentence's own example, if it carries one, obeys itself (⛔ no bare tracker number in the new text — the id-lint over AGENTS.md is the gate).
Premise re-read (seat, origin/main 57ceb9d at 2026-09-20T22:27Z): AGENTS.md :14 still reads 「a rule's provenance lives in the PR that landed it」. The premise holds.
Serial constraints cleared: 1 of 24 open PRs touches AGENTS.md — PR #19214 (claude/issue-16233-agents-return-propagating-sea…, draft, +20 / −10 at :931–:956, the return-delivered seam declaration) — a different region ⇒ region-parallel under ruling 甲, the later lander merges once; git ls-remote --heads origin | grep issue-19294 → 0 heads; H17 index: 0 rows.

Net-line budget (a PM figure, ⛔ not the dev's to raise): net ≤ +3 lines in AGENTS.md. Label on the PR: skip-changeset. Tier H: the PR stays DRAFT — the seat reviews and ACCEPTs, the maintainer's click lands it.

---

Generated by Claude Code

[os-steve]

os-dev-report
{
"issue": 19294,
"status": "blocked",
"branch": "claude/issue-19294-provenance-cites-record-then-sha",
"pr": "#19453",
"head_sha": "9f35c66b45527069f948ee9918dce3f5476e9f28",
"session": "session_017ETYWqMQD4qMtZzAGovWNi",
"premise_still_valid": true,
"blocked_on": "AGENTS.md's line ratchet is at headroom 0 (1099 lines, ceiling 1099) and the ruled text is +3 physical lines, so pnpm check:pm-skill-ratchet exits 1 on the PR. Raising that ceiling requires a maintainer ruling on THIS card's AGENTS.md line budget, quoted verbatim in the raising PR body and in the CEILINGS comment of scripts/pm/check-skill-line-ratchet.mjs. The maintainer's 「同意」 on decision batch #195 item 3 letter C+D rules the TEXT; the dispatch carried no ruling on the LINE BUDGET, and a dev pays a line ratchet in deleted content or reports the gap, never by raising the ceiling. The ceiling row is untouched and the measured count is reported red. Everything else is done and pushed.",
"summary": "AGENTS.md :14 said a rule's provenance lives in the PR that landed it; that sentence is REPLACED (not appended to) by the ruled order: the ADR or ruling record when one exists, otherwise the commit sha in this repository's history, with a PR number demoted to a convenience link and never the citation — plus letter D's second half, that runtime strings (refusal prose, prescriptions, anything an author is shown) carry no tracker number and the lesson goes into the text. The neighbouring mechanical-enforcement clause is kept intact and the new text obeys itself (no bare tracker number; the id-lint that scans AGENTS.md is green on it). Net +3 lines in AGENTS.md, exactly the dispatch's budget — which is what puts the file over its zero-headroom ratchet ceiling, the one thing left. Assignee on the card was os-steve (the PM's, per the dispatch atom); I wrote none.",
"files_changed": [
"AGENTS.md"
],
"net_lines": "+6 / -3 = net +3 (AGENTS.md 1099 -> 1102 physical lines); no other file touched",
"before_after": {
"before": "(pnpm check:pm-skill-id-lint) — a rule's provenance lives in the PR that landed it. Where a hook or CI gate enforces a rule mechanically, the rule is stated once here and the script's own header is the authority on detail.",
"after": "(pnpm check:pm-skill-id-lint) — a rule's provenance cites the ADR or ruling record that decided it, otherwise the commit sha in this repository's history; a PR number is a convenience link, ⛔ never the citation. Runtime strings — refusal prose, prescriptions, anything an author is shown — carry no tracker number (pnpm check:doc-authoring): the lesson goes into the text. Where a hook or CI gate enforces a rule mechanically, the rule is stated once here and the script's own header is the authority on detail.",
"restatement_sweep": "grep -n -iE 'provenance|PR that landed|landed it' AGENTS.md on 57ceb9d = 2 hits: :14 (replaced) and :253 (an unrelated instruction that a repo-local ADR mirroring a cloud decision carries a ## Provenance section — left alone). The convention is stated once."
},
"tests": "No package is touched, so there is no dependency closure to build and no package test suite in scope; the repo-wide pnpm lint scan is CI's run. Verification is the derived gate union on head 9f35c66: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (no paths) yielded 15 families; every one run with its exit captured before any pipe; --ran reconciliation over the exit-coded record printed '15 derived, 15 run, 0 NOT-MEASURED, 0 UNRUN' and '✓ dispatch-gates --ran: 15 derived famil(ies) accounted for ... (a DERIVED zero — all 15 recorded an exit code and none of them is 3)'. 14 green, 1 red (the ratchet). Key verdict lines: '✓ check-skill-id-lint: 27 file(s) clean (pattern /#[0-9]{3,}/g)'; '✓ check-governed-prose: 2 instruction surface(s) name all 6 registered governed surfaces ... and claim no others'; '✗ check-skill-line-ratchet: AGENTS.md is 1102 lines; the ratchet ceiling is 1099. ... Raising a ceiling requires a maintainer ruling quoted in the PR.' No ablation applies: the change is one prose sentence in an instruction file, not a guard.",
"gates": [
"node scripts/check-closing-keyword-parity.mjs :: exit 0",
"node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0",
"node scripts/check-comment-mask-corpus.mjs :: exit 0",
"pnpm check:agent-test-spelling :: exit 0",
"pnpm check:docs-audit-scope :: exit 0",
"pnpm check:driver-memory-census :: exit 0",
"pnpm check:gitlink-declared :: exit 0",
"pnpm check:nul-bytes :: exit 0",
"pnpm check:pm-governed-merges :: exit 0",
"pnpm check:pm-governed-prose :: exit 0",
"pnpm check:pm-skill-id-lint :: exit 0",
"pnpm check:pm-skill-ratchet :: exit 1 (RED — the blocker; AGENTS.md 1102 vs ceiling 1099)",
"pnpm check:refd-timer-probe :: exit 0",
"pnpm check:required-contexts :: exit 0",
"pnpm check:watch-hint-literal :: exit 0",
"pnpm check:doc-authoring :: exit 0 (beyond the derived union — run because the new text names this gate)",
"pnpm check:pm-dispatch-gates :: exit 0 (beyond the derived union — the dispatch named it; detached with its exit captured, waited out in-round, 1883 cases pass, 970.3s)",
"node scripts/pm/check-governed-merges.mjs --pr 19453 :: exit 3 (GOVERNED, landing tier H — mechanism assumption 3 confirmed; the PR stays DRAFT)"
],
"mechanism_assumptions": [
"1 HOLDS: AGENTS.md :14 on 57ceb9d still read 「a rule's provenance lives in the PR that landed it」; the restatement grep found no second statement of the convention.",
"2 HOLDS: PR #19214 edits AGENTS.md at a different region (+20 / -10). REFINED, and it matters: that PR also raises the same ratchet row 1099 -> 1109 with its own maintainer ruling quoted in the CEILINGS comment. If it lands first the arithmetic here becomes 1109 -> 1112, still red — merging origin/main does not clear the ratchet by itself.",
"3 HOLDS: check-governed-merges --pr 19453 exits 3, GOVERNED, landing tier H(人合), size 9 changed lines under the 5000 threshold.",
"4 HOLDS for the id-lint and doc-authoring gates (both green). REFINED: pnpm check:doc-authoring is NOT in this card's derived union — AGENTS.md is outside its scan roots — so it was run as a declared extra because the new prose names it."
],
"mcp_calls": "0 — no MCP GitHub tool was called, read or write.",
"api_writes": "3 REST proxy writes + 2 git pushes. REST: POST /repos/objectstack-ai/objectstack/pulls (draft PR 19453); POST /repos//issues/19453/labels (skip-changeset, via scripts/pm/label-write.mjs — HTTP 200, read-back MATCHES the target: size/xs, skip-changeset); POST /repos//issues/19294/comments (this report, via scripts/pm/post-stamped.mjs). Git: the empty-branch write probe, then the work commit. Zero PATCH on the PR body (written once, at creation, and read back byte-identical). No label written on the card.",
"deviations": [
"Declared narrowing: no repo-wide pnpm lint and no package build/test — the diff touches no package, and the repo-wide scan is CI's run under os-dev.md's local-verification scope.",
"Two families run beyond the derived union, both declared: pnpm check:doc-authoring (the new prose names it) and pnpm check:pm-dispatch-gates (the dispatch named it).",
"Self-report on the commit message: it says the runtime-string discipline is one check:doc-authoring 'already holds every package to', which overstates the gate's reach — its prose-id leg scans packages/ minus packages/spec on a shrink-only baseline of 821 pinned sites. The PR body states the reach precisely. Not amended, because amending a pushed commit needs a force-push and the message is otherwise correct (no card relation, model-free trailer pair).",
"The ratchet ceiling row in scripts/pm/check-skill-line-ratchet.mjs was left untouched although the gate is red — raising it is the maintainer act, not the dev act."
],
"open_questions": [
{
"question": "The ruled text cannot land green: AGENTS.md is at headroom 0 and the ruling's three clauses are +3 physical lines. How is the ratchet paid?",
"options": [
"A — the maintainer rules this card's AGENTS.md line budget at +3 (1099 -> 1102, or 1109 -> 1112 if PR #19214 lands first); the ruling is quoted verbatim in the PR body and in a new CEILINGS comment on the AGENTS.md row, and a follow-up commit on this branch lands the row. This is the route the ratchet header prescribes and the route every precedent on that row took (1074 -> 1075, 1075 -> 1099, and #19214 at 1099 -> 1109).",
"B — pay the 3 lines by compressing content elsewhere in AGENTS.md. Needs a claim on a file surface this card does not hold, and mixes an unruled deletion into a ruled governed diff.",
"C — trim the ruled text to net 0. Not available without dropping letter D or the clause that names the runtime-string population: the paragraph goes from about 466 to about 779 bytes of prose and six lines cannot hold that at the section width (6 x 93 = 558)."
],
"recommendation": "A. 实际业务需求: the need is measured, not speculative — the spec seat read 11.7-15.1 % of one week's merged-PR numbers already deleted, and AGENTS.md is read in full by every seat session, so the decayed convention is being followed today; holding ruled text for three lines serves nothing. 项目长远合理性: the raise route is the ratchet's own contract (per-card maintainer ruling quoted in-tree), so the decision stays recorded where the next author reads it, rather than being worked around by compressing unrelated rules out of the file. 防 AI 写错: the sentence is replaced, not appended, so there is no second spelling for an agent to fall back to, and the in-tree quoted ruling stops the next author inferring a standing licence to grow the file. 创业阶段不扩散: +3 is the minimum faithful text — no new gate, no new surface, no staged window, and the old convention retires immediately rather than coexisting."
}
],
"out_of_scope_findings": [
"noted, not filed: check:doc-authoring's prose-id leg excludes packages/spec and runs on a shrink-only baseline, so the mechanical reach of the runtime-string rule is narrower than the prose states. Carrier: the reach card already named on the #19294 body — no new card, and the PR body states the reach precisely instead of implying repo-wide enforcement.",
"noted, not filed: the CEILINGS row for AGENTS.md carries four stacked per-card narratives inside a gate script whose own header prescribes moving narrative out of operational text. Carrier: the next raise on that row, PR #19214, already in flight."
]
}

---

Generated by Claude Code

[os-steve]

os-dev-report
{
"issue": 19294,
"status": "done",
"branch": "claude/issue-19294-provenance-cites-record-then-sha",
"pr": "#19453",
"head_sha": "a799442150f5db0beb19b71741c3f59ae53d43b9",
"session": "session_017ETYWqMQD4qMtZzAGovWNi",
"premise_still_valid": true,
"supersedes": "the earlier os-dev-report on this card (status blocked on the line ratchet). The seat widened the file surface to pay the ratchet in retired content; the ratchet is now green and nothing was raised.",
"summary": "AGENTS.md :14's provenance sentence is REPLACED by the ruled order — the ADR or ruling record first, otherwise the commit sha in this repository's history, a PR number only as a convenience link and never the citation — plus letter D, that runtime strings carry no tracker number and the lesson goes into the text. The +3 physical lines that costs are paid back by retiring four fragments that each restate a rule living elsewhere or point a second time at a file already pointed at, so the file returns to 1099 lines and pnpm check:pm-skill-ratchet is green with the ceiling row untouched. All 15 derived gate families plus one declared extra are green on head a799442, reconciled with --ran. The PR stays DRAFT: governed, landing tier H.",
"files_changed": [
"AGENTS.md"
],
"net_lines": "AGENTS.md 1099 -> 1099 = NET 0 against origin/main (the ruled text +3, the retirements -3). The ratchet ceiling row in scripts/pm/check-skill-line-ratchet.mjs is UNTOUCHED at 1099. PR diff as GitHub reports it: +25 / -25 over 1 file.",
"retirement_table": [
{
"retired_at": "AGENTS.md :58-59 (pre-edit)",
"text": "; the script headers are the authority on detail",
"kind": "verbatim restatement of a rule whose home is another line",
"rule_still_lives_at": ":19 — 'Where a hook or CI gate enforces a rule mechanically, the rule is stated once here and the script's own header is the authority on detail.' The two gates it qualified (pnpm check:type-check-coverage, pnpm check:type-check-debt) are still named on the same line.",
"bytes": 48
},
{
"retired_at": "AGENTS.md :452-453 (pre-edit)",
"text": "The two measured mutation shapes and their triggers live in pm-dispatch references/platform-readings.md.",
"kind": "second pointer to a reference file already pointed at from another surviving line",
"rule_still_lives_at": ":433-434, two paragraphs above in the SAME section — 'the readings live in pm-dispatch references/platform-readings.md'. The paragraph's own rule (spell poison-shaped tokens out; read the body back) and its ⛔ line both survive.",
"bytes": 107
},
{
"retired_at": "AGENTS.md :758-759 (pre-edit)",
"text": "(shape, sha256 vs that record, record pin == .objectui-sha)",
"kind": "the gate's own detail list — a restatement of the rule whose home is another line",
"rule_still_lives_at": ":19 (the script's own header is the authority on detail); scripts/check-sdui-manifest.mjs is still named on the same line, and the regenerate-on-pin-bump rule is at :159-161 in the Frontend section.",
"bytes": 61
},
{
"retired_at": "AGENTS.md :760-761 (pre-edit)",
"text": "— "could not run" is a failure, not a skip (Route & surface ownership §3) —",
"kind": "verbatim restatement plus a second pointer to the section that owns the rule",
"rule_still_lives_at": ":851-855, Route & surface ownership rule 3 — 'a verifier that silently degrades (reusing a stale build, skipping a check it could not run) is worse than no verifier, because it reports success. Prefer failing to falling back.' Twelve scripts cite that section by name and none of them cites :760.",
"bytes": 82
}
],
"lines_bought_by_content": "3 lines, all bought by deleted content and NONE by re-wrap — proved per paragraph before the edit: a greedy re-wrap of each untouched paragraph at its own observed width returns exactly the line count it already has (:57-63 actual 7 = greedy 7; :449-455 actual 7 = greedy 7; :751-762 actual 12 = greedy 12), so none of the three carried re-wrap slack to bank; after the deletions the same greedy wrap returns 6, 6 and 11. Measured total deleted: 298 bytes of prose. The wrapper keeps backtick spans whole, so no inline code identifier is split across a line (checked: zero odd-backtick lines in the diff).",
"candidates_rejected": [
":163 'Full procedure: docs/releases-maintenance.md.' — the ONLY pointer to that file in AGENTS.md, so retiring it leaves the rule with no other home. Rejected.",
":949 '(scripts/check-durability-degradation-log-level.mjs; its header is the authority)' — qualifies as a restatement, but it sits inside PR #19214's reserved region :931-:956. Rejected on the region fence.",
":865 '— its header is the authority on detail' (39B) and :720 '(its own output is the authority on detail)' (43B) — both qualify as restatements of :19, but neither buys a line: :862-871 greedy-wraps to 10 lines with or without it, and :720 is a one-line lead-in that survives the deletion. Rejected as insufficient; ⛔ not cut deeper into a rules paragraph to manufacture the line.",
":140 '(see Multi-agent discipline §8)' — 33B, buys no line, and it is the only pointer to §8. Rejected.",
":579 "§10's 'never trust git's textual merge of a generated file'" — qualifies as a restatement, but its paragraph :552-619 is loosely wrapped (actual 68 lines vs greedy 61), so any line taken there would be re-wrap currency, not content. Rejected on the content-only rule.",
":261 / :272 the governed-surface enumerations — pnpm check:pm-governed-prose reds when the paragraph names fewer surfaces than the register, so these are gate-pinned text. ⛔ Rejected: retiring one would break a gate."
],
"tests": "Derived union re-run on head a799442 after the merge of origin/main: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (no paths) — 15 families, byte-identical to the list derived in round 1, and no STALE TREE warning this time (the pre-merge derivation printed one, naming scripts/pm/check-governed-queue-guard.mjs and scripts/pm/os-regen-merge.sh; the merge cleared it). Every family run with its exit captured before any pipe; --ran over the exit-coded record: '15 derived, 15 run, 0 NOT-MEASURED, 0 UNRUN' and '✓ dispatch-gates --ran: 15 derived famil(ies) accounted for ... (a DERIVED zero — all 15 recorded an exit code and none of them is 3)'. ALL 16 GREEN. Verdict lines: '✓ check-skill-line-ratchet: AGENTS.md is 1099 lines (ceiling 1099; headroom 0)'; '✓ check-skill-id-lint: 27 file(s) clean (pattern /#[0-9]{3,}/g)'; '✓ check-governed-prose: 2 instruction surface(s) name all 6 registered governed surfaces ... and claim no others'; '✓ doc authoring guard: 403 files clean'. No package is touched, so there is no build closure and no package test suite in scope; the repo-wide pnpm lint scan is CI's run. No ablation applies — the change is prose in an instruction file, not a guard.",
"gates": [
"node scripts/check-closing-keyword-parity.mjs :: exit 0",
"node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0",
"node scripts/check-comment-mask-corpus.mjs :: exit 0",
"pnpm check:agent-test-spelling :: exit 0",
"pnpm check:docs-audit-scope :: exit 0",
"pnpm check:driver-memory-census :: exit 0",
"pnpm check:gitlink-declared :: exit 0",
"pnpm check:nul-bytes :: exit 0",
"pnpm check:pm-governed-merges :: exit 0",
"pnpm check:pm-governed-prose :: exit 0",
"pnpm check:pm-skill-id-lint :: exit 0",
"pnpm check:pm-skill-ratchet :: exit 0 (was exit 1 before the retirements; AGENTS.md 1099 vs ceiling 1099, headroom 0)",
"pnpm check:refd-timer-probe :: exit 0",
"pnpm check:required-contexts :: exit 0",
"pnpm check:watch-hint-literal :: exit 0",
"pnpm check:doc-authoring :: exit 0 (beyond the derived union — the new text names this gate)",
"node scripts/pm/check-governed-merges.mjs --pr 19453 :: exit 3 (GOVERNED, landing tier H, size 50 changed lines under the 5000 threshold)",
"pnpm check:pm-dispatch-gates :: exit 0 (round 1, 1883 cases, 970.3s; NOT re-run — the merge changed no dispatch-gates source, measured: git diff --name-only 5ee37e0 a799442 | grep -c dispatch-gates = 0)"
],
"mcp_calls": "0 — no MCP GitHub tool was called, read or write.",
"api_writes": "4 REST proxy writes + 4 git pushes across both rounds. REST: POST /pulls (draft PR 19453); POST /issues/19453/labels (skip-changeset, read-back matched); POST /issues/19294/comments twice (the round-1 report and this one). Git: the empty-branch probe, the provenance commit, the retirement commit, the merge commit. ⛔ Zero PATCH on the PR body — written once at creation, per the rework instruction to leave it as written.",
"deviations": [
"⚠️ THE PR BODY IS NOW STALE AND WAS DELIBERATELY NOT PATCHED, per the rework instruction. Its section titled "The AGENTS.md line ratchet — measured red, and ⛔ not a dev's to move" describes the pre-rework state: it says pnpm check:pm-skill-ratchet exits 1, asks the maintainer for a +3 line-budget ruling, and its 维护者速读 "你要做的" names that ruling as item ①. NONE of that is true of head a799442 — the ratchet is green, the ceiling is untouched, and the only maintainer act left is the merge click. The seat carries this correction into the review record.",
"Merged origin/main once (8e368dc, no rebase) to clear the derivation's STALE TREE warning; the merge touched no line of AGENTS.md (git diff HEAD~1 --stat -- AGENTS.md empty) and AGENTS.md on main is still 1099 with its ceiling row still 1099, so the net-0 arithmetic is against the current main.",
"Declared narrowing: no repo-wide pnpm lint, no package build or test — the diff touches no package.",
"One family run beyond the derived union, declared: pnpm check:doc-authoring. pnpm check:pm-dispatch-gates was run green in round 1 and not re-run; the merge changed no dispatch-gates source.",
"Another actor relabelled the PR while it sat: labels now read documentation, size/s, skip-changeset (round 1 wrote skip-changeset onto size/xs). ⛔ Not corrected — not mine to set.",
"Self-report carried forward: the round-1 commit message says the runtime-string discipline is one check:doc-authoring 'already holds every package to', which overstates that gate's reach (its prose-id leg scans packages/ minus packages/spec on a shrink-only baseline). The PR body states the reach precisely. Not amended — that would need a force-push."
],
"open_questions": [],
"out_of_scope_findings": [
"noted, not filed: check:doc-authoring's prose-id leg excludes packages/spec and runs on a shrink-only baseline, so the mechanical reach of the runtime-string rule is narrower than the prose states. Carrier: the reach card already named on the #19294 body — no new card.",
"noted, not filed: the CEILINGS row for AGENTS.md carries four stacked per-card narratives inside a gate script whose own header prescribes moving narrative out of operational text. Carrier: the next raise on that row, PR #19214, already in flight.",
"noted, not filed: two more restatements of the file's own 'the script's own header is the authority on detail' clause survive at :720 and :865 (and a third at :949 inside PR #19214's region). Each is retirable content the next AGENTS.md ratchet squeeze can spend; none buys a line on its own. Carrier: the next PR that needs lines in this file."
]
}

---

Generated by Claude Code

[os-steve]

ACCEPT — domain:skills#2 (session_017ETYWqMQD4qMtZzAGovWNi, seat post #19287) at 2026-09-20T23:23Z; PR #19453 (draft, head a799442, Tier H — the merge is the maintainer's click, ⛔ not the queue).

Checklist, verified on GitHub and on the tree (⛔ not on the report's self-description):

• Shape: draft · base main · first line Fixes #19294 · Clause-②: no line-initial · ## 维护者速读(草稿) present (corrected by the seat on this head) · labels skip-changeset + size/s + documentation.
• Scope: 1 file, AGENTS.md +25 / −25 (net 0; 1099 / 1099, the ceiling row untouched) — :14 replaced by the ruled order, +3 lines paid by four retirements each re-read to its surviving home; PR docs(agents): say how a return-delivered durability seam is declared #19214's region untouched. check-governed-merges --pr 19453: GOVERNED Tier H.
• Contract: ## Contract review PASS on the PR at this head (5753476235, in-seat at CONTRACT_REVIEW_TIER); --pair 19453 after the record: exit 0.
• Tests, seat-run on the head: line ratchet exit 0 (1099 / 1099), id-lint exit 0, governed-prose exit 0; merge-tree vs origin/main 8e368dc clean. The dev's union 15 / 15 with --ran reconciled on this head, check:doc-authoring exit 0, check:pm-dispatch-gates exit 0 (round 1, no dispatch-gates source changed since).
• Gates / CI on a799442 at 2026-09-20T23:21Z: 26 check runs, 1 still running, 0 red.
• Report: mcp_calls 0 · api_writes 4 (+4 pushes across two rounds) · the rework paid the ratchet in retired content as the seat instructed, with the rejected candidates listed. The stale PR body (round 1's blocker) rewritten by the seat on this head — one footer, content read back. Three observations with carriers, correctly not filed. Ruling executed: batch chore(deps)(deps-dev): bump @types/node from 20.19.30 to 25.0.10 #195 item 3 letter C+D (maintainer 「同意」).

Landing: Tier H ⇒ the maintainer merges (or an authorized APPROVED review, then the seat lands); the PR stays draft until then. pm:dispatched comes off at MERGED (the Fixes line closes this card).

---

Generated by Claude Code