The getting-started guides teach ~14 symbols the packages do not export — one decision per symbol, applied everywhere (the #5160 class, on `content/docs/guide/**`)

[os-support-ai]

Filed by the repo:objectui execution seat (PM round 17, session session_01RV6yuVCxymHYE16PL9vQkE) as the fabricated-export half of #5174, per that card's Q2 answered as option C. Filed unassigned, not claiming.

Part of #5174 — the fragment / self-containment half stays on that card, which is genuinely per page. This one is not: a fabricated export is one decision about the real API surface, and shaping it per guide would re-litigate the same wrong symbol up to six times.

How this became visible

#5174's PR5341 widened check-doc-snippet-types.mjs to collect .md under content/docs — 40 guides that were previously neither covered nor declared ungated. Of the 28 holding a ts/tsx block, zero passed as collected. 20 are now on the ledger with measured diagnostic mixes, and those mixes name documented symbols that do not exist on the packages' built dist/index.d.ts.

These are the getting-started guides — the pages a reader copies from most. A reader who copies one of these imports does not get a degraded render; they get a compile error. Same defect class as #5160 (five published READMEs, 15 TS2305), one directory over.

The symbol table, as measured by PR5341

symbol	claimed from	occurrences
getComponentRegistry	@object-ui/react	6
registerDefaultRenderers	@object-ui/components	5
AppSchema / ThemeSchema / ReportSchema	@object-ui/types and /zod	9
BaseSchema	@object-ui/core	3
getExpressionEvaluator	@object-ui/core	—
ObjectStackProvider	—	—
registerAllComponents	@object-ui/components	—
ObjectSchema	@object-ui/types	—
Field	@object-ui/types	—
InputRenderer	@object-ui/components	—
componentSchema	—	—
DashboardSchema / PageSchema	@object-ui/types	—
FormSchema	—	—

⚠️ Re-measure before working. The counts come from PR5341's run; the tree moves. The authoritative list is the current UNGATED_DOCS entries for content/docs/guide/** and content/docs/api/schema-reference.md, whose reason strings name the symbols by hand.

The three dispositions, and the one already decided

#5053 established them, and they are not interchangeable:

• renamed → re-spell it;
• lives in a neighbour package → fix the import path;
• removed with nothing replacing it → delete the example and teach the real surface (the subtraction form of plugin-map README teaches an API the package does not implement — every snippet in it renders an empty map #5002 / PR5021).

One is already settled and should not be re-decided: registerDefaultRenderers resolves to initializeComponents() plus the side-effect @object-ui/fields import, evidenced by apps/site/app/components/ObjectUIProvider.tsx — PR5341 made that call once and applied it.

The measurement rule that makes this card safe

Take the name set from each package's built dist/index.d.ts, never from a grep of src/. #5053 measured that ReportScheduleConfig appears twice in src/ and is not exported, so a grep-based check calls a missing symbol real. ⛔ And do not "fix" a missing export by adding the export — that is a contract change and is not what this card is for.

Done when

Each symbol has one recorded disposition with its evidence, applied at every site. A guide's UNGATED_DOCS entry is rewritten to its new measured mix when its export diagnostics clear, and deleted only if that guide reaches zero overall — most will not, because the fragment / self-containment work on #5174 is a separate job. ⛔ Never widen an entry, never add one, never relax the gate.

Related

• check-doc-snippet-types.mjs collects only .mdx under content/docs — 40 .md guides are uncovered with no UNGATED_DOCS entry, contradicting its own "covered by default" rule #5174 — the collector change that exposed these; the fragment half stays there
• docs: five published READMEs import symbols their packages do not export — 15 TS2305, measured against the built dist #5160 — the same class on five published READMEs (14 of 15 landed via PR5260, the 15th via PR5332)
• docs(plugin-report): README 按真实导出面重写三处虚构导出与陈旧幸存清单 #5053 / plugin-report README 教三个不存在的导出:ReportBuilder 组件、registerDrillHandler、ScheduleConfig 组件 #5016 / plugin-report README's export snippets call every real export with the wrong signature — exportAsCSV(data, 'file.csv') passes a filename where the data argument goes #5048 — the disposition vocabulary and earlier instances
• check-doc-component-types collects only .mdx too — 26 .md guides teach 345 type literals inside fences with nothing checking them #5342 — the same extension-only collector in check-doc-component-types.mjs, filed as a sub-issue of finding(docs/gate): check-doc-component-types 的扫描面止于代码围栏 —— 八个 PR 新加的「真实 register 键表」全部在门外,且门从不判 namespace 半边 #5106

[os-support-ai]

Claim: PM loop round 18
Session: session_01RV6yuVCxymHYE16PL9vQkE
Branch: claude/issue-5343-guide-fabricated-exports
Worktree: objectui-issue-5343
Domain: repo:objectui (execution seat)
File surface: content/docs/guide/**, content/docs/api/schema-reference.md, and the UNGATED_DOCS ledger in scripts/check-doc-snippet-types.mjs (stop on breach; explain in the report)
Container & model: L, mode:subagent, model: opus — node scripts/pm/dispatch-gates.mjs --tier <paths> returns no path-derived mandate; tier is this seat's call, taken at opus for the size and for the number of independent judgments.
Clause-②: no — and this is load-bearing: the card forbids the accept-set-widening repair. ⛔ Never fix a missing symbol by adding the export. That is a contract change, it is a different card, and it is the single way this task can go wrong invisibly.
Serial constraints cleared: content/docs/guide/** has no in-flight claim. ⚠️ scripts/check-doc-snippet-types.mjs is shared with #5174, which is still pm:dispatched — but its landed half (PR5341, the collector widening) is merged and its remaining half has no dev in flight, so there is no concurrent writer on that file. Round-18 siblings hold disjoint surfaces (#5214 six packages; #4818 packages/layout; #5126 skills/objectui/**; #5356 packages/app-shell/src/preview). #5342 (the same collector defect in check-doc-component-types.mjs) is a different script and stays in the queue — ⛔ do not touch it here.

Re-measure first — the card says so and it means it

The symbol table in the body comes from PR5341's run and the tree has moved since. The authoritative list is the current UNGATED_DOCS entries for content/docs/guide/** and content/docs/api/schema-reference.md, whose reason strings name the symbols by hand. Re-derive it in your worktree and report your own list; where it disagrees with the card's table, your reading wins and the disagreement is worth a line in the PR.

Take the name set from each package's built dist/index.d.ts, never from a grep of src/. #5053 measured ReportScheduleConfig appearing twice in src/ while not being exported — a grep-based check calls a missing symbol real. State per leg whether a build artifact sits between your edit and the thing under test, and rebuild when it does.

The dispositions

#5053's three, and they are not interchangeable: renamed → re-spell; lives in a neighbour package → fix the import path; removed with nothing replacing it → delete the example and teach the real surface (the subtraction form of #5002 / PR5021).

One is already settled and ⛔ should not be re-decided: registerDefaultRenderers resolves to initializeComponents() plus the side-effect @object-ui/fields import, evidenced by apps/site/app/components/ObjectUIProvider.tsx; PR5341 made that call once and applied it.

The point of doing this as one card rather than per guide: a fabricated export is one decision about the real API surface. Record one disposition per symbol with its evidence, then apply it at every site. If you find yourself deciding the same symbol twice because two guides spell it differently, that is the failure this card exists to prevent — go back and make it one decision.

Ledger discipline — the ratchet only tightens

Rewrite a guide's UNGATED_DOCS entry to its new measured mix when its export diagnostics clear. Delete an entry only if that guide reaches zero overall — most will not, because #5174's fragment / self-containment half is a separate job and those diagnostics stay. ⛔ Never widen an entry, never add one, never relax the gate. If a guide gets worse under your change, that is a defect in the change, not a ledger update.

Part of #5174 and Fixes #5343.

---

Generated by Claude Code