AGENTS.md §4 promises the pinned sibling is protected, but `Console Pin Gate` only BUILDS it — a break that reds objectui's tests is invisible to every gate in both repos

[os-warren]

Filed by domain:spec execution seat 2, session session_01UDXER3sdqfeVYpEWZs5mZx, 2026-09-22T08:1xZ. ⛔ Unlabelled and unrouted on purpose — an execution seat files, triage grades and routes.

Surfaced by the second at-tier review of PR #19657, which found a real sibling break that no gate caught. ⛔ Re-derived first-hand here, ⛔ not taken on the reviewer's word.

The rule, and what it promises

AGENTS.md:1098-1105, Post-Task Checklist §4:

A removal that breaks the pinned sibling checkout ships together with the sibling fix and the pin bump — or it does not ship. The Console Pin Gate job builds objectui at the pinned .objectui-sha against current main, so a removal or rename the pinned sibling still imports turns main red for every PR in the repo the moment it merges — 「retire the surface」 and 「leave the sibling untouched」 cannot both hold.

The rule is right. Its stated mechanism is narrower than its text claims, and the gap is load-bearing because the rule leans on the gate for its teeth.

What the gate actually does — read from the workflow, not from the rule

.github/workflows/ci.yml, the Console Pin Gate job, has exactly three substantive steps:

step	command
Build the Console SPA at the pinned objectui SHA	bash scripts/build-console.sh
Assert a real Console dist is in place	an inline dist check
Verify the Console dist stamp matches the pin	pnpm check:console-sha

And scripts/build-console.sh invokes no test runner and no typecheck: grep -nE "test|vitest|typecheck|tsc" over it returns a single hit, inside a comment at :265, about probe derivation. Lit control for that grep: the same instrument fires on the workflow file itself, which does contain run: lines.

⇒ the gate builds the sibling and stamps it. It ⛔ never runs objectui's suite and ⛔ never typechecks it.

The consequence, measured on a live case

PR #19657 retires Connector.connectionTimeoutMs and wraps both carriers in a z.preprocess pipe (the ADR-0087 residue stage). At objectui@87af769e9a3ee28ace099fdd653d3ebd79fe82e2 — the current .objectui-sha — packages/app-shell/src/views/metadata-admin/clientValidation.optOuts.test.ts:468 asserts checks(DeclarativeConnectorEntrySchema) > 0, reading _zod.def.checks.

tree	reading
against objectstack main	1
against PR #19657's head	0 — a pipe def has no checks array

One assertion reds. The SPA still builds, so the gate is green-or-skipped either way. ⇒ a genuine break in the pinned sibling passed every gate in both repos and was caught only by a human-tier contract review, on its second round. Tracked on the sibling side as objectui#10211.

⚠️ It was skipped at that head in fact — but that is not the finding. A green run would not have caught it either, and that is the finding.

Why the rule's text and the gate's reach diverge

The rule was written for removals and renames of an exported surface: the sibling imports a name, the name is gone, the build fails. For that class the mechanism is exact. This break is a different class — the export still exists, still imports, still behaves, and only its internal representation changed. Nothing fails to build; a structural assertion stops being true.

⇒ the rule's pre-merge prescription — 「does the pinned sibling import what you are removing? git grep it」 — also cannot see this class, because nothing was removed to grep for.

Options, ⛔ none of them decided here

1. Widen the gate — run the pinned sibling's test suite, or the subset that touches spec schemas. ⚠️ Cost is real and must be measured before it is proposed: a full sibling suite in every objectstack PR is a large standing bill, and the job already carries a 45-minute timeout.
2. Narrow the rule's text to what the gate can actually enforce, and say plainly that representation changes are not covered — pairing it with a named manual step at the same place.
3. Move the pin's own discipline: treat a sibling assertion that reads a dependency's internal def shape as a defect in the sibling (objectui#10211 takes that view for this instance), so the class stops existing rather than being gated for.

⭐ These are not equivalent and the choice is not an execution seat's. (1) buys coverage with standing cost, (2) buys honesty with no coverage, (3) buys both but only where the sibling cooperates. A maintainer or the skills lane should pick.

⚠️ Reach of this reading

One gate was read, because one break exposed it. ⛔ Not measured: whether other cross-repo gates in this repo carry the same build-but-do-not-test shape, and whether objectui's own CI has a reciprocal gap facing objectstack. Whoever takes this should census both before choosing an option.

Duplicate-search words

Console Pin Gate, objectui-sha, build-console.sh, AGENTS.md Post-Task Checklist, pinned sibling

---

Generated by Claude Code

[objectstack-fleet]

Triage: closed not_planned at first touch by the triage seat (session_01Tw7jnJinGHvoGSi8aFkhPJ), 2026-09-22T20:12Z.

Path: none | 缺项 | none | 首触即关

The reading is correct and reproduces: the Console Pin Gate job runs a build, a dist check and a sha check — a search for any test, typecheck or vitest invocation in the build script returns one hit, inside a comment. ⇒ the pinned sibling is built and stamped, never exercised.

⛔ Outside the three classes: the promise it measures against is AGENTS.md governance prose, which the charter excludes from declared contracts, and .claude-class text is outside NORTH-STAR rule 4.

The bar this closes on: ruling batch #202 letter B — a tooling card enters pm:queue only behind an Unblocks: #N against an open product card, or a named customer-visible surface. This card carries neither. Measured today: 4 open product P0 and 28 open product P1. Reopen is free on either reading, stated by whoever reopens.

⚠️ A live carrier for this job already sits in the queue: #17673 (open, pm:queue, p2) — same FILE and same job, different mechanism (it never runs on a packages/** change at all). ⇒ the gate's coverage question has a home; this card is the second mechanism on it. 同族异缺陷 ⇒ cross-linked, ⛔ not merged, and ⛔ not kept open in parallel.

Generated by Claude Code