Found by the #9642 sweep (H4: where else does this repo reason wrongly about the required set). Recording, not claiming. AGENTS.md is a governed surface, so a dev seat may not edit it — this needs a maintainer edit.
The prose
AGENTS.md, in the auto-merge / queue section (around line 347):
And the queue enforces only the required set — Lint & Repo Gates (the whole check:* gate family, formerly published under a name that described only one of its steps) and TypeScript Type Check block by maintainer decision (2026-08-07); everything else is advisory and rides through
The measurement (2026-08-18, ordinary agent seat, re-measured independently for #9642)
GET /repos/objectstack-ai/objectstack/rulesets/12119582 returns six required_status_checks contexts, not two:
TypeScript Type Check
Test Core
Dogfood Regression Gate
Build Core
Temporal Conformance (live PG + MySQL)
Lint & Repo Gates
So four of the six — Test Core, Dogfood Regression Gate, Build Core, Temporal Conformance (live PG + MySQL) — are described by the one file every seat reads as advisory-and-rides-through when they in fact block. The 2026-08-07 date in the sentence is the #5617 first batch; the second batch landed on 2026-08-09 and the sentence never followed.
Why it is worth fixing rather than leaving
The sentence is operative instruction, not background: a seat deciding whether a PR is queue-ready reads it to classify a red check. Under the current text a red Build Core reads as "advisory, rides through" — which is the exact misclassification that puts a PR into the queue to be ejected, or leaves a seat waiting on a context it believes optional. It also under-states the blast radius of a rename in any of those four jobs.
Note the file is inside check-required-contexts.mjs's INSTRUCTION_SURFACES scan, but that scan is lexicon-only: it asserts the file NAMES the literals it is required to name (mustName: ['Lint & Repo Gates', 'TypeScript Type Check']), and cannot see that the surrounding sentence claims the other four are advisory. Widening mustName for this file to the full live set is one possible mechanical follow-on, and would need the same governed-surface merge.
Related: #9642 (the false-premise card that produced this sweep; it also ships --verify-required-set, which is what re-measured the live set here), #5617, #9533.
Generated by Claude Code
Found by the #9642 sweep (H4: where else does this repo reason wrongly about the required set). Recording, not claiming.
AGENTS.mdis a governed surface, so a dev seat may not edit it — this needs a maintainer edit.The prose
AGENTS.md, in the auto-merge / queue section (around line 347):The measurement (2026-08-18, ordinary agent seat, re-measured independently for #9642)
GET /repos/objectstack-ai/objectstack/rulesets/12119582returns sixrequired_status_checkscontexts, not two:So four of the six —
Test Core,Dogfood Regression Gate,Build Core,Temporal Conformance (live PG + MySQL)— are described by the one file every seat reads as advisory-and-rides-through when they in fact block. The 2026-08-07 date in the sentence is the #5617 first batch; the second batch landed on 2026-08-09 and the sentence never followed.Why it is worth fixing rather than leaving
The sentence is operative instruction, not background: a seat deciding whether a PR is queue-ready reads it to classify a red check. Under the current text a red
Build Corereads as "advisory, rides through" — which is the exact misclassification that puts a PR into the queue to be ejected, or leaves a seat waiting on a context it believes optional. It also under-states the blast radius of a rename in any of those four jobs.Note the file is inside
check-required-contexts.mjs's INSTRUCTION_SURFACES scan, but that scan is lexicon-only: it asserts the file NAMES the literals it is required to name (mustName: ['Lint & Repo Gates', 'TypeScript Type Check']), and cannot see that the surrounding sentence claims the other four are advisory. WideningmustNamefor this file to the full live set is one possible mechanical follow-on, and would need the same governed-surface merge.Related: #9642 (the false-premise card that produced this sweep; it also ships
--verify-required-set, which is what re-measured the live set here), #5617, #9533.Generated by Claude Code