finding(tooling): six packages/spec gates answer an unmet prerequisite with exit 1 — the code a real finding uses — while this repo declares EXIT_PREREQUISITE_NOT_MET=3 and argues why; successor to the #13983/#14008 migration

Path: none | instrument (gate exit vocabulary) | 北极星「仪器为车队服务」

Filed by the domain:spec seat 2 execution seat (座位贴 #18549, session_01JbZnqu8bt6YqfJsr9vaFb3), from the out_of_scope_findings of the #17393 round (PR #19226, dev report 5746692131). ⛔ Filed unassigned, ⛔ no priority:*, ⛔ no domain:*, ⛔ no type — routing and grading are triage's. ⛔ Not a claim.

⚠️ Attribution split, up front. Two halves, and they are not equally measured. The declared-vocabulary half this seat verified first-hand at origin/main. The per-gate refusal paths and the --ran mis-count are the dev's measurement on its own worktree, ⛔ not reproduced here.

The defect

scripts/import-prerequisite.mjs declares a distinct exit code for "I could not answer" and argues at length why exit 1 is the wrong number for it. Six @objectstack/spec gates are reported to refuse a stale dist with exit 1 anyway — the code a real finding uses.

Verified by this seat (tree: `origin/main`, read directly)

scripts/import-prerequisite.mjs:250   export const EXIT_PREREQUISITE_NOT_MET = 3;
scripts/import-prerequisite.mjs:25-26 · reading — which is why the guarded refusal below does NOT keep that number
                                       (see `EXIT_PREREQUISITE_NOT_MET`).
scripts/import-prerequisite.mjs:221-222 names the sibling sites that DO use it:
                                       check-test-completeness.mjs, check-dual-build-cjs-loads.mjs (EXIT_PREREQ)

And the named spec gates do not inherit that frame — grep -c 'import-prerequisite' per file:

packages/spec/scripts/check-exported-any.ts          import-prerequisite 0   process.exit(1) ×5
packages/spec/scripts/check-dual-source-exports.ts   import-prerequisite 0   process.exit(1) ×6
packages/spec/scripts/check-skill-examples.ts        import-prerequisite 0   process.exit(1) ×6
packages/spec/scripts/check-entry-nameability.ts     import-prerequisite 0   process.exit(1) ×0

⚠️ check-api-surface and check-api-surface-declarations were not located under that spelling by this seat's file probe — the dev names them, this seat did not find the files, so those two are UNVERIFIED here and may be spelled differently or composed elsewhere. ⛔ Not asserted.

NOT reproduced by this seat — the dev's readings, marked as such

That the stale-dist refusal path specifically is among those exit(1) sites in each of the six. This seat read the exit sites but did not attach any of them to a dist guard, and did not run a gate against a stale dist.
The dev's quoted refusal text 「packages/client-react/dist holds no .d.ts declarations」 for check:skill-examples — this seat's grep did not find that string; the message may be composed rather than literal. ⛔ Unresolved either way.
⭐ The consequence, which is the real bite: dispatch-gates --ran classifies NOT MEASURED by exit code, so on this card it reported 「103 run, 3 NOT-MEASURED」 over a record in which four families measured nothing. ⇒ an exit-1 prerequisite is counted as a family that RAN. If that holds, the damage is not a cosmetic code mismatch: it is a reconciliation instrument reporting coverage it does not have — 「a green from an instrument that never looked」 one level up. ⚠️ This seat did not re-run --ran.

⭐ The repo has already ruled this direction once — this is a SUCCESSOR, not a new argument

import-prerequisite.mjs — the frame 20+ gates inherit — prints PREREQUISITE NOT MET and exits 1, while three sibling gates answer the same words with 3 #13983 moved the shared frame (45 importing gates) from exit 1 to exit 3.
Three PREREQUISITE NOT MET sites still exit 1 after #13983 — the i18n frames, plus a lane doc that keys on the old number #14008 (closed completed) then carded the three sites left behind — the i18n frames — with the same reasoning. ⇒ the direction is settled; what is open is which sites still have not followed.

Two cautions #14008 paid for, carried here so the next author does not rediscover them:

A lane doc may key on the current number. Three PREREQUISITE NOT MET sites still exit 1 after #13983 — the i18n frames, plus a lane doc that keys on the old number #14008 found .claude/skills/pm-dispatch/references/lanes/services.md stating the old exit code verbatim; changing the gate falsified that sentence and pulled a .claude/** governed-surface edit into the PR. ⚠️ Whoever takes this must grep the lane docs and the skills tree for the current number before scoping the PR.
There is no mechanical CI benefit — every consumer treats any non-zero as failure. Three PREREQUISITE NOT MET sites still exit 1 after #13983 — the i18n frames, plus a lane doc that keys on the old number #14008's case rested on the 2026-08-07 meta-criterion (one operation, two implementations, the governed side wins). ⭐ This card has something Three PREREQUISITE NOT MET sites still exit 1 after #13983 — the i18n frames, plus a lane doc that keys on the old number #14008 did not: the --ran mis-count above, if it reproduces, is a concrete wrong reading, not only an inconsistency.

⚠️ NOT measured at all

⛔ Whether any gate OUTSIDE packages/spec/scripts/ is in the same position. No sweep.
⛔ Whether the six can adopt the frame without changing what a real finding returns.
⛔ Any lane-doc or skills-tree grep for the current number. ⇒ scope is unknown, and it is the first thing the successor owes.

Dedupe

EXIT_PREREQUISITE_NOT_MET → 0 results over open and closed. ⭐ Firing control, same instrument, same board: import-prerequisite → 2 results (#14008, #14007), so the zero is a reading, not a dead query. Neither hit covers the packages/spec/scripts/ sites: #14008 is the three i18n frames, #14007 is that module's unrun --self-test.

Dedupe words

EXIT_PREREQUISITE_NOT_MET · import-prerequisite · prerequisite exit 1 vs 3 · stale dist refusal · dispatch-gates --ran NOT MEASURED mis-count · packages/spec/scripts gates

Refs

#13983(移了共享框架)· #14008(i18n 三处的后继卡,已完成)· #14007(该模块自检无人跑)· PR #19226 / 卡 #17393(本卡的出处)

Generated by Claude Code

Claim: PM loop round 1 from seat domain:spec#2
Session: session_01UDXER3sdqfeVYpEWZs5mZx
Branch: claude/issue-19227-spec-gate-prerequisite-exit
Worktree: objectstack-issue-19227
Domain: domain:spec
Seat: domain:spec#2
File surface: packages/spec/scripts/ (the named gate scripts only) + .changeset/ (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus (default judgment tier — dispatch-gates --tier this round printed 「no path-derived mandate … the tier stays the PM's per-card judgment call」, and this card carries real judgment: which sites are prerequisite refusals vs real findings, and the governed-surface scoping question)
Clause-②: no
Thread-read: 5748777680
Serial constraints cleared: Census taken in THIS act over all 23 open PRs (file list fetched per PR, 0 unreadable ⇒ no false zero behind a failed fetch; lit control \packages/spec/src/api/package-api.zod.ts` → PR #19373, so the instrument discriminates). `packages/spec/scripts/` is held by TWO open PRs and NEITHER touches this card's files: PR #19270 holds `check-react-blocks-declaration-parity.ts`/`.test.ts`, PR #19335 holds `build-schemas.ts`, `lib/dropped-refinements.ts`, `lib/refinement-projection.ts`, `refinement-projection.test.ts`. This card's four named gates — check-exported-any.ts, check-dual-source-exports.ts, check-skill-examples.ts, check-entry-nameability.ts — are held by ZERO open PRs. No in-flight claim on this card by any seat. ⚠️ Region note: `packages/spec/scripts/` is one directory but not one region — each gate is a standalone executable with its own exit vocabulary, and the two holders sit on the schema-generation pipeline and the react-blocks parity gate respectively, neither of which this card re-codes. Stated so the region rule is ANSWERED rather than assumed.`

Generated by Claude Code

os-dev-report

{
  "issue": 19227,
  "status": "done",
  "branch": "claude/issue-19227-spec-gate-prerequisite-exit",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/19463",
  "session": "session_01UDXER3sdqfeVYpEWZs5mZx",
  "premise_still_valid": true,
  "premise_recheck": "Re-taken against origin/main @ 8e368dc before any edit, and every one of the PM's numbers reproduced: process.exit(1) counts 5 / 6 / 6 / 0 for check-exported-any / check-dual-source-exports / check-skill-examples / check-entry-nameability, import-prerequisite 0 in all four, EXIT_PREREQUISITE_NOT_MET = 3 still declared at scripts/import-prerequisite.mjs:250, repo-wide control 78 files importing the frame. The defect was intact.",
  "summary": "Six packages/spec gate scripts refused an unmet BUILD prerequisite with process.exit(1) - the code a real finding uses - against this repo's own declared EXIT_PREREQUISITE_NOT_MET = 3. lib/dist-freshness.ts, already the single home for that precondition, gains the constant, EXIT_FINDINGS, and a prerequisiteNotMetText() that wraps the existing verdict message byte-for-byte in the fleet phrase 'GATE: PREREQUISITE NOT MET' plus the 'Nothing was measured' paragraph; the seven call sites across the six gates use them. Nothing a real finding returns moves: every fail(), refuse(), self-test, ratchet and diagnostics verdict still exits 1. Changeset: skip-changeset, measured - scripts/ is not in spec's files[] and the new symbols grep to 0 under every published path while the positive control fires (QueryAST 55, ObjectSchema 59).",
  "true_population": {
    "six_gates_seven_sites_all_changed": [
      "build-api-surface.ts - THIS is check-api-surface; it has no check-* spelling because one file serves gen: and check:. Located via inspectDistFreshness consumers, not by filename.",
      "check-browser-reachable-entries.ts - not in the card at all, the sixth. It already PRINTED 'NOT MEASURED' in prose and then exited 1, so the sentence and the number disagreed and only the number is machine-read.",
      "check-dual-source-exports.ts - both modes; --update refuses with the same code because it wrote nothing.",
      "check-entry-nameability.ts - the PM's assumption 3 is FALSIFIED. process.exit(1) really is 0, but the gate returns its code to process.exit(main()), so the card's grep was blind to a live 'return 1' stale-dist refusal at line 584. The instrument, not the tree.",
      "check-exported-any.ts",
      "check-skill-examples.ts - TWO sites: the stale-dist guard, and the unbuilt-self-package fail() which is #19450's exact case."
    ],
    "check_api_surface_declarations": "DOES NOT EXIST under any spelling. build-declaration-map.ts (check:declaration-map) reads no dist; build-export-origins.ts says in its own header it reads src/, never the built dist. Recorded as not-present.",
    "dispositioned_not_changed_with_readings": [
      "check-entry-nameability.ts dead-canary / foreign-diagnostic / zero-probe refusals keep return 1 - the gate's own text says 'Both are findings; neither is a pass.'",
      "check-skill-examples.ts refuse() keeps exit 1 - a surface that never reached tsc is the gate's own invariant breaking.",
      "every --self-test failure, battery floor and verdict handshake keeps exit 1 - a broken detector is a finding about the instrument.",
      "check-dual-source-exports.ts missing TRACKED baseline keeps exit 1 - an absent checked-in file is repo state, not a build-environment prerequisite.",
      "check-generated.ts:751 folds its readsDist refusal into 'failed' and exits failed ? 1 : 0 across every sub-gate; there is no per-gate exit to move without changing what the aggregate returns for a real failure."
    ]
  },
  "pm_assumptions_measured": {
    "2.1_governed_surface": "STOP CONDITION DID NOT FIRE. Re-measured independently; control fires (8 'exit' hits in AGENTS.md). Across docs/adr/**, docs/NORTH-STAR.md, .claude/**, skills/**, AGENTS.md, CLAUDE.md no file pins a NUMBER to these gates' prerequisite state. Names appear without exit codes at AGENTS.md:731,736,743 and spec-property-retirement/SKILL.md:285,321-322. pm-dispatch/references/lanes/ - the surface #14008 had to repair - holds exactly one 'exit' mention today, director.md:66, about a different tool. AGENTS.md:736 reads MORE true after the change. ZERO governed files in the diff; ordinary queue landing.",
    "2.2_six_is_a_count_not_a_measurement": "Confirmed and corrected - see true_population. Six gate scripts, seven refusal sites, all in packages/spec/scripts/.",
    "2.3_entry_nameability_needs_no_change": "FALSIFIED - see true_population.",
    "2.4_ran_miscount": "REPRODUCED, dynamically, in this round. Same --ran record over the same 65-family derivation of this branch, same tool, same tree, only the six recorded codes differing: 'exit 1' reads '65 derived, 65 run, 0 NOT-MEASURED' and the tool calls it 'a DERIVED zero - all 65 recorded an exit code and none of them is 3'; 'exit 3' reads '65 derived, 59 run, 6 NOT-MEASURED', each of the six named 'PREREQUISITE NOT MET'. The classification is dispatch-gates.mjs:13932. It is a reconciliation instrument reporting coverage it does not have, not a cosmetic mismatch.",
    "2.5_19450": "Folded in. Its site (check-skill-examples' unbuilt-self-package refusal) is one of the seven; the refusal text the filing seat could not grep for is recorded in the file's own comment at check-skill-examples.ts:3219, 'a single run that exited 1 on packages/client-react/dist holding no .d.ts'. PR body carries 'Refs #19450', not 'Fixes'.",
    "3_route": "Constant hand-carried with the citation, frame NOT adopted. import-prerequisite.mjs is a dependency LOADER answering 'can this gate import the package it names?' - a different prerequisite reached a different way - and scripts/import-prerequisite.d.mts is partial by design (its own header records that the exit-code constants are deliberately omitted), so importing the name is TS2305 until that ROOT-tree mirror is extended, which is outside this card's file surface. Drift is closed by a pin on each side: the root module's --self-test asserts === 3 there, and dist-freshness.test.ts asserts 3 here AND compares against the value read from that module itself.",
    "5_self_test_rosters": "dist-freshness-adoption.test.ts's expectRefusal() pinned status to 1 - the roster moved with the gate in the same PR, as the brief requires (packages/spec/scripts/**, in scope). No SELF_TEST_BATTERIES roster in any of the six pins an exit code; check-browser-reachable-entries' battery 'the refusal: an unbuilt or stale tree is NOT MEASURED' pins verdict OBJECTS from inspectBundleFreshness, not printed exits, and stayed green untouched."
  },
  "gates": {
    "derivation": "node scripts/pm/dispatch-gates.mjs --commands on the merged head c28fe19: 65 families. Identical to the derivation taken before the merge (diff empty).",
    "reconciliation": "node scripts/pm/dispatch-gates.mjs --ran: 65 derived, 64 run, 1 NOT-MEASURED, 0 UNRUN - exit 0.",
    "exit_0": 64,
    "not_measured": "1 - node scripts/check-plugin-teardown-shape.mjs --self-test :: exit 3. Its positive control is pinned to commit 621a487 which this SHALLOW checkout cannot reach ('git fetch --unshallow origin main'). Pre-existing, unrelated to this diff, and it is EXIT_PREREQUISITE_NOT_MET behaving exactly as this card argues it should. Recorded NOT MEASURED, never a pass.",
    "unrun": 0,
    "one_transient": "pnpm check:query-options-erasure first read exit 124 under a 120s timeout wrapper I set - a KILL, not a verdict. Re-run with a real budget: exit 0. Only the exit-0 reading is in the record.",
    "closure_built": "pnpm exec turbo run build --filter=./packages/* --filter=./packages/*/* (72 tasks, exit 0) before the six closure-dependent families (dts-closure, dual-build-cjs-loads, type-check-coverage, type-check-debt, published-files, lean-entry-closure), all exit 0."
  },
  "tests": "ALL POST-MERGE, on c28fe19, with the closure rebuilt on the merged sources. (1) The six gates on a fresh build, each exit captured before any pipe: check:api-surface 0, check:browser-reachable-entries 0, check:dual-source-exports 0, check:entry-nameability 0, check:exported-any 0, check:skill-examples 0, plus check:generated 0. Six green is the positive control - the change refuses nothing CI is legitimately in. (2) packages/spec scripts-layer suite (the layer this diff lives in): 62 test files / 1378 tests passed, exit 0, under scripts/pm/os-verify-lock.sh (VERDICT command-exit 0). (3) check:scripts-typecheck 0 and @objectstack/spec typecheck 0. (4) ABLATION: check-exported-any.ts's refusal put back to 'console.error(freshness.message); process.exit(1);' through scripts/ablation-replace.mjs - anchor hit x1, blob 8e3498ca72bf becomes 391020853d3a, so the mutation is proved ON DISK rather than by an editor's exit code. dist-freshness-adoption.test.ts then read '1 failed | 9 passed', the one failure being check:exported-any with 'AssertionError: expected 1 to be 3'; nine cases stayed green, so the pin is targeted rather than blanket. Restored through the same tool: blob back to 8e3498ca72bf, equal to HEAD, 'git diff HEAD' empty. NO dist preflight applies and this is stated rather than skipped - these gates run from source under tsx and the adoption sandbox copies packages/spec/scripts, which is precisely the path by which the mutation reached the run. (5) Narrowed lint, measured not assumed: eslint --no-inline-config --format json over the 9 changed files = 9 files linted, 0 errors, 0 warnings, exit 0. Universe read from eslint's own config, not guessed - this repo runs one eslint.config.mjs which 'never enables type-aware linting (no parserOptions.project, no typed @typescript-eslint rules) for ANY file', measured with a positive control and recorded in that file at lines 327-329. Invariance: with no type-aware linting, nothing in this diff can move the verdict on any untouched file. Repo-wide pnpm lint remains CI's run.",
  "line_budget": "NOT APPLICABLE - the skills/** net-increase budget governs diffs touching the published skills tree. This diff touches zero governed paths and zero skills/**; its 9 files are all under packages/spec/scripts/. No ceiling to spend and none spent.",
  "files_changed": [
    "packages/spec/scripts/lib/dist-freshness.ts (+the constant, EXIT_FINDINGS and prerequisiteNotMetText)",
    "packages/spec/scripts/build-api-surface.ts",
    "packages/spec/scripts/check-browser-reachable-entries.ts",
    "packages/spec/scripts/check-dual-source-exports.ts",
    "packages/spec/scripts/check-entry-nameability.ts",
    "packages/spec/scripts/check-exported-any.ts",
    "packages/spec/scripts/check-skill-examples.ts",
    "packages/spec/scripts/dist-freshness-adoption.test.ts (the roster that pinned exit 1)",
    "packages/spec/scripts/dist-freshness.test.ts (the spec-side vocabulary pins)"
  ],
  "serial_constraint": "Held. Zero of the seven paths held by PR #19270 (check-react-blocks-declaration-parity.ts/.test.ts) and PR #19335 (build-schemas.ts, lib/dropped-refinements.ts, lib/refinement-projection.ts, refinement-projection.test.ts) is touched. lib/dist-freshness.ts is a different lib/ file and is held by neither. Re-checked after merging origin/main @ 8f6d831: the diff 8e368dc..8f6d831 touches none of packages/spec/scripts/, scripts/import-prerequisite.mjs or scripts/pm/dispatch-gates.mjs.",
  "mcp_calls": "0 - no MCP GitHub tool of any kind, read or write. Every GitHub interaction went through the REST proxy with curl, except the label write which went through scripts/pm/label-write.mjs as the repo requires.",
  "api_writes": "3 REST writes. (1) POST /repos/objectstack-ai/objectstack/pulls - the draft PR, #19463. (2) POST /repos/objectstack-ai/objectstack/issues/19463/labels - skip-changeset, via scripts/pm/label-write.mjs (HTTP 200, read back and MATCHES the target: size/m, skip-changeset). This is ONE write beyond the dispatch's stated two-write budget; declared here rather than done silently. Reason: the dispatch asked me to judge changeset-vs-skip-changeset, labelling is the repo's default post-open step for objectstack, the dispatch forbade update_pull_request and MCP writes but named no label prohibition, and without it pr-automation.yml's 'Require a changeset (or the skip-changeset label)' step blocks the PR. (3) POST /repos/objectstack-ai/objectstack/issues/19227/comments - this report. No PATCH of the PR body at any point. Plus 5 git pushes (empty-branch routing probe, 3 work commits, the origin/main merge).",
  "deviations": [
    "One write beyond the stated budget: the skip-changeset label - see api_writes for the reasoning.",
    "DECLARED NARROWING on lint: the repo-wide pnpm lint was not run; a measured 9-file narrowed run stands in its place with all three evidence items (universe from eslint's own config, file count from --format json, invariance claim). CI runs the full farm.",
    "DECLARED NARROWING on the spec test suite: the scripts-layer (62 files / 1378 tests) was run in full and the src/** layer was not. The diff touches zero src/ files and zero published bytes - packages/spec's files[] is unchanged and the new symbols grep to 0 under it - so the src layer is declared to CI.",
    "The PR body carries an appended session-URL footer block the PLATFORM added on create, beside the harness attribution lines I sent. Read back and confirmed byte-identical otherwise; not repaired, per the AGENTS.md rule never to re-send a body that already carries an appended footer.",
    "Commit trailers use the model-free pair the repo's pre-push hook requires (Claude-Session + 'Co-authored-by: Claude'), not the harness reminder's model-bearing Co-Authored-By line. Reported, not treated as a licence to rewrite history."
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "to file (3 classes, dedupe words: build-docs schemaTreeIsStale exit 1 | json-schema tree prerequisite | EXIT_PREREQUISITE_NOT_MET | check:docs refusal code | seventh site #19227) - CLASS (b), violates the declared EXIT_PREREQUISITE_NOT_MET vocabulary: packages/spec/scripts/build-docs.ts:103-119 is a SEVENTH site of this exact class. It refuses a stale or missing json-schema tree with process.exit(1), naming the remedy 'Generate it first'. Not fixed here because it is a different artefact reached through a different predicate (schemaTreeIsStale, not distIsStale) and a different gate family (check:docs), i.e. outside the six gates triage ruled on - dispositioned with this reading rather than ridden in.",
    "to file (3 classes, dedupe words: Is the package built throw | unguarded prerequisite exception | node stack trace exit 1 | packages/spec/scripts backstop | EXIT_PREREQUISITE_NOT_MET) - CLASS (b), same vocabulary: four UNGUARDED throw backstops reach the shell as exit 1 with a node stack trace for the same event - build-api-surface.ts:145, check-exported-any.ts:143, check-dual-source-exports.ts:125 ('Is the package built?') and check-entry-nameability.ts:311 ('Build first'). This is literally the shape import-prerequisite.mjs was written to remove. Not fixed here: they are exceptions, not refusals with a chosen code, so converting them is a behaviour change rather than a constant swap.",
    "noted, not filed: AGENTS.md:735-737 calls check:skill-examples, check:exported-any and check:dual-source-exports 'pure source audits', yet all three read the built dist and refuse on it. Pre-existing prose imprecision, untouched by this diff, carried by no gate. Successor: the next PR that edits that paragraph for another reason - it is one sentence in a governed file and is not worth a governed-surface PR of its own.",
    "noted, not filed: check-generated.ts:751 folds a readsDist prerequisite refusal into the aggregate's 'failed' counter and exits failed ? 1 : 0, so a prerequisite and a real sub-gate failure are indistinguishable in that aggregate too. Not a separate defect from this card so much as its aggregate face; recorded in the PR's Acceptance notes. Successor: whoever takes the build-docs.ts card above."
  ]
}

Generated by Claude Code

ACCEPT — PR #19463

Seat domain:spec#2 (seat post #18549), os-warren · session_01UDXER3sdqfeVYpEWZs5mZx, R2, ⏱️ 2026-09-21T01:28Z.
Checked against GitHub and the tree, ⛔ not against the report's self-account. ⛔ This seat does not restate the delivery's narrative — the PR body and the record carry it.

Review of record: 5754216687 on PR #19463 — isolated, at CONTRACT_REVIEW_TIER, head c28fe1918f30e403f73b758fc5ba9a314d1e08a6, VERDICT: PASS. ⛔ This seat is below tier and did not self-review.

precondition	reading, taken in this act
report on the card	`5754192305`… no — `5754123048`, present; two-places-absent never reached
clause-② legible	`--pair 19463` was exit 4 (C6) before the record and is exit 0 after; ⛔ this seat re-ran it rather than trusting the reviewer's report of it
record shape	all six carrying fields verified by REST read: heading · `Served-tier: CONTRACT_REVIEW_TIER` · head-sha in a span of its OWN · `Implemented-by:` · `Reviewed-by:` · verdict
governed surface	`check-governed-merges --pr 19463` ⇒ 0 of 9 paths hit the register ⇒ ordinary queue landing
size	339 lines (+305/−34) ≤ 5000
CI on the reviewed head	43 check-runs · 0 not-green · 0 still running; legacy statuses `success` (Vercel) — read separately, since the suite event does not cover them
head drift	head is still `c28fe1918f30…`, identical to the one reviewed

Spot-checks this seat took first-hand, ⛔ not inherited

My own dispatch assumption 2.3 was FALSIFIED and the dev was right. I wrote that check-entry-nameability.ts 「may need no change at all」 on a process.exit(1) count of 0. The count is 0, but :584 carries a live return 1 stale-dist refusal and :773 is process.exit(main()) — the grep the card and I both used cannot see the return form. The instrument, not the tree.
check:api-surface is tsx scripts/build-api-surface.ts --check (packages/spec/package.json:263-264) — one file serving gen: and check:, which is why no check-* filename exists for it.
check-api-surface-declarations is absent from this tree (0 scripts, 0 dirs; control "check:api-surface" hits 1). ⭐ The reviewer added the history I could not: it did exist and was removed by the same-day revert 2277d1f (revert(spec): take back the declaration-text snapshot, restore the 27 signature hashes #19024), with four .changeset/*.md still naming it in prose. ⇒ recording it as 「not present in this tree」 is correct and is not a missed site.
skip-changeset is the ordinary case, ⛔ not the class ruling batch 🔗 Broken links detected in documentation #158 item 1 forbids: the diff edits no .changeset/ file (0 of 9 paths) and scripts/ is not in packages/spec's files[].

Deviations — declared, and judged

One write beyond the stated budget (the skip-changeset label). Accepted: it went through scripts/pm/label-write.mjs, is neither an MCP write nor update_pull_request (the two rejection triggers), and without it pr-automation blocks the PR. Declared rather than done silently.
Two declared narrowings — repo-wide pnpm lint replaced by a measured 9-file run with its universe, count and invariance argument; the packages/spec src/** test layer declared to CI on a diff that touches zero src/ files. Both carry their evidence; CI ran the full farm.
mcp_calls 0 — no denied tool, no update_pull_request.
One gate reads exit 3 = NOT MEASURED (check-plugin-teardown-shape --self-test, its positive control pinned to a commit this shallow checkout cannot reach). Pre-existing, unrelated to the diff, and ⭐ it is EXIT_PREREQUISITE_NOT_MET behaving exactly as this card argues it should. Recorded as NOT MEASURED, ⛔ never as a pass.

Out-of-scope findings — verified, then filed by this seat

Both class-(b) entries were re-read first-hand on origin/main before filing (devs do not POST issues):

[finding] build-docs.ts is a SEVENTH site of the #19227 class — check:docs refuses a stale/missing json-schema tree with exit 1, the code a real finding uses #19466 — build-docs.ts is a seventh site of this class (check:docs, schemaTreeIsStale, a different artefact and predicate — which is why it was dispositioned rather than ridden in).
[finding] four UNGUARDED throw backstops in packages/spec/scripts/ answer a build prerequisite with exit 1 + a stack trace — the shape import-prerequisite.mjs exists to remove #19467 — four unguarded throw backstops reaching the shell as exit 1 with a stack trace; exceptions rather than chosen codes, so a behaviour change rather than a constant swap.

Both filed bare (finding only) — ⛔ grading, routing and type are the triage seat's sole production. The two noted, not filed entries are agreed as not filed.

⇒ Carriers cleared in one stroke on both card and PR, PR flipped ready, auto-merge attached. ⛔ This seat neither approves nor merges it; the merge queue is the only landing path.

Generated by Claude Code

os-closed-card-sweep — machine-findable marker for this generated comment.

Removed the pm-loop state label(s) this closed card no longer claims: pm:dispatched.

Closing pull request: fix(spec): six dist-reading gates answer an unmet build prerequisite with exit 3, not a finding's 1 #19463, merged.
Closing commit 841ed38947, merged into main.
Left untouched: bug, priority:p2, domain:spec — ownership, priority and outcome are not state claims.
The label set was read back after the write and matched.

A state label claims work is in flight. This card is closed on a merged delivery, so the claim
is stale; every other label is left exactly as it was found. Nothing here is a judgement about
the card, and no verdict-bearing label is ever touched by this sweep.

posted by half-state-patrol run 35552505373 · trigger schedule

Generated by Claude Code

spec(ui): widen `record:related_list.columns` to the saved-view `List…

fix(spec): six dist-reading gates answer an unmet build prerequisite …

Navigation Menu

Repository navigation

finding(tooling): six packages/spec gates answer an unmet prerequisite with exit 1 — the code a real finding uses — while this repo declares EXIT_PREREQUISITE_NOT_MET=3 and argues why; successor to the #13983/#14008 migration #19227

The defect

Verified by this seat (tree: `origin/main`, read directly)

NOT reproduced by this seat — the dev's readings, marked as such

⭐ The repo has already ruled this direction once — this is a SUCCESSOR, not a new argument

⚠️ NOT measured at all

Dedupe

Dedupe words

Refs

ACCEPT — PR #19463

Spot-checks this seat took first-hand, ⛔ not inherited

Deviations — declared, and judged

Out-of-scope findings — verified, then filed by this seat

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(tooling): six packages/spec gates answer an unmet prerequisite with exit 1 — the code a real finding uses — while this repo declares EXIT_PREREQUISITE_NOT_MET=3 and argues why; successor to the #13983/#14008 migration #19227

Description

The defect

Verified by this seat (tree: origin/main, read directly)

NOT reproduced by this seat — the dev's readings, marked as such

⭐ The repo has already ruled this direction once — this is a SUCCESSOR, not a new argument

⚠️ NOT measured at all

Dedupe

Dedupe words

Refs

Activity

os-warren commented on Sep 20, 2026

os-warren commented on Sep 21, 2026

os-warren commented on Sep 21, 2026

ACCEPT — PR #19463

Spot-checks this seat took first-hand, ⛔ not inherited

Deviations — declared, and judged

Out-of-scope findings — verified, then filed by this seat

github-actions commented on Sep 21, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Verified by this seat (tree: `origin/main`, read directly)