Remove/localize the six dangling `@objectstack/spec/ui` theme-schema imports in `packages/types/src/zod/theme.zod.ts` — the ruled FIRST leg of unbreaking objectstack's Console Pin Gate

[os-zhuang]

Filed by the skills seat (session session_01MsbKEG4LtERSLaDrbehM3e, 2026-08-22) executing the maintainer's recorded ruling on objectstack-ai/objectstack#10856 — this is the missing first leg of that ruling, uncarded until now, which is why the repair has been stalled since the ruling landed this morning.

The ruling (recorded on objectstack#10856, 2026-08-22, decision-inbox digest, accepted verbatim 「接受所有」)

Ruled: Options A + C. A fixes the instance: the objectui side goes first — objectui removes/localizes the six dangling @objectstack/spec/ui theme-schema imports in packages/types/src/zod/theme.zod.ts (the ordering is forced, since objectui's tip carries the same dangling import as the pin), and only then does objectstack bump the Console pin past it. Option B (restoring the six retired exports as a compatibility surface) is not taken.

The defect this leg repairs

objectstack PR #10695 (2026-08-21, ADR-0049 ruled retirement, card objectstack#10485) deleted ThemeSchema / ColorPaletteSchema / TypographySchema / BorderRadiusSchema / ShadowSchema / ThemeModeSchema from @objectstack/spec/ui. objectui's packages/types/src/zod/theme.zod.ts still imports all six — measured on origin/main 0b1326d today (lines 24–25 for Shadow/ThemeMode; the import block starts ~line 20). Consequence: objectstack's Console Pin Gate cannot build the vendored SPA against the current framework tree — red on every objectstack merge-queue build (non-blocking, but ~89 red queue builds/24h and a triage channel full of identical false alarms; the count is on objectstack#10856).

Scope

• Remove the six imports and either delete the re-exports or localize the schema definitions into @object-ui/types (the file's own comment at ~line 81 says which are retained on purpose — honour it; the maintainer's original retirement ruling kept objectui's ThemeEngine/ThemeContext intact, so localizing is the expected shape where an engine consumer still needs the shape).
• Downstream consumers of the re-exported names inside objectui keep compiling — measure the consumer set before choosing delete vs localize per name.
• ⛔ Do not touch the spec side; restoring exports was explicitly rejected.

Downstream

objectstack#10856 (pm:blocked on this card) executes the pin bump once this lands on objectui main. The class-level rule (a pin-breaking removal ships with its pin bump) is objectstack#10986, separately queued.

Refs: objectstack#10856 (the ruled card, full measurement history) · objectstack PR #10695 (the retirement) · objectui #5489/#5650 (the component-kind retirement — related, deliberately different symbols).

[os-zhuang]

Claim: PM loop round 17
Session: session_01EuPCi56cnGyykygi3z9w4m
Branch: claude/issue-5710-theme-zod-dangling-imports
Worktree: objectui-issue-5710
Domain: domain:ui
File surface: packages/types/src/zod/theme.zod.ts, packages/types/src/zod/index.zod.ts, packages/types/src/theme.ts, packages/providers/src/types.ts and the parity tests under packages/types/src/__tests__/ + packages/providers/src/__tests__/ (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: claude-fable-5
Clause-②: yes
Serial constraints cleared: no in-flight card shares this surface. Round-17 siblings are fenced disjoint — #5619 (packages/auth + packages/app-shell/src/console/** + apps/console) and #5637 (packages/components/src/renderers/basic/record-picker.tsx). ⛔ packages/app-shell/src/chrome/ThemeProvider.tsx:3 mentions ThemeModeSchema in prose only and is fenced OUT of this card (it is also inside #5619's package). PR #5400 (changeset-release/main, Version Packages) is never touched. Predecessor on this surface, 78cbdb5 (#5489/#5650, ThemeComponentSchema retirement), is merged.

Tier basis. node scripts/pm/dispatch-gates.mjs --tier packages/types/src/zod/theme.zod.ts packages/types/src/theme.ts packages/providers/src/types.ts — run at dispatch, not recalled — returns "no path-derived mandate … the tier stays the PM's per-card judgment call (floor sonnet · default opus · ceiling fable). Clause ② is NOT reachable from paths … judged from the card CONTENT." Judged from content: this card sits on the spec-mirroring surface (theme.zod.ts re-exports @objectstack/spec/ui zod validators by reference), so clause ② is declared yes and the card is dispatched at CONTRACT_REVIEW_TIER (claude-fable-5, scripts/pm/dispatch-gates.mjs:2722) rather than below it. Maintainer authorization for this seat to dispatch above its own served tier, quoted verbatim, 2026-08-22: 「你虽然是 opus，但是可以派 fable 的卡」. No needs:contract-review compensating label is attached because none is owed at-tier — and for the record it does not exist in this repo (scripts/pm/ensure-pm-labels.sh:238 creates it for objectstack-ai/objectstack only).

Premise re-verified before dispatch, on origin/main (not the shared worktree).

• objectui origin/main = 7138bc1. All six imports present in packages/types/src/zod/theme.zod.ts (import block lines ~21–29). Card's measurement stands.
• objectstack origin/main = 95437e7. All six names return 0 export matches under packages/spec/src/ui/; control (PageSchema, FormViewSchema) returns live hits at page.zod.ts:410 / view.zod.ts:2394. The retirement is real and the zero is not a broken grep.

⚠️ One measured fact the card does not carry — the named file is not the whole dangling set. packages/providers imports ThemeModeSchema directly from @objectstack/spec/ui at src/types.ts:2 (feeding ThemePreference at :39) and in two tests (__tests__/spec-symbol-batch7.test.ts:28-29, __tests__/theme-mode-spec-parity.test.tsx:21). Against the framework tree those dangle for exactly the same reason. Treat this as a PM mechanism assumption, not a finding to accept on my word — re-measure it, and see the dispatch brief for how the ruling's observable requirement (a green Console Pin Gate) governs whether they are in scope.

---

Generated by Claude Code