# Changelog ## 1.1.4 — 2026-07-14 Light-theme support — the controls whose chrome was hardcoded dark now adapt. ### Themeable LED well - **`ledWell` theme token** — the recessed "screen" fill behind the LED segments of `LEDKnob`, `LEDFader`, `Meter`, and the default well of `SegmentDisplay` / `AlphaDisplay`, now comes from the theme instead of a hardcoded near-black. Dark base keeps the classic dark well (`#0b0d0e`); the **light base is `transparent`**, so LED controls and readouts render as clean flat segment rings / bar meters / digits on the light panel (still clearly "LED" from the lit segments) instead of dark blobs. The `faceColor` / `background` props still override per-instance. ### Light-theme panel chrome - **`scheme` theme token** (`'dark' | 'light'`, set by the `base`) drives the raised gradient/border/shadow of `PushButton` (and `Button`), `TransportButton` and `SegmentSwitch`. On a light base they render as light raised buttons instead of dark chips; unlit LED pips flip to a faint dark so they still read. New `panelButtonChrome(scheme, pressed)` helper. - Fixes the whole panel-button/switch family looking like dark chips on light themes; the flat knobs and faders already adapted (their face is the `face` token). ## 1.1.3 — 2026-07-14 Fourth integration-feedback release — a composability fix for buttons, a much smarter meter, and the pan control the mixer was missing. ### Buttons - **Action buttons no longer show an LED by default.** `Button` (and `PushButton mode="action"`) are plain by default — an action has no state to indicate. `led` defaults to `'strip'` for `toggle`/`momentary` (which do have a state) and to `false` for `action`; pass `led="dot"` / `led="strip"` to opt a command button back in. ### Buttons compose as Radix triggers - `PushButton` / `Button` now forward unknown props (`...rest`) to the underlying `