Introduce a two-tier widget model and clearer chrome names. No external consumers yet, so the breaking renames land now. Controls vs Fields (controls/, was fields/): - Extract a bare `*Control` for every value input (Text/Number/Textarea/ Slider/Select/Color/Boolean) — pure widget: value/onChange, widget props, readonly, a `level` prop (→ data-stage-level) + forwarded validation handlers. No caption, no Field, no validation. - Refactor each `*Field` to compose its control as the single source of truth (BooleanField excepted — its caption must live inside the Kobalte root for label association, so it keeps bespoke wiring; BooleanControl is a parallel bare widget). - Share `ControlValidationProps` (level + focus/hover handlers). Chrome rename (layout/, was panes/): - SidePane → Panel, Module → Section, EditorPanes → EditorPanels. - EditorPanels slot props leftSide/rightSide → leftPanel/rightPanel. - localStorage prefixes stage-pane:/stage-module: → stage-panel:/stage-section:. - CSS: .stage-pane*/.stage-module* → .stage-panel*/.stage-section*; matching token renames (panel-header-height, section-header-pad/body-pad, color-section-header-*). Other: - LabelField → Label (bare display, no suffix). - Add seven `*Control` exports + types; bare-control demo in the playground. - Update architecture.md (Control/Field taxonomy), README, CLAUDE.md, NEXT-UP. typecheck + 248 tests + build all green.