Closes the remaining scope of objectstack-ai/objectstack#4074 (steps 2–3) and retires the p1-spec-alignment.test.ts debt #3009 declared. Three public types said something different from what the platform accepts; each fix below carries its runtime evidence.

1. ActionParam is the authoring shape, aligned with the spec's input

name / label / type become optional and field / objectOverride appear. The spec's primary way to declare a param — a bare field reference that inherits label/type/validation/options from an object field — was unrepresentable while all three were required: { field: 'status' } was a type error in the very package that claims spec alignment.

The resolved shape the dialog consumes — after app-shell's resolveActionParams() inlines the reference — remains @object-ui/core's ActionParamDef, with all three required. Authoring and resolved are different types on purpose; that separation is the whole point (and is spec's own: it exports ResolvedActionParam distinct from the schema input).

The new guard caught me in the act. I typed label as the spec's I18nLabel and wrote a per-locale-record fixture, matching what I'd claimed in the issue — the now-compiled annotation immediately failed: in the current spec, I18nLabelSchema is z.ZodString (the record form is the separate I18nObject). The fixture was corrected, and since label imports the alias rather than restating it, objectui tracks any future widening automatically. Guards that run beat claims that don't — the PR's thesis, demonstrated against its own author mid-PR.

2. ListViewInferred is z.input, not z.infer

The spec sub-schemas flowing into the list-view surface (userActions, tabs → ViewTab, sharing) carry .default()s, so the inferred output type made userActions.refresh or a tab's pinned / visible required. But nothing on the render path ever runs .parse(): normalizeListViewSchema deliberately applies no defaults — "an absent flag stays absent" is one of its own test names. So the output type simultaneously

• rejected valid authored metadata (userActions: { sort: true }, a tab without pinned), and
• promised renderers defaults that never arrive at runtime.

z.input matches both the author and the actual runtime object. Code that trusted the phantom defaults now gets an optionality error — a latent bug surfacing, not a regression.

3. FormField.dependsOn matches its runtime reader

resolveCascadingOptions (@object-ui/core) has always accepted a bare name, a list of names, or lookup-parameter entries { field, param } — its parameter type DependsOnInput says so. The public FormField.dependsOn said string, so array-authored metadata type-errored while working, and the components form renderer read the key through (f as any).dependsOn to get past its own type — the as any was the confession.

DependsOnInput now lives in @object-ui/types next to FormField (single source of truth; the dependency direction types → core is the correct one), core imports and re-exports it for its existing consumers (@object-ui/fields' useCascadingOptions keeps working untouched), and both as any reads are typed. form.tsx lint warnings drop 87 → 85.

The p1 exclusion is gone

tsconfig.test.json no longer excludes anything. The 14 errors resolved site-by-site rather than papered over:

Verification

• Discrimination checks, 3/3 bite: revert ListViewInferred to z.infer → TS2739 on the exact fixtures; revert dependsOn to string → TS2322; revert ActionParam.name to required → TS2741 on the field-backed annotation. Restored: clean.
• pnpm type-check — 76/76 tasks.
• pnpm vitest run — 731 files / 8516 tests passed, 1 file / 24 skipped.
• Affected suites directly: types (16 files/246), core normalizer + evaluator + fields cascading (26 files/552 with types), components form + plugin-form (38 files/290).
• eslint on changed files: 0 errors, no new warnings (form.tsx count drops by 2).
• node scripts/check-changeset-fixed.mjs — clean.

Changeset: @object-ui/types major (the ActionParam optionality and ListViewInferred input-typing are breaking for consumers that destructured required fields), core/components patch.

Also fixes a wrong reference merged in #3009: the guard file's header said the test project landed in "#3005".

Refs objectstack#4074, #3009, #3003, #2231, #2890, objectstack#4115, objectstack#4118

Generated by Claude Code