11 Commits (d797a0cebc2e92d58af8cdad170d6109f2396c3a)

Author	SHA1	Message	Date
dev	d797a0cebc	feat(motion): M9 F1c+F2 — dropdown-menu item cascade (children-DOM) ... F1c (exit-heavy): DomCascade.pending() aggregates the items' finished so the owner Presence holds the subtree until the exit cascade settles (PresenceOptions.pending, Presence.startPhase). beginEnter drives the enter from the off-state with the transition suppressed (items mount in the on-state, so a passive mirror would ease toward off instead of jumping). pending() settles each finisher (then(noop,noop)) so one cancelled row can't collapse the wait. F2: wire the children-DOM cascade into the real dropdown-menu. Content part declares animation.surface+staggerChildren; provider routes an opt-in 'animation' prop, runs a DomCascade over getCascadeRows (every visible row incl. disabled), forwards a pending hook through the floating shell. Coexistence fixes surfaced by the menu: item rows hand their transition to the cascade-* preset via a higher-specificity rule (longhands keep the stagger delay); disabled opacity gated off during the cascade; the panel's own dismiss-fade signature suppressed in cascade mode (data-cascade) so it doesn't fade the panel before the rows finish; the trigger is excluded from the menu's dismissal so the toggle closes (pre-existing bug). Verified in a real browser (Playwright): enter+exit cascade with reversed stagger, all four close methods, disabled row fades. dom-cascade 9/9, check 0 new errors. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	2d562f3788	feat(sema): Lectura C steps 5-8 — 11 sema packs + doctrina samples ... Step 5 — 3 packs alta-frecuencia (silencio + tap leve): switch, toggle, toggle-group + tuning `form.toggle.silent: { gain: { op: 'add', value: -0.3 } }` Step 6 — 6 packs menús + árboles (emerge.soft / form.commit.subtle): menubar, navigation-menu, dropdown-menu, context-menu, tree-view, tree-grid Step 7 — card scope: KEEP `sema` + `family-default` (sin código). Step 8 — 2 packs (versión lean tras descartar 5 prematuros): tooltip (silent-by-default) collapsible (mirror accordion) + tuning `tooltip.silent: { gain: { op: 'add', value: -0.2 } }` Doctrina codificada en LIBRO_VARIACIONES_Y_EXTENSIONES.md: - D.5 — packs alta frecuencia (toggles) - D.6 — packs superficies menú / árbol - D.7 — sonido canónico vs samples SOUND_LIBRARY = recursos | SOUND_TUNINGS = canon | packs = composición samples NO sustituyen firma con intent.deltas sampleOverlay descartado permanentemente (sobreingeniería) family signal admite excepción para marcas culturales Cierra Lectura C steps 5-8 del audit-codex P1 #3. Total: 11 packs nuevos sobre 9 perfiles canónicos de tuning. 195/195 tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	504780ad8b	feat(morfo/sema): add expression field + sema coverage check (P1 #3) ... User doctrinal decision 2026-05-26: `scope: ['sema']` declares **participation** in sema. It does NOT impose the obligation of shipping a pack. The new `expression` field on Morfo declares HOW the component contributes its perceptual signature. Schema change (src/uix/morfo/types.ts + schema.ts): type SemaExpressionMode = 'pack' | 'family-default' | 'delegated' | 'none'; interface Morfo { // ... expression?: SemaExpressionMode; } Semantics: - 'pack' — sema/components/{kebab}.ts cascades the signature - 'family-default' — use family base + intent deltas as-is (no override) - 'delegated' — composite; perceptual expression lives in children's packs - 'none' — explicit opt-out (rare; reserved for headless contracts) Coverage check (scripts/morfo-vocabulary-check.ts §4): FAIL events declared + no 'sema' in scope — incoherent WARN scope:sema + events + no pack + no expression — ambiguous OK scope:sema + events + (pack OR expression) — explicit OK no events — coverage N/A Pack discovery is automatic from filesystem; the morfo doesn't need to declare `expression: 'pack'` redundantly. Lint passes when a pack file exists at `src/uix/sema/components/{kebab}.ts`. Applied to 5 morfos that had events but no sema scope (incoherent state): - announce, clipboard, listbox, virtual-grid, virtual-list now declare scope: ['soma', 'sema'] + expression: 'family-default'. Applied to 28 morfos that had scope:sema + events but no pack: - 4 composites (date-picker, date-range-picker, time-picker, time-range-picker) → expression: 'delegated' - 24 others (button, card, carousel, collapsible, color-field, command, context-menu, drag-drop, dropdown-menu, feed, grid-list, menubar, month-grid, navigation-menu, range-calendar, switch, table, time-field, toggle-group, toggle, tooltip, tree-grid, tree-view, year-grid) → expression: 'family-default' The 29 morfos that already have packs are not touched; the lint discovers their packs from the filesystem. Pending follow-up (separate commits per author's plan): - Create packs for high-frequency toggles (switch, toggle, toggle-group) - Create packs for menus / navigation / tree (menubar, navigation-menu, context-menu, dropdown-menu, tree-view, tree-grid) - Review card scope (may not need sema scope at all) - Per-component review of the rest Verification: - npm run morfo:vocabulary: EXIT 0 - 0 coverage FAILs, 0 coverage WARNs - vitest src/uix/sema src/uix/morfo: 195/195 pass - 7 name-shape WARNs remaining are all words.* (separate dev track) Closes P1 #3 from src/uix/audit-codex-full-1.md (Sema coverage policy). 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
dev	98fc40bf62	batch A-3.1: add semantic events to 12 interactive morfos ... A pass over every component flagged "interactive with 0 events" (audit A-3.1) plus the texts.label slot they all shared. The events follow the canonical sema families and reuse the focus-move filtering installed earlier so the audit no longer treats keyboard navigation as missing coverage. Per-component event additions: - listbox: commit-select, commit-unselect (affirm/neutral, target=item) - toggle-group: commit-toggle (intent fromProp, target=item) - grid-list: commit-select, commit-unselect (target=item) - context-menu: open, close, commit-select - dropdown-menu: open, close, commit-select - menubar: commit-select - navigation-menu: commit-select - tree-view: commit-select + shift-expand + shift-collapse - tree-grid: commit-select + shift-expand + shift-collapse - table: shift-sort + commit-select + shift-expand-row - carousel: shift-slide - feed: commit-load-more + shift-focus-item - command: commit-invoke (palette item invocation, intent fulfill) - splitter: commit-resize (handle settle, not continuous drag) - drag-drop: commit-drag-start + commit-drop + commit-cancel - color-field: commit-set - time-field: commit-set Each got a `texts.label` slot + matching catalog entry. New catalog files for context-menu / dropdown-menu / menubar / toggle-group; existing files extended for the rest. Audit: PASS 25 → 33 in one batch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	37de27fcf2	Declare interactive data attrs in morfos	5 months ago
dev	aba18117ba	morfo: catalog `archetype` across 65 components (~265 part declarations) ... Bulk classification pass that gives every part a cross-component archetype where one applies. Done with `scripts/catalog-archetypes.ts` — a one-shot mechanical mapping based on a kebab → archetype table, plus three manual overrides for components where Provider IS the interactive element. Coverage - 440 part declarations examined. - ~265 received an archetype (provider, trigger, content, overlay, viewport, item, indicator, thumb, track, label, title, description, close, action, header, image, fallback, arrow, separator, group, input, segment). - ~175 left without one — genuinely component-specific (Slider.Range, PinInput.Segment internals, color-picker channel-slider, etc.). Manual overrides (Provider IS the trigger) - Toggle, Switch, Checkbox: their `Provider` part is a `<button>` that the user actually interacts with, not a root container. Archetype set to `'trigger'` instead of the default `'provider'` so eidos can style them alongside Dialog.Trigger / Popover.Trigger / etc. Script (scripts/catalog-archetypes.ts) - Walks every `*.ts` under `src/uix/morfo/components/`. - Inserts `archetype: '...'` directly after the matching `kebab:` line when a mapping exists. - Idempotent — skips parts that already declare an archetype. - Indent-aware — only operates on part kebabs (≥2 tabs), never the morfo root kebab. Bug discovered + fixed mid-pass when radio-group's root kebab `'radio-group'` matched the `'radio-group' → 'group'` alias and inserted at the wrong level (cleaned up by hand). - Reports per-file counts + the list of unmapped kebabs at the end so future passes can extend the mapping. Tests - Updated `omits data-archetype when not declared` test to use a tiny inline morfo (Toggle's Provider now has archetype 'trigger', so it can't be the "no archetype" fixture anymore). Verification - 22/22 runtime tests, full focused suite green. - 66/66 morfo-check (every component still validates against its DOM — archetype is additive, doesn't change emitted attrs apart from the new `data-archetype="..."` which morfo-check doesn't enforce yet). - 68/68 smoke routes. - svelte-check unchanged at 155.	6 months ago
dev	8d4f53a73f	soma/morfo: typed createAttrs + 6 audit batches + form hang fix + A36 ... ## morfo: typed createAttrs - `types.ts`: all array fields are now `readonly` so morfos can be authored with `as const satisfies Morfo` without casts. - `createAttrs` is a generic `<const M extends MorfoShape>` that infers the emitted attr map from the morfo's literal shape. Typos like `attrs.trigerr` are now compile errors; autocomplete lists every valid part. - All 66 morfos migrated: `export const xMorfo = { ... } as const satisfies Morfo`. - Two latent bugs the new typing caught: `dateRangeFieldAttrs.root` and `timeRangeFieldAttrs.root` — legacy from the root→provider refactor, fixed to `.provider`. - Docs (morfo/README, COMPONENT_GUIDE) mandate `as const satisfies Morfo`; the older `: Morfo` annotation widens literals and loses autocomplete. ## Audit batches 1–7 (soma-audit-2026-04-20) Batch 1 — Keyboard a11y (A14/A12): - Tabs: `isFallbackTabStop(el)` using `untrack` → first trigger gets `tabindex=0` when no tab matches (WCAG 2.1.1 was failing). - RatingGroup: `dir` prop + `getDirectionalKeys(dir, 'horizontal')` for RTL. - Accordion P1-1/P1-6 dismissed: roving/labelledby already correct per APG. Batch 2 — A33 reactive collections: Select `labelRegistry` and NavigationMenu `triggerRefs` migrated to `SvelteMap`. Batch 3 — A31 O(N²) fix: RadioGroup lifts `hasSelection` + `isFallbackTabStop` to the provider with `untrack`-wrapped DOM walk. Per-item derivations drop from O(N²) to O(1) per trigger. Batch 4 — Morfo aria sync: toast / time-field / date-field / tabs / tag-group / navigation-menu declare every aria the provider emits (14 entries across 6 files). Batch 5 — Accessible naming props: Tabs.List, ToggleGroup, TreeView, NavigationMenu expose `aria-label?` / `aria-labelledby?` with explicit "required unless labelledby is set" JSDoc. Batch 6 — A30 cleanup: Checkbox `setLabelId` and 5 trigger-ref providers (select/tooltip/link-preview/dropdown-menu/context-menu) migrated from `$effect(() => parent.ref = opts.ref)` to the `Provider` base's `onRefChange` callback (fires via attachRef inside `untrack`). Batch 7 — A11 wrapper thinning: stepper/tree-view wrappers removed `ctx.get()`, providers expose proxy derivations; time/date-range-field inputs use `untrack(() => …)` for one-shot id registration; menubar content's 40-line keyboard nav moved to `MenubarMenuProvider.onContentKeydown`; color-picker area + channel-slider pointer state machines moved to the providers with `onpointerdown/move/up` emitted via `props`. form-auto-fields deferred with justification (reflective schema renderer, not a state-holding wrapper). ## Form hang fix (A36) `runValidate` entered the `isPromiseLike` branch even for sync schemas because sium's Standard-Schema adapter declares `validate: async`. The fallback `return { errors, issues }` read both reactive vars inside the validation `$effect` while the `.then(...)` microtask wrote them → microtask-mediated loop, silent to Svelte's sync effect-depth guard. Symptom: kitchen-sink hung the tab on mount with onChange / onBlur. Fix: `return untrack(() => ({ errors, issues }))`. Regression locked by two new 5s-timeout tests in `form-auto-fields.svelte.test.ts`. Pattern codified as A36 in COMPONENT_GUIDE; CLAUDE.md count updated to A1–A36 / 39 items. ## Verification - `npm run check`: 0 errors in soma/morfo scope (sema demo pre-existing errors untouched). - `npx vitest run src/uix/soma src/uix/morfo`: all tests green (94 + 7 = 101 tests, inc. 2 new form regression tests). - `npm run smoke`: 65/65 routes. - `npx tsx scripts/morfo-check.ts`: 66/66 morfos. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	6 months ago
dev	91257e8526	soma/morfo: rename root part → provider + fix toolbar effect loop ... Naming coherence across the part layer: the root part's `kebab` field now matches its `name: 'Provider'`. The `createAttrs` special case still emits `data-{component}` (no suffix) for the provider part — the DOM contract is unchanged, only the authoring name changes. Affected: - createAttrs special-case: 'root' → 'provider' - 66 morfos: kebab 'root' → 'provider' - 77 soma provider files: `attrs.root` → `attrs.provider`, constructor part arg 'root' → 'provider' - Docs: A2 rule rewritten, morfo/README, soma/README example updates - Test / schema / morfo-check: updated for new kebab Toolbar fix: remove `itemsVersion` counter and per-item `$effect` blocks that called `notifyItemsChanged()`. The pattern was an A30 violation — each item's $effect read `ref.current`/`disabled` and wrote back to the provider, which cascaded through `firstTabStop` → per-item `props` $derived → DOM reattach → effect re-run, triggering `effect_update_depth_exceeded` on page load. `isTabStop` now uses `untrack` around the DOM walk so per-item `props` derivations only depend on `lastFocusedElement`. Verification: 7/7 morfo tests, 65/65 smoke, 66/66 morfo-check, no effect loops detected across any demo page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	6 months ago
dev	0222af7a0b	morfo: enrich 65 components with aria + keyboard + focus contracts ... Each morfo now declares what its provider actually emits (via agent-based extraction from provider code). Before: parts + data only. After: parts + data + ARIA per part + keyboard per part + focus policy for overlays. Contract source: provider's `readonly props = $derived.by(...)` blocks, classified into the v.* value kinds — literal, stateRef, partRef, propRef, translationRef. Conditions extracted from ternary / guard patterns. Focus policies added on overlay components: popover, drawer, alert-dialog, dropdown-menu, context-menu, select, date-picker, date-range-picker, time-picker, time-range-picker, color-picker. Context-menu uses return:'previous' (no discrete trigger). Tooltip, link-preview, combobox, command omit focus (no trap). Tag-group Link variant: morfo-check tolerates sibling parts sharing a physical element (Link IS Item in the DOM) via allPartAttrs cross-scope. README.md added — developer guide: authoring a morfo step-by-step, the v.* builders, severity rules, validation layers, polymorphism handling via defaultElement + role, Sema alignment (data-last-action, transition markers). Verify: npm run check — 5 errs, all pre-existing in sium/examples. vitest run src/uix/morfo — 7/7 pass. morfo:check — 64/66 pass (2 flaky Playwright navigation timeouts, re-run clean when isolated). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	6 months ago
dev	8a5b402dd3	morfo: port 65 components + sium.lazy + morfo-check passes 66/66 ... All 65 soma components now consume their morfo as the cross-layer contract. createAttrs(morfo) and registerContract(morfo) overloads removed — the Morfo form is now mandatory. Each component provider has a 3-line morfo import + wire-up block instead of 20+ lines of inline declarations. Additions: sium/core/lazy.ts — lazy() combinator for recursive schemas (unblocks morfo's eventual lazy part-tree validation; tests included). sium/examples/ — booking, color, login, settings, signup, survey, tree form demos. Route demos at src/routes/test/sium/{booking,color,login,settings, signup,survey,tree}. Tooling: morfo-check.ts — now tolerates sibling parts sharing a physical element (Link variant of Item, etc.). Queries via allPartAttrs cross-scope. morfo-vocabulary-check.ts — 28 WARN (legitimate per-component vocabularies or subsets like switch missing "indeterminate"). All reviewed, none are bugs. Fixes caught by morfo-check: table: data-sorted / data-pinned marked severity:'optional' (only emitted when sorting/pinning active, not always). tree-grid: data-expanded on Row severity:'optional' (branches only). menubar: data-menubar-value declared on Trigger. splitter: data-splitter-panel-id declared on Panel. Verify: npm run check — 0 morfo errors (4 pre-existing in sium/examples, unrelated). npx vitest run src/uix/morfo — 7/7 tests pass. npm run smoke — 65/65 routes pass. npm run morfo:check — 66/66 morfos validate against real DOM. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	6 months ago