Filed unassigned by the spec-lane PM seat (session session_01225pUjnCKWqxcc1PeqKFUq) from PR #9113's patch round; grading and routing are triage's. Duplicate-searched: no card names check:i18n + dispatch-gates.
Measured (cost already paid once today)
PR #9113 added two form entries (object.form.ts / field.form.ts rows for the new placeholder key). That moved platform-objects' four metadata-forms i18n locale bundles, and pnpm check:i18n went red on CI — as the LAST step of the "TypeScript Type Check" job. The dev's diff-derived gate union (via node scripts/pm/dispatch-gates.mjs <changed paths>) did not and cannot name the family: check:i18n rides the TypeScript workflow with no path filter the derivation can see, so it scores "undetermined/silent" for every card — the derivation's own residue caveat, here with a measured false-clearance. Cost: one full CI round trip + a patch commit (e83629589, four bundles regenerated, additions only).
Fix directions (for whoever owns the gate map — triage routes)
- Give the mapping a machine-readable anchor: a
paths:-style comment or metadata in the workflow step (or a registry entry dispatch-gates reads) declaring that check:i18n fires on packages/spec/src/**/*.form.ts (+ the bundle schemas' other producers — enumerate from check-i18n-bundles.mjs itself, not from memory). - Alternative: teach
dispatch-gates.mjs a convention-triggered rule ("edits a .form.ts in a package feeding metadata-forms bundles ⇒ run pnpm check:i18n"), the same mechanism its test-file rules use.
Either way the invariant is: a gate that a diff can move should be derivable from that diff — "undetermined" was designed as an honest unknown, not a standing blind spot on a known edge.
Refs
PR #9113 (the paid instance) · scripts/pm/dispatch-gates.mjs (residue semantics in its output header) · scripts/check-i18n-bundles.mjs (the gate).
Filed unassigned by the spec-lane PM seat (session
session_01225pUjnCKWqxcc1PeqKFUq) from PR #9113's patch round; grading and routing are triage's. Duplicate-searched: no card namescheck:i18n+ dispatch-gates.Measured (cost already paid once today)
PR #9113 added two form entries (
object.form.ts/field.form.tsrows for the newplaceholderkey). That moved platform-objects' four metadata-forms i18n locale bundles, andpnpm check:i18nwent red on CI — as the LAST step of the "TypeScript Type Check" job. The dev's diff-derived gate union (vianode scripts/pm/dispatch-gates.mjs <changed paths>) did not and cannot name the family:check:i18nrides the TypeScript workflow with no path filter the derivation can see, so it scores "undetermined/silent" for every card — the derivation's own residue caveat, here with a measured false-clearance. Cost: one full CI round trip + a patch commit (e83629589, four bundles regenerated, additions only).Fix directions (for whoever owns the gate map — triage routes)
paths:-style comment or metadata in the workflow step (or a registry entry dispatch-gates reads) declaring thatcheck:i18nfires onpackages/spec/src/**/*.form.ts(+ the bundle schemas' other producers — enumerate fromcheck-i18n-bundles.mjsitself, not from memory).dispatch-gates.mjsa convention-triggered rule ("edits a.form.tsin a package feeding metadata-forms bundles ⇒ runpnpm check:i18n"), the same mechanism its test-file rules use.Either way the invariant is: a gate that a diff can move should be derivable from that diff — "undetermined" was designed as an honest unknown, not a standing blind spot on a known edge.
Refs
PR #9113 (the paid instance) ·
scripts/pm/dispatch-gates.mjs(residue semantics in its output header) ·scripts/check-i18n-bundles.mjs(the gate).