docs(guide,api): one disposition per fabricated export, applied at every site (#5343)

[os-support-ai]

Fixes#5343
Part of #5174

The getting-started guides taught 14 symbols the packages do not export. A reader who copied one of those imports did not get a degraded render — they got a compile error. Same class as #5160 (five published READMEs), one directory over, on the pages people copy from most.

Every name set comes from each package's built dist/index.d.ts, resolved exactly as check-doc-snippet-types.mjs resolves it (each package's exports.types), never from a grep of src/ — the #5053 rule. The measurement harness reuses that script's own analyze() / compileSnippets(), so the numbers below are produced by the same pipeline that writes the ledger, over the whole corpus in one program (637 blocks, 541 semantically judged). Build artifacts sit between every edit and the thing under test, so the packages were built first (turbo run build, 43 tasks) and every measurement ran against that dist/.

Re-measured before working — and it agrees with the card

The card said its symbol table came from PR5341's run and the tree had moved. Re-derived here, the baseline reproduced the ledger's recorded mix exactly, for all seven entries — so this tree had not moved on these pages. One number disagrees with the card's body table: AppSchema / ThemeSchema / ReportSchema are 8 occurrences, not 9 (TS2305x2 + TS2724x6 in schema-overview.md). The card's ObjectStackProvider row lives at content/docs/utilities/index.md:163, outside this card's file surface; it is untouched, still on the ledger, and now filed on its own (see Findings).

One disposition per symbol, applied at every site

