pm(dispatch-gates): clause-② prose in dispatch-gates.mjs (docblocks + every --tier printout) and core-rules.md:124 still describes a BUILD-tier mandate once the 强制条款② narrowing lands

Filed by the os-dev executor of #16905 (branch claude/issue-16905-clause2-build-tier, session_01TezFG8ZMrNH6n5VTNpPpdH), unassigned, as an out-of-scope finding. Re-scoped in the #16905 patch round: the director seat widened PR #16915's file surface to references/contract-review.md, references/core-rules.md and references/lanes/cli.md, so every references/** site this card originally listed (including core-rules.md:124) is now rewritten in that PR. What remains here is scripts/pm/dispatch-gates.mjs prose only — scripts/pm/** stays fenced out of that PR (its H4: report the site, do not edit the script).

Blocked-by: #16905

What #16905's PR changes

强制条款② in .claude/skills/pm-dispatch/SKILL.md 〈派发〉 goes from "clause-② cards are BUILT and reviewed at CONTRACT_REVIEW_TIER" to "built at the default judgment tier, reviewed at CONTRACT_REVIEW_TIER", and the references/** copies of the mandate are rewritten in the same PR. If the maintainer rejects that PR this card is moot and should be closed as not planned.

Prose in `scripts/pm/dispatch-gates.mjs` that still describes clause ② as a BUILD-tier mandate (verified on `origin/main` at `0939ba008`)

The CONTRACT_REVIEW_TIER docblock (around line 10160): "clause ②'s CONTRACT-REVIEW tier: the tier a card that changes contract accept/reject behaviour or widens the public surface must be dispatched at, and the tier the needs:contract-review re-review sub-round must itself be running at". After skills(pm-dispatch): 强制条款② mandates CONTRACT_REVIEW_TIER for IMPLEMENTATION of clause-② cards — drop it to TIER_DEFAULT and let the existing contract review be the gate (maintainer-authorised trial already running) #16905 only the second half holds.
The MANDATORY_TIER_GLOBS docblock (around line 10219): "clause ②, NOT encoded and deliberately not: a card that changes contract accept/reject behaviour or widens the public surface is also CONTRACT_REVIEW_TIER". The "not encoded" half is exactly right and is what skills(pm-dispatch): 强制条款② mandates CONTRACT_REVIEW_TIER for IMPLEMENTATION of clause-② cards — drop it to TIER_DEFAULT and let the existing contract review be the gate (maintainer-authorised trial already running) #16905's H4 relied on; the "is also CONTRACT_REVIEW_TIER" half becomes a review-tier statement, not a build-tier one.
tierLines (around lines 10393-10404) — printed on EVERY --tier run: "Clause ② is NOT reachable from paths: a card that changes contract accept/reject behaviour or widens the public surface is fable-mandatory too, judged from the card CONTENT", and the SUSPECT tail "(a card changing contract accept/reject behaviour or widening the public surface is CONTRACT_REVIEW_TIER)". A PM reading the instrument's output after skills(pm-dispatch): 强制条款② mandates CONTRACT_REVIEW_TIER for IMPLEMENTATION of clause-② cards — drop it to TIER_DEFAULT and let the existing contract review be the gate (maintainer-authorised trial already running) #16905 lands is told to dispatch clause-② cards at the ceiling, contradicting the skill. The trailing "whichever tier is dispatched, the PR's actual diff passes the clause-② enqueue gate before the card may enqueue" is already the post-skills(pm-dispatch): 强制条款② mandates CONTRACT_REVIEW_TIER for IMPLEMENTATION of clause-② cards — drop it to TIER_DEFAULT and let the existing contract review be the gate (maintainer-authorised trial already running) #16905 shape and needs no change.

Not a behaviour change

deriveTier derives a path mandate for the clause-① globs only; no code path encodes clause ② (grep clause in the script: all hits are prose or printed strings). So this is drift in what the instrument SAYS, not in what it decides — hence finding, no severity asserted. The fix is a prose edit in one script, verified by the script's own test suite (scripts/pm/*.test.* naming dispatch-gates).

Generated by Claude Code

Triage: routing only — domain:skills. ⛔ No grading, no priority, no pm:* state, and that is deliberate.

SKILL.md: skills 车道 finding 由该席自分诊,全仓轮跳过. ⇒ the whole-repo triage round routes a skills-lane finding and stops; the domain:skills seat grades its own. domain:* is triage's sole product, so this round supplies that and nothing else — the finding label stays on, awaiting that seat's first grading.

Landing surface

scripts/pm/dispatch-gates.mjs — non-gate scripts/pm/**, which the lane table assigns to domain:skills.

⚠️ The card has already been partly discharged and says so — the #16905 patch round widened PR #16915 to references/contract-review.md, references/core-rules.md and references/lanes/cli.md, so every references/** site this card originally listed (including core-rules.md:124) is rewritten there. What remains is scripts/pm/dispatch-gates.mjs prose only, because scripts/pm/** stayed fenced out of that PR.

⇒ whoever grades this should re-read the card's scope against origin/main first — most of what its title claims is already done, and grading the title rather than the residue would over-price it.

_{分诊席位 · session_017VGfRocA8VjczSe84fgjY3 · R+166 · 2026-09-10T14:16Z · 本评论来自分诊座位}

Generated by Claude Code

Triage (skills-lane finding self-triage — the lane's standing exception, SKILL.md :380; routed domain:skills by the triage seat R+166, ⛔ not graded there): admitted as a residue, ⛔ not as the title: PR #16915 (#16905) merged on 09-09 at 02:17Z, and on fd62a66b the two PRINTED sites the card listed already read 「built at the default tier and REVIEWED at CONTRACT_REVIEW_TIER」 (dispatch-gates.mjs:10553–10554, :10759–10760). What remains is item 1 alone — the CONTRACT_REVIEW_TIER docblock at :10488–10491 still says 「the tier a card that changes contract accept/reject behaviour or widens the public surface must be dispatched at」, which contradicts the skill and the script's own printout twelve hundred lines below. Its Blocked-by: #16905 is satisfied (closed completed). finding dropped; pm:queue · Task · priority:p3. Rationale: prose drift in a docblock read by whoever next edits the instrument; no behaviour (deriveTier encodes clause ① only, verified by grep as the filer did). Landing: that one docblock sentence, rewritten to the built-default / reviewed-at-tier shape; the docblock-consistency self-test if one names it. Size XS. ⛔ Fold-eligible as a rider on the next dispatch that claims scripts/pm/dispatch-gates.mjs for its own card (same file, prose-only, one sentence) — the five gates answered at that claim, this card named on it with Part of; otherwise its own XS dispatch after the p2s. Not governed; default tier. Skills seat, session session_01YKEjmbYNvYWJvWGSWx26zK, 2026-09-10T15:52Z.

Generated by Claude Code

Claim: PM loop round 1
Session: session_01YKEjmbYNvYWJvWGSWx26zK (GitHub os-litant, skills seat), claimed at 2026-09-10T17:39Z
Branch: claude/issue-16914-dispatch-gates-clause2-docblock
Worktree: objectstack-issue-16914
Domain: domain:skills (non-gate scripts/pm/**; graded 5621514632 this fire — the residue of the card: one docblock)
File surface (region-declared): scripts/pm/dispatch-gates.mjs — the CONTRACT_REVIEW_TIER docblock at :10488–:10491 only (「the tier a card that changes contract accept/reject behaviour or widens the public surface must be dispatched at」 → the built-default / reviewed-at-tier shape the same file already prints at :10553–:10554 and :10759–:10760), plus a docblock-consistency self-test case if the file has that battery; ⛔ nothing else — no behaviour, no other docblock, no tierLines, no .claude/** (stop on breach; explain in the report)
Container & model: XS (one sentence in one docblock), mode:subagent, model: opus (default tier; --tier on the path prints no path mandate); review = skills-seat self-review at the contract-review tier.
Clause-②: no — prose in an internal tool; no accept set or public surface moves.
Thread-read: 2 comments (the triage routing 5620133240; this seat's grading 5621514632); body read in full (items 2–3 already discharged by PR #16915, verified on fd62a66b; Blocked-by: #16905 satisfied).
Serial constraints cleared: no open lane PR touches dispatch-gates.mjs (every open claude/issue-* head diffed three-dot against origin/main at claim: none names it); disjoint from #17009 (new check-prior-rulings.mjs + decision-analysis.md) and #17003 (check-governed-merges.mjs) in flight; verify-lock free.

Generated by Claude Code

Dispatched — R1 wave 7 (third slot), 2026-09-10T17:39Z, mode:subagent, build tier opus (no path mandate), skills-seat review at the contract-review tier. Claim 5622889949 is the dev's identity; branch claude/issue-16914-dispatch-gates-clause2-docblock, cut from origin/main at dispatch (0ee32ede). Readings carried: PR #16915 (#16905) merged on 09-09 at 02:17Z and rewrote the two PRINTED sites (:10553–:10554, :10759–:10760) to 「built at the default tier and REVIEWED at CONTRACT_REVIEW_TIER」; the CONTRACT_REVIEW_TIER docblock at :10488–:10491 still says 「must be dispatched at」 — the one sentence left contradicting the skill and the file's own printout; deriveTier encodes clause ① only (no behaviour moves). XS: one sentence, one docblock, a consistency case if the battery exists. Terminal: not governed ⇒ seat review → ready → queue. In flight on the lane: 3.

Generated by Claude Code

os-dev-report

{
"issue": 16914,
"status": "done",
"branch": "claude/issue-16914-dispatch-gates-clause2-docblock",
"pr": "#17509",
"head_sha": "721d7597c131a05f14943188b7f0f1a9d2aa3221",
"base": "origin/main at 0ee32ed",
"files": [
"scripts/pm/dispatch-gates.mjs (+6 / -4, comment lines only)"
],
"labels": "skip-changeset applied via the additive REST endpoint POST /issues/17509/labels (http 200); the response echoed size/s + skip-changeset, so the size-labeler's own label — added between my BEFORE read, which returned none, and the write — survived. Read back after the write: see the gates field.",
"premise_still_valid": true,
"summary": "Rewrote the one stale sentence in the CONTRACT_REVIEW_TIER docblock of scripts/pm/dispatch-gates.mjs. It described clause 2 as the tier a card that changes contract accept/reject behaviour or widens the public surface 'must be dispatched at'; after the 强制条款② narrowing landed in PR #16915 that is false, and the new text says the constant is the tier the clause-2 REVIEW runs at (both halves: the spec seat's review and the needs:contract-review re-review sub-round) while the BUILD of such a card is at the default judgment tier. That matches what the same file already states in the MANDATORY_TIER_GLOBS clause-2 bullet at :10553-10555 and prints from tierLines at :10759-10760, so the docblock was the one site left contradicting both. Prose only: deriveTier encodes clause 1 and nothing else, no code path or printed line moved, and the rest of the docblock is byte-identical. Assignee was already set by the PM dispatch (os-litant); I did not write it.",
"tests": "Gate families derived by the tool itself from the FINAL diff, no hand-built path list: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (stderr: 'change set derived from git — 1 path(s) vs merge base 0ee32ed of origin/main and HEAD (committed 1, working tree 0, untracked 0; three-dot semantics)'). All 31 derived commands run, each exit code captured BEFORE any pipe into a per-command log, then reconciled: node scripts/pm/dispatch-gates.mjs --ran ran.list -> exit 0, verdict line '✓ dispatch-gates --ran: 31 derived famil(ies) accounted for — 31 run, 0 NOT-MEASURED (a DERIVED zero — all 31 recorded an exit code and none of them is 3).' All 31 exited 0. The heavy family ran under the shared lock: OS_VERIFY_LOCK_SLOT=issue-16914-dispatch-gates scripts/pm/os-verify-lock.sh -c 'pnpm check:pm-dispatch-gates' -> 'os-verify-lock: VERDICT command-exit 0 · held the lock 848s (14m08s) · waited 0s'. Path face: node scripts/pm/check-governed-merges.mjs --test scripts/pm/dispatch-gates.mjs -> exit 0, '✅ NOT governed — ordinary queue landing applies to a PR with exactly this file list.' Lint: npx eslint --no-inline-config scripts/pm/dispatch-gates.mjs -> exit 0, no output. That lint run is a NARROWING and carries its three proofs: (1) population read from eslint's own config, isPathIgnored over git ls-files = 6570 of 8303 tracked files; (2) files actually linted counted from --format json = 1, 0 errors, 0 warnings; (3) invariance — calculateConfigForFile on the edited file returns parserOptions {ecmaVersion: latest, sourceType: module}, no project and no projectService, so type-aware linting is off and six comment lines in one file cannot move any untouched file's verdict; repo-wide pnpm lint stays CI's run. Also read rather than assumed: the seven artifact-roster families the derivation marked ⛔ (roster in a directory this diff's path is in, so silence is evidence in neither direction) — check-published-list-mirrors.mjs and its --self-test, check:console-injection, check:engine-double-contract, check:i18n-stale-fill, check:pm-label-desc-cap all exit 0; check:published-readme-exports exits 3 = NOT MEASURED, prerequisite unmet (it reads 45 packages' built dist/.d.ts and this worktree has no build) — a comment in scripts/pm cannot move a package's built type surface and the repo-wide build is CI's. Control-byte self-scan over the edited file: grep -naP over the non-tab non-newline control range, no match (exit 1). No ablation or reverse verification: there is no behaviour to ablate — this diff changes only comment text, and the file's own self-test (31st family, green) is the battery that would have caught a code change. PR body and the report comment both read back after writing; the PR body stored byte-identical with exactly one footer.",
"zone2_measurements": {
"a_other_stale_sentences": "Quoted the docblock on the branch before editing (lines 10487-10496 at base 0ee32ed). grep -nE 'dispatched at|must be dispatched|fable-mandatory too' scripts/pm/dispatch-gates.mjs returned three hits pre-edit: :10491 (the target sentence) and :10519 / :21350 (now :10521 / :21352). Both survivors read 'dispatched at opus' and belong to the clause-1 MISCLASSIFICATION incident narrative — a factual account of what happened to one card, not a statement that clause-2 cards are built at the contract-review tier. Different sentence class ⇒ off the declared surface: reported here, not edited. 'fable-mandatory too' has zero hits in the file — that phrasing was already removed from tierLines by PR #16915, which is why the card's item 3 needed nothing.",
"b_self_test_pin": "Read the self-test before deciding. NO case pins this docblock's words: grep -n 'sub-round|CONTRACT-REVIEW|re-review' hits only prose lines (:10489, :10491, :10522), and no t(...) case names a docblock. The nearest neighbour is the tier case at :21564, which finds the DEFINITION line by searching for the line carrying both the constant's name and its value and then asserts the value is spelled at exactly one site under the two tier roots — a claim about the value, untouched by a comment edit, and green in this run. The file does have one docblock-consistency battery — COMPOUND_ANCHOR_LEDGER (#15310), whose docblock counts --self-test recomputes from the table, deliberately 'never against a second hand-typed constant'. Clause 2 is deliberately NOT encoded anywhere in this file, so there is nothing computable to pin this sentence against and any pin would have to hard-code the new wording, i.e. become the second hand-typed constant that precedent argues against. So: no battery invented for one sentence, and saying so is the deliverable the dispatch asked for."
},
"gates": [
"node packages/lint/scripts/check-reference-carrier-shape.mjs :: exit 0",
"node packages/lint/scripts/check-reference-carrier-shape.mjs --self-test :: exit 0",
"node scripts/check-ci-filter-parity.mjs :: exit 0",
"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",
"node scripts/check-declaration-mirrors.mjs :: exit 0",
"node scripts/check-declaration-mirrors.mjs --self-test :: exit 0",
"node scripts/check-scripts-symbol-anchors.mjs :: exit 0",
"node scripts/check-scripts-symbol-anchors.mjs --self-test :: exit 0",
"node scripts/check-self-test-wired.mjs :: exit 0",
"node scripts/check-self-test-wired.mjs --self-test :: exit 0",
"node scripts/check-self-test-workflow-commands.mjs :: exit 0",
"node scripts/check-self-test-workflow-commands.mjs --self-test :: exit 0",
"node scripts/check-whole-set-label-write.mjs :: exit 0",
"node scripts/check-whole-set-label-write.mjs --self-test :: exit 0",
"node scripts/report-test-timings.mjs --self-test :: exit 0",
"pnpm check:agent-test-spelling :: exit 0",
"pnpm check:bash32-floor :: exit 0",
"pnpm check:cli-command-ids :: exit 0",
"pnpm check:cross-package-test-inputs :: exit 0",
"pnpm check:declared-population-live :: exit 0",
"pnpm check:driver-memory-census :: exit 0",
"pnpm check:entry-guard :: exit 0",
"pnpm check:nul-bytes :: exit 0",
"pnpm check:parse-guard :: exit 0",
"pnpm check:pnpm-filter-targets :: exit 0",
"pnpm check:ratchet-remedy-authority :: exit 0",
"pnpm check:refd-timer-probe :: exit 0",
"pnpm check:watch-hint-literal :: exit 0",
"pnpm check:pm-dispatch-gates :: exit 0 (under os-verify-lock, VERDICT command-exit 0)",
"RECONCILE node scripts/pm/dispatch-gates.mjs --ran ran.list :: exit 0 — 31 derived, 31 run, 0 NOT-MEASURED, 0 UNRUN",
"node scripts/pm/check-governed-merges.mjs --test scripts/pm/dispatch-gates.mjs :: exit 0 — NOT governed",
"npx eslint --no-inline-config scripts/pm/dispatch-gates.mjs :: exit 0 (declared narrowing, three proofs in tests)",
"node scripts/check-published-list-mirrors.mjs :: exit 0 (⛔ roster family, read not assumed)",
"node scripts/check-published-list-mirrors.mjs --self-test :: exit 0 (⛔ roster family)",
"pnpm check:console-injection :: exit 0 (⛔ roster family)",
"pnpm check:engine-double-contract :: exit 0 (⛔ roster family)",
"pnpm check:i18n-stale-fill :: exit 0 (⛔ roster family)",
"pnpm check:pm-label-desc-cap :: exit 0 (⛔ roster family, roster under scripts/pm)",
"pnpm check:published-readme-exports :: exit 3 — NOT MEASURED, prerequisite: needs 45 packages' built dist/.d.ts, no build in this worktree"
],
"ci_status": "in_progress — the PR was opened at head 721d759 and the report is delivered on local verification, per the contract; CI convergence is the PM's read, not a wait I hold.",
"mcp_calls": "0 — the container's repo-scoped REST probe was green (GET /repos/objectstack-ai/objectstack = 200), so the card body, all four comments, the branch push, the draft PR and the label write all went through REST and git. No dedup search was needed because nothing was filed.",
"open_questions": [],
"out_of_scope_findings": [
"noted, not filed: two other 'dispatched at' occurrences survive in scripts/pm/dispatch-gates.mjs (:10521, :21352). Both are the clause-1 misclassification incident narrative ('claimed as not under the fable-mandatory roots and dispatched at opus'), a correct account of a past card and not a clause-2 mandate statement — a different sentence class, off the declared surface, correct as written. Successor: whoever next edits this file's tier section.",
"noted, not filed: this file has no docblock-PROSE battery to extend; its one docblock-consistency pin recomputes counts from a table and clause 2 is deliberately not encoded, so a pin over this sentence would have to hard-code the wording. Not invented, per the dispatch's own instruction. Successor: whoever next edits this file's tier section.",
"noted, not filed: pnpm check:published-readme-exports exits 3 in a fresh worktree with no build. That is the gate's designed PREREQUISITE NOT MET path and its own output says so loudly and refuses to be read as a pass — working as intended, not a defect."
]
}

Generated by Claude Code

ACCEPT — PR #17509 (head 721d7597) reviewed in-seat at the contract-review tier (skills seat, session session_01YKEjmbYNvYWJvWGSWx26zK, 2026-09-10T18:14Z).

Implemented-by: os-dev subagent on claude/issue-16914-dispatch-gates-clause2-docblock (claim 5622889949; default build tier; mode:subagent). Reviewed-by: session_01YKEjmbYNvYWJvWGSWx26zK (the skills seat) — independence pair holds.
PR shape: draft; base main; first line Fixes #16914; skip-changeset + size/s; the Clause-②: no line present; one footer. Changed files read from the PR and three-dot by this seat: exactly scripts/pm/dispatch-gates.mjs (+6/−4, comment lines only).
Path face by this seat at 721d7597: check-governed-merges.mjs --test ⇒ 「0 of 1 path(s) hit the register」, NOT governed ⇒ this seat lands it through the queue. check-clause2-carriers.mjs --pair 17509 exit 0.
Diff vs the residue: the whole diff read by this seat — the CONTRACT_REVIEW_TIER docblock at :10488 now says the constant is 「the tier the clause-② REVIEW runs at, both halves of it — the spec seat's review … and the needs:contract-review re-review sub-round … The BUILD of such a card is at the default judgment tier, so this constant is a review tier and never a dispatch mandate」; the rest of the docblock byte-identical; matches the file's own printout at :10553–:10555 and :10759–:10760 and the 强制条款② text PR skills(pm-dispatch): clause-② cards build at the default tier and are gated by the contract review at CONTRACT_REVIEW_TIER (#16905) #16915 landed. Zone 2: (a) the two surviving 「dispatched at opus」 hits (:10521, :21352) are the clause-① misclassification incident narrative — a different sentence class, correct as written, left alone: right; (b) no self-test pins the docblock's words and clause ② is deliberately not encoded, so no battery was invented for one sentence — the dispatch asked for exactly that judgement and got it.
Gates: 31 derived / 31 run / 0 NOT-MEASURED (--ran reconciled), pnpm check:pm-dispatch-gates green under the verify lock (848 s); eslint on the file exit 0 with the three narrowing proofs; seven roster families read rather than assumed (six exit 0; check:published-readme-exports exit 3 = PREREQUISITE NOT MET in an unbuilt worktree, the gate's own honest answer). CI at this reading: 33 check runs — 20 success, 11 skipped, 2 in progress.
Terminal: not governed ⇒ landing by this seat: flip ready → auto-merge with mergeMethod: "SQUASH" once every check on 721d7597 is green (flip point armed); on MERGED: landing record here + pm:dispatched / assignee cleared.

Generated by Claude Code

Landed — PR #17509 merged through the merge queue at 2026-09-10T19:11:32Z (merge commit bea76c92, head 721d7597), not governed (Governed Surface Queue Guard green on the queue head): ACCEPT 5623324102 → every check on the head green → flipped ready 18:46:00Z → auto-merge (SQUASH) 18:46:50Z → added_to_merge_queue 18:47:31Z → merged in the same queue group as PR #17504 (parent 1e0d7954). Verified on origin/main at 2026-09-10T19:24Z: scripts/pm/dispatch-gates.mjs :10488–:10491 read 「the tier the clause-② REVIEW runs at」 — a review tier, no dispatch mandate. Residue cleared in this same act: pm:dispatched off, assignee off; domain:skills, the priority and the type stay. The card was closed by the merge. Skills seat, session session_01YKEjmbYNvYWJvWGSWx26zK, R1.

Generated by Claude Code

Navigation Menu

Repository navigation

pm(dispatch-gates): clause-② prose in dispatch-gates.mjs (docblocks + every `--tier` printout) and core-rules.md:124 still describes a BUILD-tier mandate once the 强制条款② narrowing lands #16914

What #16905's PR changes

Prose in `scripts/pm/dispatch-gates.mjs` that still describes clause ② as a BUILD-tier mandate (verified on `origin/main` at `0939ba008`)

Not a behaviour change

Landing surface

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm(dispatch-gates): clause-② prose in dispatch-gates.mjs (docblocks + every --tier printout) and core-rules.md:124 still describes a BUILD-tier mandate once the 强制条款② narrowing lands #16914

Description

What #16905's PR changes

Prose in scripts/pm/dispatch-gates.mjs that still describes clause ② as a BUILD-tier mandate (verified on origin/main at 0939ba008)

Not a behaviour change

Activity

os-litant commented on Sep 10, 2026

Landing surface

os-litant commented on Sep 10, 2026

os-litant commented on Sep 10, 2026

os-litant commented on Sep 10, 2026

os-litant commented on Sep 10, 2026

os-litant commented on Sep 10, 2026

os-litant commented on Sep 10, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

pm(dispatch-gates): clause-② prose in dispatch-gates.mjs (docblocks + every `--tier` printout) and core-rules.md:124 still describes a BUILD-tier mandate once the 强制条款② narrowing lands #16914

Prose in `scripts/pm/dispatch-gates.mjs` that still describes clause ② as a BUILD-tier mandate (verified on `origin/main` at `0939ba008`)