Three issues, one theme: a rule that isn't a check isn't a rule. Each lands as CI, and each ships with a run showing the guard failing against pre-fix code.

• objectstack#4115 — a spec-named symbol must be an import, not a declaration
• objectstack#4118 — the 8 zero-error packages (measured: 12) type-check their tests
• objectstack#4075 step 1 — inventory ActionDef's keys, warn on the ones nothing reads

objectstack#4115 — scripts/check-spec-symbol-derivation.mjs

objectui declares local types and consts under the same names as @objectstack/spec exports, with doc comments claiming spec canonicity. Every audited instance had drifted or was one release from it: ActionType (missing form), ChartType (7 of 19 members), ActionLocation + 2 (re-declared union + tuple + z.enum under a comment that said "re-export here"), ActionParamFieldType (16 of 49).

The cost is specific to agent-driven development: an agent reads the comment, takes it as ground truth, and builds on it. #2901 was filed with a backwards premise because the fork carried the spec's own symbol name.

How it works. Enumerates all 4231 spec export names — types and values, through the compiler's view of each subpath's .d.ts, because a runtime import() sees only values and the drifted symbols are mostly types. Then flags an exported declaration whose name the spec owns, unless it is derived.

Both sanctioned forms pass, because both bind the local name to the spec at compile time:

export type { ActionLocation } from '@objectstack/spec/ui';   // re-export
export type ActionType = z.infer<typeof SpecActionType>;      // derivation

Derivation must sit in a structural position — a type alias's own type node, an interface's extends, a const's initializer. A spec name merely mentioned inside a members block does not count, because that is what a fork looks like. Consts are stricter: array and object literals are not descended into, so export const ACTION_LOCATIONS = [...SpecLocations] is still flagged — a faithful copy passes every value comparison, and only reference identity distinguishes a re-export from a fork (#3003).

The ledger names symbols, not counts. 156 pre-existing collisions across 19 packages, listed by name. A per-package count is a budget: it lets the next fork land as long as an unrelated one was fixed in the same PR, and it makes the failure message point at whichever symbol sorts first rather than the one just written. --ledger regenerates the block, so burning them down is mechanical.

Barrel re-exports through a relative path or an @object-ui/* sibling aren't counted twice — the declaration they point at is judged on its own turn.

❌  a spec-named symbol is hand-written, not derived:
    • @object-ui/types declares 1 spec-named symbol the spec already owns:
        type `ActionType`  packages/types/src/ui-action.ts:80  (exported by `@objectstack/spec/ui`)

    • @object-ui/plugin-markdown declares 1 spec-named symbol the spec already owns:
        type `ChartType`  packages/plugin-markdown/src/__proof.ts:1  (exported by `@objectstack/spec/ui`)

    • @object-ui/types lists 1 symbol in DEBT that no longer collide — `SelectOption`.

Runs in the type-check job after install (it reads the spec's .d.ts, not the build). 5.5s.

objectstack#4118 — 12 packages type-check their tests

A package tsconfig excludes test files — correctly, it is the BUILD config and they'd emit into dist. The hole is that no other tsc invocation read them. objectui#3009 found what that costs: spec-derived-unions.test.ts had built its whole contract on satisfies checks that never ran, under a header calling them "the real enforcement". Reverting a derived alias produced zero errors.

12 free wins, not 8. The extra four fell out of a better config template: plugin-calendar and plugin-kanban needed only the jest-dom matcher types, providers was already clean, and sdui-parser's 50 TS2304s were env globals — exactly as the issue suspected, not real errors.

Wiring sdui-parser up surfaced a real bug. render.test.tsx imports @object-ui/core and @object-ui/react with neither declared in its package.json — phantom dependencies resolved only through the root tsconfig's paths alias and vitest, never as a dependency a consumer would get. Both are devDependencies now, which is also what makes paths: {} in the new config meaningful: with the alias in place, an undeclared workspace import still compiles.

Every tsconfig.test.json follows objectui#3009's template — noEmit, composite: false, paths: {} to kill the TS6059 source-leak noise, and lib / types only where the tests actually need them (mobile reads Array.prototype.at, so ES2022; plugin-report pulls in a source file that reads process.env, so node).

The guard grows a second half so this can't silently regress. A package with test files either compiles them or carries a TEST_DEBT entry with a measured count — re-measured against current main, not copied from the issue's table: 240 code-tier errors across 15 packages. It also fails on a tsconfig.test.json that nothing runs, which is the objectui#3009 shape itself.

    • @object-ui/plugin-tree (packages/plugin-tree) has a tsconfig.test.json that its "type-check" script never runs,
      so the file looks like enforcement while nothing compiles it — the exact shape of objectui#3009.

    • @object-ui/permissions (packages/permissions) has 3 test files that no `tsc`
      invocation reads: its tsconfig.json excludes them (correctly — it is the build config)

objectstack#4075 step 1 — ActionDef's key inventory

ActionDef ends with [key: string]: any. Deleting ActionDef.execute produced zero compile errors (objectui#2990); the same deletion against @object-ui/types' ActionSchema — no index signature — correctly produced TS2353. One reader can catch a retired key, the other is structurally incapable. That's how a typo (targt) and a tombstoned key both reach a runner that then silently does nothing — the #2169 shape.

Step 1 is the non-breaking half: make the key set visible, warn on anything outside it, change no types.

What the inventory found — step 2's worklist:

ActionEngine reads two of the first group through as any casts — (ra.action as any).visible, (action as any).locations. Those casts exist only because the field is undeclared, and they go away when step 2 promotes them.

Two things the inventory corrected:

• execute is not simply gone from the spec — it's a live tombstone, still in ActionSchema so the parser can reject it by name with the rename prescription (verified by parsing). So it's warned about separately and more loudly: an unknown key is probably a typo, a retired key is metadata that used to work.
• to / external / newTab / replace are a real objectui dialect — the navigation alias's own spelling, read off the action when no nested navigate object is present. Declared rather than left to trip the warning, with a tripwire test that fails if the spec ever adopts one.

The lists are data because TS types don't survive to runtime, and keyof ActionDef can't substitute — the index signature widens it to string | number, which is the problem itself. actionKeys.pin.test.ts re-derives each list from its real source (the interface via the AST, the spec via its schema), so a hand-maintained list can't drift from what it mirrors.

One pin is deliberately inverted: the suite asserts the index signature is still there. The day that fails, step 3 has landed, tsc catches unknown keys itself, and this warning plus executeScript's rename branch retire together.

AssertionError: expected { missing: [ 'target' ], stale: [] } to deeply equal { missing: [], stale: [] }

Verification

• pnpm type-check — 76/76 tasks successful (3m51s)
• node scripts/check-type-check-coverage.mjs — green, both halves
• node scripts/check-spec-symbol-derivation.mjs — green (5.5s)
• node scripts/check-lint-coverage.mjs — 45/45 packages, 0 errors
• node scripts/check-changeset-fixed.mjs — green
• eslint on all new/changed files — 0 errors, 0 warnings
• Core action tests — 208 passed (11 files), including 12 new
• Every one of the 12 wired packages verified at 0 errors individually

Changeset: @object-ui/core minor (new public exports). The other 11 packages change only build wiring, so no runtime version bump.

Scope note: all three issues are filed on objectstack-ai/objectstack but every change is in objectui; the sibling repo is untouched.

🤖 Generated with Claude Code

Generated by Claude Code