feat(ui): canonical Input/Textarea onto Base UI, retire native ui.tsx Input (#520 item 22)

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable

[Astro-Han]

Summary

#22 PR10: collapse the dual Input tracks onto one canonical primitives/input.tsx + primitives/textarea.tsx, retiring the native ui.tsxInput/Textarea.

Why

Refs #22 / #520. The renderer had two parallel Input implementations: the native ui.tsxInput (single <input> + inputClasses, focus-visible:ring-2, used by 44 call sites across 9 settings files) and the Base UI primitives/input.tsxInput (span data-slot="input-control" wrapper + inner Base UI Input + ring-[3px], used by InputGroup). bare-field-chrome-contract pinned the native's data-maka-field-chrome + border-input + ring-2, so retiring the native was not a clean look-preserving swap — it needed inputClasses ported into the Base UI primitive, InputGroup updated to avoid double chrome, and the chrome contract rewritten.

Scope

Changed:

• primitives/input.tsx now wraps Base UI's Input primitive with maka's inputClasses styling ported as the default chrome. Stays a single <input> (no span wrapper) so caller CSS targeting > input / input:focus-visible still matches. unstyled gives the bare form (bareFieldClasses + data-maka-field-chrome="none") for Field/InputGroup embedding.
• primitives/textarea.tsx parallel shape: single <textarea> + inputClasses + textarea sizing. Base UI ships no Textarea, so this is a native textarea. Drops the Base UI Field.Control + span wrapper (callers don't use Field).
• ui.tsxInput, Textarea, inputClasses, bareFieldClasses retired. inputClasses + bareFieldClasses moved into primitives/input.tsx (exported) so number-field keeps its standalone NumberFieldInput chrome.
• InputGroup: InputGroupInput/InputGroupTextarea already pass unstyled (inner field bare, InputGroup owns the chrome — no double chrome). InputGroup CSS updated to key off data-slot="input"/"textarea" (the single element) instead of the retired span data-slot="input-control"/"textarea-control"; dropped the span-only :contents / :before:hidden rules.
• index.ts re-exports primitives/input + primitives/textarea as the canonical Input/Textarea; the 44 settings usages keep importing from @maka/ui unchanged.
• Internal packages/ui imports (composer, plan-reminder-panel, skills-panel) + stories repointed at the primitives.
• Contracts: new input-canonical-contract (single element, inputClasses token lock, ui.tsx retired, bare-field shape); field-chrome.test rewritten for the unified shape (drops nativeInput/h-8.5/field-sizing-content assertions that pinned the old primitives/input vs ui.tsx divergence); radius-convergeinputClasses tier repointed at primitives/input.tsx.

Not included:

• PR8 combobox migration (SearchModal + CommandPalette) — separate PR, runtime keyboard interaction risk.

Verification

• npm run typecheck — clean.
• npm run -w @maka/ui test — 43/43 pass.
• npm run -w @maka/desktop test — 2069/2069 pass.
• npm run -w @maka/ui build + npm run -w @maka/desktop build:main — clean.
• Screenshot pixel diff vs main (ImageMagick compare): settings-general and settings-bots light/dark 1280 AE=0 (pixel-identical, both contain Input). settings-data 364 px (edge); settings-appearance/settings-daily-review ~9-10K px in a 12px right-edge column (window edge, not input/textarea); settings-memory ~18K px in a large content block (main-branch composer/sidebar commits feat(sidebar): add project-grouped session view mode #510/feat(composer): workspace picker, git branch switching, and composer defaults persistence #511, not this PR).

User-facing impact

None intended. Input/Textarea visuals are preserved by porting inputClasses (min-h-9, border-input, bg-foreground oklch 0.02, px-3 py-2, shadow-sm, focus-visible:ring-2 ring-offset-2) into the Base UI primitive. The DOM changes from a single <input> (ui.tsx) to a single Base UI <input> — still a single <input>, so caller CSS targeting > input keeps matching.

Reviewer notes

• The single-<input> decision is load-bearing: maka CSS has .settingsRow > input / .settingsField input:focus-visible / .providerEditor input:focus selectors. A span wrapper (the old primitives/input shape) would break the > input direct-child selectors. So the Base UI Input primitive is used directly with inputClasses on it, no span.
• inputClasses + bareFieldClasses are exported from primitives/input.tsx (not a shared util) because they are the canonical field chrome and number-field is the second consumer of inputClasses for its standalone NumberFieldInput.
• Textarea drops the Base UI Field.Control wrapper because no caller uses Base UI Field with it; it's a plain native <textarea> with inputClasses. Base UI ships no Textarea component.
• Commits are independent revert targets; squash on merge.

Checklist

• Scope matches the PR title and excludes unrelated changes
• Verification lists commands/results, or explains why they were not run
• User-facing impact, docs, changelog, migrations, and breaking changes are noted, or marked none
• Risk, rollback, or review focus is called out for non-trivial changes
• UI changes include screenshots/video, or explain why not applicable