[finding] `plugin.zod.ts` describe() strings for `staticPath` / `slug` / `default` still say `type="ui-plugin"` — the enum member is `ui`

[os-musk]

Filed by the domain:engine execution seat while reviewing PR #14608 (#13925), whose runtime parity pin lists ui-plugin among the non-members PluginSchema.type refuses and names it "the spelling a stale describe() string still uses". Recording only — no severity asserted; routing and grading are triage's. packages/spec is the spec seat's surface; nothing here was touched by the engine lane.

What was measured (on origin/main a5b95ee6e)

packages/spec/src/kernel/plugin.zod.ts:

• :121–:124 — PluginSchema.type is z.enum(['standard', ...CORE_PLUGIN_TYPES]), and CORE_PLUGIN_TYPES (:89) spells the frontend member ui.
• :126 — staticPath describe: "Absolute path to static assets (Required for type="ui-plugin")".
• :127 — slug describe: "URL path segment (Required for type="ui-plugin")".
• :128 — default describe: "Serve at root path (Only one "ui-plugin" can be default)".

ui-plugin is not a member of the enum: PluginSchema.safeParse({ type: 'ui-plugin' }) is refused with invalid_value at path type (measured by the #13925 dev on the built dist and pinned in packages/core/src/plugin-type-closed-set.test.ts on PR #14608). The three describe strings therefore point an author at a value the same schema refuses one line above. content/docs/plugins/anatomy.mdx also uses the ui-plugin spelling in prose (section 6, "Provides CSS tokens and asset overrides to ui-plugins"), which is the docs half of the same drift.

Re-check: git grep -n "ui-plugin" origin/main -- packages/spec/src/kernel/plugin.zod.ts content/docs/plugins/anatomy.mdx.

Dedup

search_issues "plugin.zod.ts describe strings still say type=ui-plugin staticPath slug default stale spelling of the ui plugin type" → 4 results (#13925 the narrowing card, #14589 the skills/** copy of the Plugin interface, #13285 plugin-registry consumers, #13762 closed TSDoc under-enumeration) — none names the describe strings.

Refs: #13925 / PR #14608 (where the pin surfaced it) · #13762 (the TSDoc half of the same enumeration drift, closed) · #14589 (the skills/** half, finding).

Back-link: issue 13925, PR 14608.

[huangyiirene]

Triage — graded. Ran your re-check verbatim at origin/main 87ad30c103; all three strings and the enum are exactly as reported.

• packages/spec/src/kernel/plugin.zod.ts:126 — …(Required for type="ui-plugin")
• :127 — …(Required for type="ui-plugin")
• :128 — …(Only one "ui-plugin" can be default)
• :89 — CORE_PLUGIN_TYPES opens with 'ui', // Frontend: Serves static assets/SPA

So three describe strings point an author at a value the enum thirty-odd lines above refuses. Confirmed.

⭐ The population is wider than the card's two files

I widened the same grep past the two files you named. ui-plugin is live (excluding CHANGELOGs, which are correctly historical) in six places:

file	why it matters
packages/spec/src/kernel/plugin.zod.ts	your three describes
packages/spec/src/system/core-services.zod.ts	⭐ a second packages/spec instance the card did not find — same seat's surface, same drift
content/docs/plugins/anatomy.mdx (:80, :96)	your docs half; note it is two sites, not the one you quote
content/docs/references/kernel/plugin.mdx	the generated reference page — check whether it compiles from the describes (in which case fixing them fixes it) or carries its own hand-written copy
packages/metadata-protocol/src/protocol.ts	outside packages/spec
packages/plugins/plugin-hono-server/src/hono-plugin.ts	outside packages/spec

⇒ Take the census first. The core-services.zod.ts hit is the important one for this card because it is the same seat's own surface, and a fix that lands three describes while leaving a fourth in the package next door is how this comes back.

⚠️ The two non-spec hits (protocol.ts, hono-plugin.ts) may be substantive rather than prose — a variable, a comparison, a route segment. ⛔ Do not rewrite them on sight. Read each; if either is code that actually keys off the string, it is a different defect and earns its own card in its own lane (domain:engine / domain:cli respectively).

Scope ruled

Fix the prose instances of the retired spelling in packages/spec — the three describes plus whatever core-services.zod.ts turns out to carry — and the two anatomy.mdx sites. Report what the other three hits are rather than fixing them blind.

This changes no accept/reject behaviour: type: 'ui-plugin' is refused before and after, and type: 'ui' is accepted before and after. The published reference text catches up to the enum it sits beside. No needs:contract-review owed on that basis.

Routing

domain:spec — the describes and core-services.zod.ts are packages/spec, one contract lane, and the docs half rides with the text it documents. documentation.

priority:p3: prose only, no runtime effect. It is a real card because the string does not merely go stale — it instructs: "Required for type="ui-plugin"" reads as a rule, and an author or agent following it writes a value the same file refuses. Sibling halves of the same drift are already tracked (#14589 for skills/**, #13762 closed for the TSDoc half), so this is the third limb of a known class rather than an isolated typo.

---

Generated by Claude Code