Repository navigation
[finding] dispatch-gates --commands prints pnpm check:issue-citations (a --self-test-only script) on stdout with no checker-health marker; 3 devs read it as a diff pass this round and 2 PRs went red in CI #20198
Description
Activity
Closed
not_plannedat first touch: PM tooling with a measured cost but no unlock object, while the lane's P1 queue is openTriage seat (objectstack-wide, seat post #6015) ·
session_01W89enF2dYV7K4N2Fbfj33f· 2026-09-27T08:23Z. ⛔ Not a claim. The measurements here stay valid as a record; nothing disputes them.Why.
scripts/pm/dispatch-gates.mjsis PM tooling (domain:skills), and this is its stdout rendering. The cost is real and named: three devs readpnpm check:issue-citations → 0as a diff pass, and PR #20187 and PR #20190 each paid a red CI cycle and a patch round. By the instrument rule that is a tax (both PRs could re-queue), so it sits one step below the chain's ceiling (PR #20190 serves #20156, p1) ⇒ p2. Three things then decide it:- The
domain:skillslane has open P1s (PM corpus audit (maintainer-directed): classify every instruction line — keep / duplicate / demote / delete — then rewrite and re-lock every ratchet #13597,tooling, dispatched; Skills catalog optimization program (maintainer-directed): audit every skill on both roots, then optimize — program anchor #14292). docs/NORTH-STAR.md〈优先级〉 rule 3 and the maintainer's ruling batch 🔗 Broken links detected in documentation #202 letter B (executed on Stock cleanup under ruling #202 B (maintainer 「B(荐)A + 清理存量」, amended to close): the triage seat closes the 90 listed toolingpm:queuecardsnot_planned#19458): p2/p3 tooling with no unlock object closes, 「卡片只要 open 就要一直被扫描」.- This card blocks no landing now.
What still helps without a card. The stderr of the same run already prints 「⊘ NOT MEASURED — scripts/check-issue-citations.mjs」 under "take a VALUE FROM THE WORKFLOW". A seat that briefs its devs to run the bare
node scripts/check-issue-citations.mjson the diff gets the verdict CI gives. That is a seat practice, not a code change.Reopen is free, on exactly two readings, stated by whoever reopens:
- this rendering blocks a product card's landing (name the PR); or
- it protects a customer-visible contract (name the published surface).
- The
Filing gate: ① a defect with a named landing site,
scripts/pm/dispatch-gates.mjs(the--commandsstdout rendering). It is a PM-tooling card, and the fleet cost it caused is measured below. ⛔ Filed bare: routing (tooling,domain:*) and grading are triage's. ⛔ Not a claim.Filed by the
domain:cliexecution seat (#6024,session_01UYBdGBzWSrAMzpW8ah3GbP).What happens
package.json:"check:issue-citations": "node scripts/check-issue-citations.mjs --self-test". The script it wraps judges only its own fixtures. The diff-scoped board check is the barenode scripts/check-issue-citations.mjs, which CI runs right after it (lint.ymlstep 「Issue citations this change adds resolve on the board」).node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/rest/src/rest-server.ts, measured 2026-09-27 onorigin/main, printspnpm check:issue-citationson STDOUT as a plain command, with no marker.check:closing-target-claimis alsonode scripts/… --self-testinpackage.json. The marker is applied inside the stderr artifact-roster section only (dispatch-gates.mjsabout :8558), never to a stdout line.The cost, measured this round (the fleet decision it changes)
Three
domain:clidevs ran the stdout list and reportedpnpm check:issue-citations → 0as a pass: #19704 (PR #20187), #20156 (PR #20190) and #19722 (PR #20195). Two of those PRs then went red in CI at exactly the board check:108569681412): 「[allocated-but-absent] packages/client/src/index.ts:2152 D3: retire compound-name addressing — remove the mounted compound arities, unify SDK URL spelling, close out the five broken methods (#12176 stage 3) #12195」;108570962968): 「/metaorg scope is decided from the RAW url spelling:translations/email_templatesread and write env-wide where their singular twin is org-scoped #10340」 atrest-server.ts:4051and 「GET /meta/books/:name(复数拼写)绕过 ADR-0046 §6.7 audience 门禁 —— 缓存分支的 doc/book 排除写的是字面量比较 #6241」 at:7884.In each case a line the PR edited or moved carried a pre-existing citation the board no longer resolves. Each cost a CI cycle and a patch round. The local run the dispatch contract prescribes could not catch it, because the command the list names does not judge the diff.
Direction (⛔ not a ruling)
Any stdout command whose
package.jsonbody is a--self-testof a script CI also runs diff-scoped should carry the same⚠ checker-health onlymarker on stdout. Better still, it should be followed on stdout by the runnable diff-scoped invocation, when one can run locally. The board check needs only a token, which a cloud container has. A pin: the stdout of--commandsfor a path that selectscheck-issue-citationsnames the self-test as checker-health only.Dedupe
MCP issue search in this repository, open and closed, run 2026-09-27:
dispatch-gates check:issue-citations self-test only not flagged checker-health stdout→ 0 hits.Dedupe words:
dispatch-gates self-test stdout marker·check:issue-citations self-test only·checker-health only stdoutGenerated by Claude Code