5 Commits (599c142124b706f5d693e2edf4e8f394ee790fca)

Author	SHA1	Message	Date
dev	599c142124	feat(eidos): non-modal menus + unified list-surface size layer (control-height rows) ... Non-modal menus: - DropdownMenu + ContextMenu default to trapFocus=false + preventScroll=false (were modal — hard focus-trap + body scroll-lock that made them feel stuck). Menus stay navigable while open (Chakra-style); the props remain for an opt-in modal menu. morfo focus.trap=false + the demo control defaults aligned. list-surface — ONE shared size source for list surfaces: - new lib/list-surface.css (--list-* keyed on [data-list-surface][data-size], 1:1 with the control sizes) + lib/list-surface-context.ts (shared size context for portaled sub-panels). DropdownMenu/ContextMenu/Menubar/Listbox bridge their --{c}-* size tokens to --list-*; ContextMenu gained the size axis it lacked. Row-height doctrine — unified to CONTROL-HEIGHT: - archetypes.css [data-archetype=item/option] gains a fallback-guarded control- height FLOOR (min-block-size: var(--list-item-height, auto) + padding-block: var(--list-item-py, var(--space-1-5))) — ZERO regression off a list-surface (the ~45 non-list archetype consumers are untouched). Select/Combobox/Command stamp data-list-surface so their option rows inherit the floor, matching menu items. Verified: select option md 36px / lg 44px = menu items; bare archetype item unchanged (0 floor, --space-1-5 padding). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	f8056f438b	fix(demos): eliminate each_key_duplicate crash in 22 component demos ... The event-trace inspector in each demo keyed its `{#each}` by a `Date.now()` timestamp (`entry.at` / `h.at`). A single interaction can stamp `data-event` on several elements within the same millisecond, so two trace entries share the key and Svelte throws `each_key_duplicate` (reported on dropdown-menu). The trace is an ephemeral, 3-item, text-only log with no transitions or stateful children, so positional reconciliation is correct: drop the timestamp key (the each becomes unkeyed). The `fmtTime(...at)` display is left intact. Swept all 22 demos carrying the pattern (21 keyed by `entry.at` + announce by `h.at`): dropdown-menu, context-menu, menubar, navigation-menu, listbox, grid-list, table, tree-view, tree-grid, feed, command, carousel, drag-drop, clipboard, announce, alert-dialog, button, color-field, link-preview, range-calendar, time-field, time-range-field. Verified: `as \w+ (\w+.at)` -> 0 occurrences site-wide; `npm run check` 0 errors; browser repro on dropdown-menu + table (burst of events, no each_key_duplicate, console clean). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	4b5bd9f35d	refactor(dropdown-menu): remove unused modal; Trigger→Button; canon vocab fixes ... Three related fixes touching the menu surface: 1. **Remove `modal` from DropdownMenu** (#127). The prop was declared in soma but never wired to anything — no overlay, no pointer-events blocker, no scrim. ark-ui / Headless-UI / Chakra all treat menu as non-modal by convention; Dialog/Drawer/AlertDialog cover blocking semantics. Drop it from soma (types, provider opts, component, test fixture), the eidos doc comment, the menubar consumer, and the dropdown-menu demo (state, control, snippet, API table, parity table). 2. **DropdownMenu.Trigger now renders `<Button>` internally** (#120 first consumer). Default variant='surface', size='md', intent='neutral'. `variant` is narrowed to ControlVariant (`'surface' | 'outline' | 'ghost'`) per DEMO_AUTHORING_GUIDE §12.7 so the trigger stays consistent with the form-control surface (Field/Select/Combobox) instead of inheriting Button's wider 6-variant set. The eidos demo exposes variant/size/intent chips that match the canonical narrowed vocab (Intent: neutral · affirm · fulfill · risk · threat · loss). Trigger's per-recipe CSS dropped — chrome comes from button.css. 3. **Menu-item unchecked indicators** (follow-up to #118). CheckboxItem and RadioItem now paint an empty outlined box / circle even when unchecked, so the user can tell at a glance which rows are checkable. Checked state fills with the accent color via the same `::before`. The reserved padding slot (26px) keeps row text from shifting when state flips. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a804c39208	feat(eidos): Button + 9 demo rebuilds + picker recipe polish ... Build: - New <Button> compound (morfo + soma + sema + eidos): 6 variants (solid/soft/surface/outline/ghost/plain), 8 colors, 5 sizes, optional icon/endIcon snippets, loading state with built-in Spinner, asChild Slot pattern, intent-driven sema (commit-action with fromProp:intent). Demo rebuilds (canonical depth per DEMO_AUTHORING_GUIDE): - context-menu, dropdown-menu, pin-input, alert-dialog, toggle-group: full per-part Morfo contracts, reference-parity tables, ARIA contract tables, keyboard tables, composition controls. - color-field, time-field, time-picker, time-range-picker, color-picker, month-grid, year-grid: same canonical treatment; per-part data/aria/ keyboard iteration of raw morfo, reference parity vs react-aria/ ark-ui/Chakra/bits-ui/Mantine. Picker recipe polish: - PickerShell.Clear/Cancel/Close refactored to use <Button size="xs"> (affects 5 pickers — date / date-range / time / time-range / color). - TimePicker + TimeRangePicker: popover condensed (min-width 18rem -> 14 / 32 -> 28), per-channel accent (hour=primary, minute=secondary, second=neutral; end variant muted), ruler off by default, hour ruler cleaned to 0/6/12/18/23. - ColorPicker: typography token --_color-picker-trigger-font-size that scales with data-size (10/12/14px); autoFormat default true; Area recipe override for [data-x-channel='hue'] with rainbow gradient + saturation/brightness Y overlays. - ValueText eidos wrapper: fix children snippet bug that suppressed soma's displayValue fallback. - date-field.css: segment editing affordance (cursor + hover + active ring) via new --_date-field-accent-element token across 8 color cascades. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	4e477e637b	feat(dropdown-menu): port from soma to eidos (Tier 1 sprint, 3/5) ... Full 15-part compound — pass-through wrappers over soma with the canonical visual recipe. Parts: Provider · Trigger · Content · Arrow · Item · Group · GroupHeading · Separator · CheckboxItem · CheckboxGroup · RadioGroup · RadioItem · Sub · SubTrigger · SubContent. API parity with Bits UI (richest reference): CheckboxGroup + RadioGroup binding arrays / scalars, nested Sub-menus, Arrow pointer. Radix Primitives + Ark UI lack CheckboxGroup; Chakra v3 + Radix Themes lack Arrow. Recipe (dropdown-menu.css): - Uniform chrome across Content + SubContent (panel shadow, border, padding, max-height) - Items share one set of tokens (hover/focus highlight, disabled opacity, indicator slot via `::before` for Checkbox/Radio data-state='checked') - SubTrigger gets a chevron via `::after` - GroupHeading: muted uppercase, micro-tracked - Separator: 1px subtle divider - Enter animation on `data-state='open'` No `variant` / `color` / `size` knobs at the eidos layer — menus are themselves the visual variant of "list of actions" within an app. Per-item destructive coloring deferred to next pass (cascade via item's `data-color` attr). Morfo scope: ['soma'] → ['soma', 'sema', 'eidos']. Sound comes from the family bases (`emerge` for open/close, `commit` for select) — no per-component cascade needed. Demo: 6-tab template, items hooked to `lastSelected` tracker, all three groupings demoed (Items / CheckboxGroup / RadioGroup / Sub). Checks: svelte-check 0 errors, component:audit 91/91 PASS. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago