Filed by the domain:ui PM seat from the objectui#7515 flight. The dev seat measured it both ways and handed it up as a PM call rather than filing across two existing cards — correct escalation.
The fact
Two already-filed gate-test defects contradict each other:
- objectui#6893 —
check-sdui-registration-pins.test.ts fails on any tree where packages/app-shell/dist exists.
- objectui#7460 —
check-readme-exports.test.ts reds on a half-built tree (one package's dist removed, which neither branch of that test handles).
⇒ Fully built reds #6893. Half-built reds #7460. There is no local build state in which scripts/__tests__/ is fully green. Measured both ways at 7fdeff55 during the objectui#7515 flight — hit accidentally, then isolated deliberately (removing app-shell/dist makes #6893 pass and restoring it makes it fail).
Why this is worth its own card rather than a comment on either
Neither existing card is wrong, and neither is a duplicate of the other — they are about different gates with different causes. What neither card records is the conjunction, and the conjunction is what actually bites:
- a contributor who runs
scripts/__tests__/ locally sees a red suite no matter what they do, so the honest signal is unavailable;
- a red that cannot be cleared is a red that gets ignored, which is the standing hazard this repo files gate cards about in the first place;
- anyone fixing one of the two in isolation will still face a red suite and may conclude their fix did not work.
The question for triage
Is this worth one card superseding both, or does it stay as a cross-reference on #6893 and #7460? That is a judgement about how the two are scheduled, not a measurement — which is why it is filed rather than decided here.
⚠️ Note the objectui#7515 dev proved its own diff cannot influence #6893: none of its changed paths appear in that gate or its test, with a lit control (the term app-shell present in both). So this is a pre-existing conjunction, not something the new gate introduced.
Refs: objectui#6893 · objectui#7460 · objectui#7515 (where both were hit) · PR #7670.
Generated by Claude Code
Filed by the
domain:uiPM seat from the objectui#7515 flight. The dev seat measured it both ways and handed it up as a PM call rather than filing across two existing cards — correct escalation.The fact
Two already-filed gate-test defects contradict each other:
check-sdui-registration-pins.test.tsfails on any tree wherepackages/app-shell/distexists.check-readme-exports.test.tsreds on a half-built tree (one package'sdistremoved, which neither branch of that test handles).⇒ Fully built reds #6893. Half-built reds #7460. There is no local build state in which
scripts/__tests__/is fully green. Measured both ways at7fdeff55during the objectui#7515 flight — hit accidentally, then isolated deliberately (removingapp-shell/distmakes #6893 pass and restoring it makes it fail).Why this is worth its own card rather than a comment on either
Neither existing card is wrong, and neither is a duplicate of the other — they are about different gates with different causes. What neither card records is the conjunction, and the conjunction is what actually bites:
scripts/__tests__/locally sees a red suite no matter what they do, so the honest signal is unavailable;The question for triage
Is this worth one card superseding both, or does it stay as a cross-reference on #6893 and #7460? That is a judgement about how the two are scheduled, not a measurement — which is why it is filed rather than decided here.
app-shellpresent in both). So this is a pre-existing conjunction, not something the new gate introduced.Refs: objectui#6893 · objectui#7460 · objectui#7515 (where both were hit) · PR #7670.
Generated by Claude Code