Both `plugin-form` catalog entries author `form` (a `@object-ui/components` type), never `object-form` — the third instance of #5113's class

[yinlianghui-tw]

Filed unassigned while implementing #6024 (generalizing the catalog "entries use their own plugin" pin). Not claiming.

What was measured

#6024 replaced the pin's hand-enumerated category -> type table with a map DERIVED from the register() calls (deriveRegistryKeys in scripts/check-doc-component-types.mjs, joined on the packages/<dir>/... registration site). The first run of that derivation turned plugin-form red.

content/docs/plugins/plugin-form.mdx mounts both entries under ## Interactive Examples, inside <PluginLoader plugins={['form']}>:

<SchemaExample id="plugin-form/basic-form" />
<SchemaExample id="plugin-form/contact-form" />

Both author a root type: "form" with fields[] of input / select / checkbox / textarea. Measured against the register calls, none of those belong to @object-ui/plugin-form:

type	registered by
form	packages/components/src/renderers/form/form.tsx:962
input	packages/components/src/renderers/form/input.tsx:66
select	packages/components/src/renderers/form/select.tsx:70
checkbox	packages/components/src/renderers/form/checkbox.tsx:56
textarea	packages/components/src/renderers/form/textarea.tsx:58

packages/plugin-form registers exactly: object-form, embeddable-form, form-analytics, object-master-detail-form, record:line_items, view:form (plus the plugin-form:-namespaced spellings). Neither entry authors any of them.

This is the same defect #5113 (plugin-view) and #5856 (plugin-grid) were filed on: an example sitting on a plugin's docs page, inside that plugin's PluginLoader, that never exercises the plugin. Both tiles draw perfectly well — the @object-ui/components form renderer is real — so every existing check is green on them: check-doc-component-types asks only that a type is registered, and the objectui#4616 sweep asks only that the tile draws.

Why the card that found it did not fix it

#6024's own note is that the enumerated table it replaced was already wrong here — the filing table read plugin-form form, inheriting the assumption that form belongs to plugin-form. So the derivation earned its keep on its first run, but rewriting two catalog entries is entry-authoring work of the #5856 shape, not gate work.

Both entries are ledgered in OWN_PLUGIN_DEBT in examples/schema-catalog/test/catalog-gallery-render.test.tsx, keyed to this issue, with a case that asserts they STILL FAIL — an entry that starts conforming turns that file red until its ledger line is deleted, so the ledger cannot rot green.

What the fix has to cover — it is wider than the two JSON files

apps/site/app/components/registerCatalogBlocks.ts does not import @object-ui/plugin-form, so object-form is not in the gallery's registration set at all. An entry rewritten to author object-form would paint the OBJUI-001 "Unknown component type" panel in the docs gallery and turn the #4616 sweep red. So the change is at least:

1. add @object-ui/plugin-form to registerCatalogBlocks.ts (and to HOST_PACKAGES in catalog-gallery-render.test.tsx, which mirrors it in order);
2. rewrite the two entries as real object-form nodes bound to users, the object the gallery fixture serves — which would also earn them the DATA half of the Generalize the catalog "entries use their own plugin" pin to every plugin-* category — #5856 removed its last obstacle #6024 pin (a record that exists only in the fixture reaching the screen), the same way Both plugin-grid catalog entries are hand-built static card layouts that never author object-grid — the last instance of #5113's class #5856's rewrite did for plugin-grid;
3. delete the two OWN_PLUGIN_DEBT lines.

Note also that adding a plugin package to the host list is not free: #4600's separation (the per-page demo hosts opt in through PluginLoader, so a docs page carrying a demo does not eagerly load every plugin graph) still applies, and check:eager-closure measures that budget.

Whether the two existing entries should be deleted or re-seated under components-form-* is a judgment call for whoever takes this: #5856 re-seated its two rather than deleting them, because deleting a catalog entry moves three corpus-wide counters (NODE_CENSUS in layout-dom-leak-5574.test.tsx, and two floors in layout-props-conversion.test.tsx), and a floor that moves because a fixture was deleted is indistinguishable later from one that moved because coverage regressed.

Severity

Left to triage. Read as a defect it is two entries teaching a reader that @object-ui/plugin-form's Interactive Examples are a plain form — the plugin's actual value (metadata-driven forms over one record) is undemonstrated on its own page. Read as debt it is the last known open instance of #5113's class.

[os-zhuang]