symbol	claimed from	disposition	resolves to	sites
getComponentRegistry	@object-ui/react	renamed + wrong package	ComponentRegistry, the process-level singleton @object-ui/core exports (Registry.d.ts:341; the spelling PR5260 landed in the core/react/components READMEs)	component-registry ×5, schema-rendering ×1
registerDefaultRenderers	@object-ui/components	renamed — settled by PR5341, not re-decided	initializeComponents() plus the side-effect import '@object-ui/fields' (apps/site/app/components/ObjectUIProvider.tsx)	component-registry ×4, schema-rendering ×1
registerAllComponents	@object-ui/components	same disposition, same evidence	as above (which also retired the registerAllFields(Registry) arity error — the real one takes no arguments and the module calls it itself at load)	building-crud-app ×1
BaseSchema	@object-ui/core	wrong package	@object-ui/types (base.d.ts:65, and it declares className — which is what retired the page's TS2339)	component-registry ×3
PageSchema	@object-ui/types / @object-ui/core	renamed + wrong package	PageNodeSchema in @object-ui/types — renamed by objectui#3074, which split the renderer NODE off the spec's Page document	schema-reference ×1, schema-rendering ×1
FormSchema	@object-ui/core	wrong package	@object-ui/types (form.d.ts:1073)	schema-rendering ×1
DashboardSchema	@object-ui/types	renamed	DashboardComponentSchema (complex.d.ts:657)	schema-reference ×1
AppSchema	@object-ui/types, /zod	renamed	AppComponentSchema (app.d.ts:283, zod app.zod)	schema-overview ×3
ThemeSchema	@object-ui/types, /zod	renamed	ThemeComponentSchema (theme.d.ts:79, zod theme.zod)	schema-overview ×3
ReportSchema	@object-ui/types, /zod	renamed	ReportComponentSchema — the presentation layer; Spec* is the definition layer (spec-report.d.ts header)	schema-overview ×2
componentSchema	@object-ui/types/zod	renamed (case)	ComponentSchema (zod/blocks.zod.d.ts:482) — aliased at the site, because the same block already imports the TYPE of that name	troubleshooting ×1
InputRenderer	@object-ui/components	removed, nothing replaces it	built-in renderers are registered by loading their package; they are not handed out one by one. The "Registering Individual Components" section is gone	component-registry ×1
ObjectSchema / Field	@object-ui/types	removed, nothing replaces it	no builder API exists. Object metadata is the plain document a data source serves (DataSource.getObjectSchema() returns Promise<any>); the example now writes it as a literal whose fields record is typed against the real FieldMetadata union	building-crud-app ×1 (two names)
getExpressionEvaluator	@object-ui/core	removed, nothing replaces it	there is no process-level evaluator — SchemaRenderer.tsx:420 constructs a fresh ExpressionEvaluator per evaluation, and each one builds its own FormulaFunctions. The section now teaches evaluateExpression(expr, context) and new ExpressionEvaluator(context)	expressions ×1

Two same-spelling names were checked and deliberately not touched, because their source is real: layout.md's prose "an AppSchema JSON document" and dashboard-filters.md's "DashboardSchema.dateRange … are part of @objectstack/spec" both name spec exports (@objectstack/spec/ui does export AppSchema). The defect was always the claimed source, never the spelling in the abstract.

The two replacement claims in expressions.md were verified by running them against the built dist/, not by reading: a context-supplied function is callable under its exact name (evaluateExpression('${formatCurrency(price)}', { formatCurrency, price: 1234.5 }) → '$1,234.50'), and ${user.permissions.includes('admin')} returns true / false against the two obvious contexts.

Adjacent falsehoods the renames exposed — fixed here, and why that is not scope creep

Re-pointing an import at the real type turns a previously-unchecked literal into a checked one. Three blocks would have gained a new diagnostic class, which the ratchet forbids, so they were corrected in the same pass, each pinned by the same built d.ts the disposition came from:

• schema-overview.md theme example — mode: 'system' (the vocabulary is auto / light / dark) and per-theme light / dark palettes (the spec Theme carries one colors map). Measured: TS2322x1 + TS2353x1 appeared, then went.
• schema-rendering.md typed page — PageNodeSchema.body is SchemaNode[], so the nested form is an array element. Measured: TS2353x1 appeared, then went.
• component-registry.mdregister(…) metadata — displayName / description / tags / schema / lazy: true are not ComponentMeta keys; the real ones (label, category, icon, inputs, labelling) are used, and lazy registration is registerLazy(type, loader). In the same page getRegisteredTypes() / getMetadata() became getAllTypes() / getMeta(), the names the Registry class declares.

Ledger — rewritten to the new measured mix, never widened

Every entry stays: none of the seven pages reaches zero, because #5174's fragment / self-containment half is a separate job.

entry	before (= what the ledger recorded)	after
api/schema-reference.md	1 undef; TS2305x1 TS2724x1	1 undef
guide/building-crud-app.md	1 parse; 20 undef; 4 unres; TS2305x2 TS2339x1 TS2345x1 TS2554x1 TS2724x1 TS2882x1	1 parse; 20 undef; 4 unres; TS2339x1 TS2345x1 TS2882x1
guide/component-registry.md	3 parse; 51 undef; 6 unres; TS2305x13 TS2339x1	3 parse; 50 undef; 6 unres
guide/expressions.md	8 parse; 6 undef; TS2724x1 TS7006x3	8 parse; 5 undef; TS7006x1
guide/schema-overview.md	9 parse; 2 undef; TS2305x2 TS2724x6	8 parse; 2 undef
guide/schema-rendering.md	8 parse; 10 undef; 1 unres; TS2305x4 TS2322x1 TS2451x2 TS7006x5	8 parse; 10 undef; 1 unres; TS2322x1 TS2451x2 TS7006x5
guide/troubleshooting.md	8 undef; 1 unres; TS2322x1 TS2339x2 TS2559x1 TS2724x1	8 undef; 1 unres; TS2322x1 TS2339x2 TS2559x1

Every bucket is equal or lower and no new class appears. Nothing was added to the ledger, no threshold moved, and no export was added to any package — the accept set is untouched.

The ledger's header note is updated with it: after this change, exactly one entry in the whole file still names a missing export (content/docs/utilities/index.md, ObjectStackProvider), and it says so by name.

Verification (at d975803fb, the final commit)

node scripts/check-doc-snippet-types.mjs → 87/87 blocks judged, 0 failed; ledger exact; controls green
node scripts/check-doc-component-types.mjs → 564 type literals, 0 unregistered
node scripts/check-doc-links.mjs → links valid across 13 scan roots
node scripts/check-control-bytes.mjs → OK (4757 tracked text files)
node scripts/check-changeset-{no-major,fixed,presence}.mjs → green; no changeset owed
pnpm exec eslint scripts/check-doc-snippet-types.mjs → clean
pnpm exec vitest run scripts/__tests__/check-doc-{snippet,component}-types.test.ts → 47 passed

Corpus re-derivation at the same commit: over all 35 guide pages plus schema-reference.md, and again over the whole 637-block corpus, zero TS2305 / TS2724 / TS2614 remain anywhere under this card's file surface. The only missing-export diagnostic left in the corpus is ObjectStackProvider at content/docs/utilities/index.md:163.

Changeset: empty frontmatter (.changeset/guide-fabricated-exports-5343.md) — docs and gate ledger only, no package src/ touched, so nothing publishes. That is this repo's declared "no release" form (AGENTS.md §9; precedent .changeset/app-shell-docs-nav-examples.md) and it is what check-changeset-presence.mjs confirms is owed. The dispatch suggested patch; a patch would move all 39 packages of the fixed group for a change with no runtime effect, so the empty declaration is used instead and flagged here.

Findings, filed not fixed

• content/docs/utilities/index.md still documents the ObjectStackProvider phantom API that #4124 removed from the page one file over #5360 — content/docs/utilities/index.md still documents the ObjectStackProvider phantom React API that data-objectstack docs page documents an ObjectStackProvider / useObjectStack React API the package does not export (the package is headless) #4124 / PR4129 removed from the sibling page one file over. Outside this card's file surface.
• ObjectSchemaMetadata declares neither titleFormat nor list_views / listViews nor icon, and the runtime reads all three #5362 — ObjectSchemaMetadata declares neither titleFormat nor list_views / listViews nor icon, all of which the runtime reads. Adding them is a contract change and a different card; this PR left the guide's metadata document a plain literal and typed only the fields record.
• finding(core): ExpressionEvaluator.registerFunction upper-cases the name, so a lower-case call in an expression renders its own ${...} source #5363 — ExpressionEvaluator.registerFunction(name, fn) upper-cases the name, so ${formatCurrency(x)} never resolves to a function registered as formatCurrency and renders its own source instead. Measured, not inferred.

---

Generated by Claude Code