[finding] `Check Changeset`'s clause-② level rule is PR-scoped but the fact it judges is package-scoped — a PR that widens package A is refused for grading package B `patch`, where B only received a comment

[huangyiirene]

Filed by the domain:spec execution PM seat (session session_01T6HeZvT9wdSJD1ZxJb5Eno, seat post #6017), from two live reds in one dispatch round rather than from inspection. ⛔ No severity asserted, no domain routing — that is triage's. ⛔ Nothing was routed around: both PRs are complying with the gate as written, and this card exists so that compliance is not silently mistaken for agreement.

The rule, as the gate states it

⛔ This PR declares clause-② YES and grades a package it grew `patch`.

A purely additive widening of a published package's public surface takes AT LEAST `minor`;
the commit type may raise a bump but never lower it below what the act requires (maintainer
ruling 2026-09-04, decision batch #35, on #15294 — written out in full under "WHICH LEVEL" in
the `Check Changeset` step of .github/workflows/pr-automation.yml).

⭐ The rule itself is right and this card does not contest it. What it contests is the scope the predicate applies it at.

The two readings, from one round

PR #16342 (card #15963) — job 101507317157… no: job 101504990504, run 34040033277, 14:43:46Z:

   .changeset/stack-refusal-envelopes.md
     - @objectstack/spec: patch      ← this PR moves @objectstack/spec's packages/*/src/**
     - @objectstack/runtime: patch   ← this PR moves @objectstack/runtime's packages/*/src/**

⇒ Correct fire. That PR adds six new published STACK_* error codes to @objectstack/spec (measured by its at-tier reviewer: present in dist/index.js and dist/index.mjs, absent from .d.ts, unrenamable once shipped without breaking catch (e) { switch (e.code) … }). It is exactly the additive widening the rule is about, graded patch. ⇒ raised to minor. No complaint.

PR #16347 (card #16106) — job 101507317157, run 34040888070, 15:00:35Z:

   .changeset/spec-preset-comparand-message-tsdoc.md
     - @objectstack/spec: patch   ← this PR moves @objectstack/spec's packages/*/src/**

⇒ Fires on the wrong package. In that PR:

package	what the diff does to it	changeset	gate's verdict
@objectstack/lint	the actual widening — a new field-typed refusal arm on filter-preset-comparand that narrows the publish/lint accept set on a declared date/datetime field (maintainer ruling 1′, #16106 comment 5557019138)	minor	accepted, not named
@objectstack/spec	one TSDoc comment at date-range-presets.ts:101, re-worded because the shared message's applicability moved. No schema change, no export change, no accept/reject change	patch	⛔ refused

The @objectstack/spec edit is not "a purely additive widening of a published package's public surface" by any reading. It publishes — the implementer measured that the TSDoc reaches 2 non-map dist files (.d.ts / .d.mts) against a control of a known .describe() string at 18 files, which is why a changeset is owed at all — but publishing a corrected comment is not widening a surface.

The shape of the gap

Clause ② is declared once, for the PR. The carrier (needs:contract-review) is a PR-level label; the Clause-②: line is a PR-body line. The gate then applies the level rule to every package the diff touches src/** of. So a PR that legitimately widens package A and merely comments in package B must grade B minor too, or go red.

That is not a tolerance question and ⛔ must not be fixed by adding one — the gate's own text forbids that, correctly. It is a scope mismatch: the declaration is PR-scoped, the act it licenses is package-scoped, and the predicate joins them at the wrong level.

⛔ What I am NOT proposing

⛔ No tolerance, no allowlist, no "skip if the diff is comment-only" — a comment-only heuristic is exactly the kind of predicate that goes quiet on the case it was built for, and this repo has three cards open this week about instruments that under-read (#16304, #16306, #16307).

Directions that keep the rule intact, ⛔ none chosen here:

1. Make the declaration package-scoped. A Clause-②: yes (@objectstack/lint) spelling, or a per-package line, so the gate applies the level rule only to the named package(s). Costs a spelling change and a migration of existing declarations.
2. Keep the PR-level declaration and derive the widened package. The gate already knows which packages the diff moved; the missing half is which of them the clause-② act applies to. That is content-judged — the same thing dispatch-gates.mjs says a path cannot answer for clause ② itself — so it likely has to be declared, which collapses into direction 1.
3. Accept the coarseness deliberately and write it down. minor on a package that only received a comment is close to free here: the reviewer of fix(spec): every defineStack refusal carries an ADR-0112 envelope — six STACK_* codes beside STACK_CROSS_REFERENCE_INVALID #16342 measured 120 minor / 125 patch pending and all 69 packages in one fixed group, so the released bump is set by the highest pending changeset anyway. If that is the answer, the gate's message should say so, because today it asserts a premise ("a purely additive widening") that is false for the PR it is refusing, and a reader who checks the premise finds it does not hold.

⭐ Direction 3's cost is not the version number — it is that a false premise in a refusal message trains readers to stop checking premises. That is the same failure class as a stale docblock, one layer up.

What both PRs are doing meanwhile

Complying. #16342 raises both packages to minor; #16347 raises @objectstack/spec to minor and records in its body that the bump is gate-required, not semantically earned, and that the widened package is lint. ⛔ Neither weakens its clause-② declaration to fit the level (the gate's direction 2), because in both cases the declaration is right.

⚠️ A second, separable observation from the same round

The gate reads clause-② from the carrier label OR a Clause-②: line in the PR body. When an at-tier review passes and the review seat correctly strips needs:contract-review from the PR, the gate loses its only signal on any PR whose body has no declaration line — and a subsequent re-run comes back green because it has nothing to judge, not because the level was fixed. I did exactly this to #16342 at 15:11Z in the ordinary course of carrier discipline, and the re-run it triggered is not trustworthy.

⇒ Whatever happens to the scope question, a PR-body Clause-②: line should probably be required rather than optional for any PR the carrier was ever hung on, so the declaration outlives the carrier. Both PRs above are adding one. Whether that belongs on this card or its own is triage's call.

---

Generated by Claude Code

[huangyiirene]

Two measurements from the same round — one refines my own wording above, one is a new and sharper defect

domain:spec PM 派发席(session_01T6HeZvT9wdSJD1ZxJb5Eno),2026-09-06T15:2xZ. Both were taken by the #15963 implementer running the gate's own script offline with --event payloads, and both are readings rather than arguments.

---

1. ⛔ Correcting myself: the blind gate says so — it does not silently pass

My "second, separable observation" above says a re-run after the carrier strip "comes back green because it has nothing to judge". That is half right and the half I got wrong matters. Measured, three states on the same commit (273247e56f, still carrying the patch the gate refused):

event payload	exit	what the log says
Clause-②: yes in the body, no carrier label	1	⛔ "…grades a package it grew patch" · declaration line: Clause-②: yes — fires on the body line alone
neither carrier nor body line	0	LEVEL AXIS: NOT MEASURED
(on the fixed head) body line, no carrier	0	✓ LEVEL AXIS: … no package … is graded patch

⇒ The gate is honest when blind: it prints LEVEL AXIS: NOT MEASURED rather than a green verdict. That is the good design and I should have checked before writing "green" — a zero-with-a-reason is not the same failure as a false pass, and conflating them is the same sloppiness this card is about.

The real defect is one layer out: the check-run conclusion is success in both the "judged and passed" and the "had nothing to judge" cases. A reader who opens the log can tell them apart; a reader who reads the conclusion — which is what the merge queue, the required-check set, and every summary view read — cannot. ⇒ the honest fix is probably that NOT MEASURED should not conclude success, or should be visible in the check-run's own output/summary rather than only in step logs.

2. ⭐ New, and it makes the durable-declaration remedy only half work

.github/workflows/pr-automation.yml triggers on [opened, synchronize, reopened, labeled, unlabeled], and its Check Changeset job skips label events. There is no edited trigger.

⇒ A PR-body edit that adds the durable Clause-②: line is never re-read by the gate until the next synchronize — i.e. until someone pushes a commit.

Measured live on both PRs of this round:

• feat(lint): field-typed equality/membership arm for filter-preset-comparand on declared date/datetime fields #16347: the passing run's event payload was the push at ~15:22:05Z, which predates the body edit at 15:22:26Z. So CI judged on the carrier alone and had not yet seen the standalone line. The implementer confirmed the line by running the script offline against the same head with the edited body.

• fix(spec): every defineStack refusal carries an ADR-0112 envelope — six STACK_* codes beside STACK_CROSS_REFERENCE_INVALID #16342: getting CI to actually read the line required a deliberate git merge origin/main after the body edit, purely to produce a synchronize. Its run 34042090196 (job 101510576899, 15:23:13Z) then printed, verbatim:

  ✓ LEVEL AXIS: this PR declares clause-② `yes`, and no package whose `packages/*/src/**` it moves is graded `patch`.
  · carrier: `needs:contract-review` is not on this PR (4 label(s) read)
  · declaration line: `Clause-②: yes`
  

  — the first measured pass in this round where the gate read the body line with the carrier already correctly cleared.

⚠️ The failure mode this creates: a seat that does the right thing in the wrong order — strip the carrier after an at-tier PASS, then add the Clause-②: line, then stop — leaves the gate at NOT MEASURED / success with a declaration sitting in the body that the gate has never read. The remedy I proposed above (require the body line) does not work on its own; it needs either an edited trigger, or the line to be present from the PR's first push.

⇒ Cheapest reading: the Clause-②: line belongs in the PR body at creation time, written by the dev opening the PR, not added later by the seat clearing the carrier. That also matches where the declaration comes from — the claim comment — rather than where it was being patched in.

---

⛔ Still choosing none of the directions in the card body; these two readings narrow which ones can work. Both PRs are complying and neither routes around anything.

---

Generated by Claude Code

---

Generated by Claude Code