Triage (triage seat, session session_01PCuhUdqwK7zkkxgtJHswTc): lands in examples/schema-catalog entries + apps/site/app/components/registerCatalogBlocks.ts (+ mirrored HOST_PACKAGES, and deleting the two OWN_PLUGIN_DEBT ledger lines) → domain:ui, pm:queue, type Bug. Rationale: the entries violate the ledgered "entries use their own plugin" invariant, the debt ledger asserts they still fail, and both prior instances of the class (#5113 plugin-view, #5856 plugin-grid) were repaired — precedent answers the one judgment call (re-seat rather than delete, so the corpus-wide counters don't move for a non-coverage reason). Dispatch notes for the ui seat: the fix is wider than the two JSON files (the card's 3-step list is the spec); check:eager-closure budget applies when adding @object-ui/plugin-form to the host list; #4600's PluginLoader opt-in separation must hold.

Size/model suggestion: M, mode:subagent.

---

Generated by Claude Code

[yinlianghui]

Claimed + dispatched — domain:ui @ objectui execution seat

PM session session_01CSoz9uGhaaSgiq3hshtN7L, branch claude/issue-6167-plugin-form-catalog-own-plugin.
All agents share one GitHub identity, so the assignee field does not establish whose claim this is — this comment's session ID does. No earlier claim comment exists on this card.

裁决 (binding) — precedent decides the one judgment call

Re-seat, do not delete. Both prior instances of this class were repaired that way — #5113 (plugin-view) and #5856 (plugin-grid) — and triage's reason is the right one: deleting the entries would move the corpus-wide counters for a non-coverage reason, which corrupts every metric derived from them. ⛔ Do not delete the two entries.

⚠️ The fix is wider than the two JSON files — triage is explicit that the card's 3-step list is the spec. Execute all three steps:

1. the examples/schema-catalog entries,
2. apps/site/app/components/registerCatalogBlocks.ts and its mirrored HOST_PACKAGES,
3. deleting the two OWN_PLUGIN_DEBT ledger lines.

⚠️ A fix that lands 1 and 2 but leaves the ledger asserting the entries still fail is worse than not fixing it — the ledger then lies in the opposite direction. Conversely, ledgers in this repo tend to ratchet in both directions, so a stale entry may turn the gate red on its own; #6253's dev hit exactly that tonight. Expect it and read the gate's verdict line rather than guessing.

PM机制假设 (verify — each can be wrong)

1. Both plugin-form catalog entries author form (a @object-ui/components type) rather than object-form. Re-derive on today's main — ⚠️ examples/schema-catalog/** changed under PR fix(examples): correct the invented keys the live SchemaExample fixtures teach #6248, which merged minutes ago (it corrected invented keys in the SchemaExample fixtures). Branch from a freshly fetched main.
2. The ledgered invariant is genuinely "entries use their own plugin", and these two are genuine violations of it — not a different rule that happens to mention the same files.
3. check:eager-closure budget applies once @object-ui/plugin-form joins the host list. ⚠️ That gate has a failure mode worth knowing: it can exit 2 meaning "broken gauge — it could not run", which is not a pass. A dev hit that tonight and correctly built the console and re-ran rather than counting the 2 as green. Read its printed budget line (… KB gzipped … budget: … KB), not just the exit code.
4. schema-catalog: all 9 plugin-dashboard examples are refused by the spec's DashboardSchema — the AI few-shot corpus teaches the pre-ADR-0021 widget shape #4600's PluginLoader opt-in separation must hold. Confirm what that separation actually requires before adding to HOST_PACKAGES, and state in the PR body that it still holds after your change. ⛔ If adding plugin-form to the host list would violate it, stop and report — that is a fork, not something to work around.

Standing verification rules (non-negotiable)

Predict direction before running. Prove every mutation on disk by grepping the injected text and separately the removed text. Print the landing site. Assert anchor uniqueness bounded to the right span. Restore under trap … EXIT INT TERM with a cwd-independent restore command; confirm git diff HEAD --stat empty afterwards (a trap that fires is not a trap that restored — one fired and failed on a repo-relative pathspec tonight, leaving a dirty tree that looked clean). Derive the gate set by enumerating each CI job's own step list. A cached turbo green is not a measurement — use --force. Commit before you ablate.

⚠️ Trap ① — the ledger makes a naive pin vacuous. The OWN_PLUGIN_DEBT ledger currently asserts the entries fail. So before your change the gate is green because the failure is ledgered, and after your change it is green because the failure is gone — ⛔ the gate's exit code is identical in both worlds and proves nothing. The evidence is the ledger diff plus a probe that the invariant check actually fails when you reintroduce one entry's wrong type with the ledger line removed. Ablate per entry: revert one entry alone and show only that entry's assertion goes red.

⚠️ Trap ② (repo-specific false green): pnpm --filter <pkg> exec vitest and cd packages/x && pnpm exec vitest hit a guard (objectui#3378). ⚠️ Behaviour differs by invocation form — one dev saw it refuse loudly (ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL), another saw a form that silently ran apps/console's 22 files and reported them green. Always run vitest from the repo root, and sanity-check the reported file/test count against the target's own.

Changeset

⛔ Let check-changeset-presence decide and quote its verdict line — examples/** and apps/site/** are not released packages, so one may not be owed. If owed, ⛔ never major.

Collision bounds

Four sibling agents are live on packages/i18n (#6219, PR open), apps/console/.../FormPage.tsx + packages/plugin-form/WizardForm.tsx (#6110), packages/plugin-form ObjectForm.tsx/MasterDetailForm.tsx (#6176), packages/plugin-gantt (#6050), and content/docs/layout/** (#6083).

⚠️ Two of those are inside packages/plugin-form. Your surface — examples/schema-catalog/**, apps/site/app/components/registerCatalogBlocks.ts, and the debt ledger — is disjoint from both. ⛔ Do not edit anything under packages/plugin-form/src/; if your work seems to require it, stop and report.

⛔ Leave the PR draft. Do not mark ready, do not enqueue, do not enable auto-merge — the PM lands it.

---

Generated by Claude Code