You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(tooling): declare check:where-matcher's test-file population where dispatch-gates can read it (#13231)
`scripts/pm/dispatch-gates.mjs` derives a card's gate list from the path
literals in each gate's own source. `check-where-matcher-conformance.mjs`
declared its population twice and the derivation could read neither: once in
prose (the extractor masks comment ranges by construction) and once as
`const SCAN_ROOT = 'packages'`, a single-segment literal `looksPathy` refuses
as no hint at all.
Measured before this change, `extractWatchHints` over the gate returned exactly
one hint — `scripts/where-matcher-conformance.baseline.json`, the gate's own
ledger. So the derivation could name the gate only for a change set that edits
the set of files ALREADY KNOWN to be wrong, and never for a NEW silently-wrong
matcher anywhere under the root it scans: the exact inverse of what it guards.
Declares `packages/**/*.test.ts` beside `SCAN_ROOT` under the
`ROOT_DIR_WATCH_HINTS` idiom, matching the identically-populated sibling
`check-objectql-double-limit.mjs` (byte-identical `testFilesUnder`, identical
`SCAN_ROOT`, identical call site). Measured at 2889 of the 2889 files the
gate's own walk admits — set-equal in both directions — against 5509 tracked
files under the bare root. Pinned in the gate's own `--self-test`, in the four
directions the sibling pins.
The PM's bare-root worklist row is re-decided from REFUSE-UNSPELLABLE to
DECLARED-NARROWER with the same `package test files` spelling, re-measured on
this tree rather than carried from the sibling.
Claude-Session: https://claude.ai/code/session_01CPrUz21stTFhJRUirdc4yw
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments