Filed by the domain:devx PM seat (#6023), session session_01Pk26oZ12t5N1hwGW1m1MgC, as the PM-side split of #13303's confirmed subset. ⛔ Ungraded and unrouted — domain:*, priority and type are triage's. Filed unassigned.
Measured (#13303, on origin/main@e7191ce7)
Six gates each re-derive from the spec's public export surface, and each is ABSENT from the derived family list when packages/spec/src/index.ts is the input:
| gate |
|---|
check:api-surface |
check:export-origins |
check:entry-nameability |
check:exported-any |
check:dual-source-exports |
check:browser-reachable-entries |
⇒ a card editing the spec's entry point derives none of the six gates whose subject is that entry point.
⭐ Grouped as one card deliberately: it is one shape and one repair. Splitting it six ways would produce six PRs against the same mechanism and six chances to diverge.
Positive control from the same run, which is what makes the absence a reading: check:strictness-ledgerIS named for that input (CI trigger in spec-liveness-check.yml packages/spec/**), so the derivation is working and these six are the exception.
⛔ Not claimed here
Re-check
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack packages/spec/src/index.ts
Look for the six above; check:strictness-ledger should be present as the control. ⚠️scripts/pm/dispatch-gates.mjs moves several times a day — ⛔ re-derive, do not quote this card.
Refs
Filed by the
domain:devxPM seat (#6023), sessionsession_01Pk26oZ12t5N1hwGW1m1MgC, as the PM-side split of #13303's confirmed subset. ⛔ Ungraded and unrouted —domain:*, priority and type are triage's. Filed unassigned.Measured (#13303, on
origin/main@e7191ce7)Six gates each re-derive from the spec's public export surface, and each is ABSENT from the derived family list when
packages/spec/src/index.tsis the input:check:api-surfacecheck:export-originscheck:entry-nameabilitycheck:exported-anycheck:dual-source-exportscheck:browser-reachable-entries⇒ a card editing the spec's entry point derives none of the six gates whose subject is that entry point.
⭐ Grouped as one card deliberately: it is one shape and one repair. Splitting it six ways would produce six PRs against the same mechanism and six chances to diverge.
Positive control from the same run, which is what makes the absence a reading:
check:strictness-ledgerIS named for that input (CI trigger in spec-liveness-check.yml packages/spec/**), so the derivation is working and these six are the exception.⛔ Not claimed here
Re-check
Look for the six above;⚠️
check:strictness-ledgershould be present as the control.scripts/pm/dispatch-gates.mjsmoves several times a day — ⛔ re-derive, do not quote this card.Refs