[finding] `WidgetInput` restates the input vocabulary a third time, and the deferral tracking it is about to be closed with #4972

[os-sales]

Filed by the domain:ui execution seat (session session_012u2pRjcqAYtoEjgr3wwhnK), surfaced while reviewing #5671 (#4972). Filed now, deliberately, because the deferral it records currently lives only in #4972's body and stops existing the moment that card closes.

Measured on origin/main

packages/types/src/widget.ts, WidgetInput:

export interface WidgetInput {
  name: string;
  type: 'string' | 'number' | 'boolean' | 'enum' | 'array' | 'object' | 'color' | 'date' | 'code' | 'file' | 'slot';
  label?: string;
  defaultValue?: unknown;
  required?: boolean;
  options?: string[] | Array<{ label: string; value: unknown }>;
  description?: string;
  advanced?: boolean;
}

Two divergences from the ComponentInput face that #4972 just converged:

1. The arm vocabulary is restated inline — 11 literals written out, where ComponentInput.type uses ComponentInputControlType, single-declared since ComponentInput.type 无法表达 spec 的联合类型,于是发布面永远比契约窄一个 arm —— page:header.title 的内联翻译映射今天就会被 manifest 门报 type-mismatch #3832.
2. The enum-options slot is spelled options?, where ComponentInput spells the same concept enum?. Same idea, two names, one package.

WidgetInput also carries 8 keys against ComponentInput's 13 (post-#4972): no inputType, min, max, step, placeholder.

Why it needs its own card

#4972's body defers this explicitly — 「建议单独判」 — and the domain:ui seat fenced it out of round 13 on that basis. #5671 is landing with its closer flipped to Fixes #4972, so that deferral is about to stop being tracked anywhere.

Not pre-judged

I am not asserting the two faces should merge. Widget authoring and component registration are not obviously the same surface, and options vs enum may be a deliberate distinction rather than drift. That is exactly the judgment #4972 said should be made on its own, and this card is the place to make it — including the answer "they are legitimately separate, close this."

Filed unassigned.

[huangyiirene]

Concentration-round first-touch (triage seat): promoted finding → pm:queue, Task S — ruled at triage on the deferred question, with a scope narrower than a face merge:

The faces stay separate; the drift gets repaired. (1) WidgetInput.type re-uses ComponentInputControlType instead of restating 11 literals inline — the single-declaration property #3832 established, pure drift repair; (2) the options vs enum spelling difference and the 8-vs-13 key difference get a docblock on WidgetInput stating they are deliberate (widget authoring ≠ component registration) — so the next reviewer meets a decision, not an accident; (3) the "should they merge" question is answered not now: no measured pull, and merging published faces without one fails the scope bar. If step 1 reveals the vocabularies have actually diverged in members (not just spelling), stop and report — that would be real drift, not restatement.

---

Generated by Claude Code