696 Commits (d18b32dd93e87a45abe2120a159e589dd5b94855)

Author	SHA1	Message	Date
dev	1805b0817d	feat(words): extension system skeleton (F2.1 + F2.2) ... Phase 1 of the words rich-text editor extension system. Skeleton + contract only — engine is NOT yet wired to consult the registry. That happens in F2.3 (migrate table) and F2.4 (migrate code-block). New module `src/uix/soma/components/words/extensions/`: - extension-types.ts: WordsExtension interface + sub-types. Every hook is optional. Hooks cover document semantics (nodeTypes, factories), normalization, commands (reducer pattern), rendering, serialization (HTML + Markdown, in + out), path navigation, keyboard, sema events, dispose. Each hook documented inline with rationale. - extension-registry.ts: createWordsExtensionRegistry() returns the runtime container. API: register / unregister / dispose extensions / findByNodeType / findByCommandName getRender / getNormalize / getCommand / getSerialize / getPath / getKeyboard allEvents / allCommandNames / allNodeTypes tryDeserializeHtml / tryDeserializeMarkdown Duplicate-name and duplicate-nodeType detection at register-time with rollback-safe semantics. dispose() tears down extensions in reverse-registration order. - extension-registry.test.ts: 14 tests covering register, conflict rejection (duplicate name, duplicate nodeType, duplicate command name), all-or-nothing rollback, sema event aggregation, dispose ordering, unregister, getRender/getNormalize/getCommand walks, tryDeserializeHtml walk-until-non-null. - index.ts: barrel. Verification: - 14/14 registry tests pass - 82/82 existing engine tests still pass (no engine touched) - Total 96/96 in src/uix/soma/components/words F2.1 (audit) + F2.2 (skeleton) done. F2.3 (migrate table) and F2.4 (migrate code-block) are separate sessions per the planned rollback-safe sub-task structure — each one will move the ~990 LoC of table and ~790 LoC of code-block from the engine core into extensions/{table,code-block}/* and wire them into the registry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	85b8a56ab0	feat(words): add toolbarLayout grouped|inline (responsive) ... New optional prop on <Words> for the toolbar layout strategy: - 'grouped' (default): each family (text/block/list/align/insert/table/ link/tools) becomes a single trigger button that opens a popover with its commands. Compact, recommended for narrow viewports. - 'inline': every command in every family renders flat in the toolbar, with the toolbar group separators marking family boundaries. High discoverability, recommended for wide editors. Tools that own their own panel UI (LinkEditor, FindReplace, HeadingPicker, CodeLanguagePicker) remain popovers/dropdowns in both layouts by design — they are not "inlineable". Accepts ResponsiveProp<WordsToolbarLayout> for breakpoint-aware switching, e.g. `toolbarLayout={{ base: 'grouped', md: 'inline' }}`. Implementation: - types.ts: new WordsToolbarLayout = 'grouped' | 'inline'; new toolbarLayout?: ResponsiveProp<WordsToolbarLayout> on WordsProps. - index.ts: export WordsToolbarLayout type. - words.svelte: resolved via eidos.resolve(toolbarLayout, 'grouped'). New helper flattenFamilyToLeafItems(family, customItems) returns the default leaf items per family for the inline expansion. Render refactored: leaf rendering extracted to a Svelte snippet reusable by both layouts, so the conditional only chooses between <ToolbarFamilyMenu> (grouped) and {#each leafs as leaf}{@render leafItem(leaf, snippetProps)}{/each} (inline). - demo: toolbarLayout state added + wired to <Words>. Verified visually in browser (preview + screenshot): - grouped: 9 family menu triggers + 1 sibling tool = 10 toolbar buttons - inline: 0 family triggers + 28 command buttons + 5 tools = 33 buttons Tests: 161/161 pass in src/uix/{contracts,soma/components/words}. TypeScript: 0 new errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	58c2c0babf	fix(words): close audit P0 + quiet focus event (FASE 1) ... Cierre de los hallazgos P0/P1 del audit Codex sobre Words + fix del evento contact-focus molesto reportado por el usuario. F1.1 — Fix evento foco (UX): El handler onfocus disparaba `runtime.trigger('contact-focus')` cada vez que el editor recibía foco, generando sound + haptic + visual stamp en cada re-focus desde popovers internos (bubble menu / link editor / find panel / slash menu / toolbar dropdowns). En sesión normal de edición el foco entra/sale del content docenas de veces, lo que producía fatiga perceptual. Cambios en words-provider.svelte.ts: - onfocus: emit solo en transición real (was-not-focused → focused). Re-focus desde popover interno NO emite. - onblur: si el related target es interno al Words tool tree (isInsideWordsTool), mantener focused=true (Words se trata como un solo scope de foco). Skip commit('blur') también para evitar commits espurios entre popover hops. F1.2 — Declarar 8 data-* hardcoded en morfo (audit P0-1): Añadidos al Content part: - data-words-find-match, data-words-find-active (mark highlights) - data-words-indent (list items con indent > 0) - data-language (alias parsing-only para interop con HTML externo emitido por Prism/highlight.js) Nuevas 6 parts compound (Eidos wrappers): - HeadingPicker + HeadingPickerPanel (data-words-heading-picker / -panel) - CodeLanguagePicker + CodeLanguagePanel - ToolbarFamilyMenu + ToolbarFamilyPanel F1.3 — Rename i18n keys a kebab-case (audit P0-1): 4 keys camelCase eran ilegales según contracts.test.ts. Renamed: - components.words.bubbleMenu → bubble-menu - components.words.slashMenu → slash-menu - components.words.linkEditor → link-editor - components.words.findReplace → find-replace Propagado a: morfo declarations (8 refs), provider tslangs calls (4 refs), catalog langs/components/words.ts (4 keys). F1.4 — Canonizar 9 event names a forma {family}-{verb}[-{variant}] (audit P2-1): Renombrados para parsear con el morfo:vocabulary script. El verb declarado en cada semantic ahora aparece explícito en el name: - commit-content → commit-save-content (verb: save) - commit-format → commit-set-format (verb: set) - commit-link → commit-set-link - commit-unlink → commit-reset-link (verb: reset) - commit-slash-command → commit-set-slash - commit-check → commit-set-check - commit-history → commit-restore-history (verb: restore) - commit-clear → commit-reset-content (verb: reset) - signal-invalid-input → signal-warn-invalid (verb: warn) Propagado a: sema cascade selectors, soma provider trigger calls, provider + content tests, demo route. 0 conflictos con event names de otros componentes (file-upload/tag-group/etc. usan namespaces propios sin colisión con words). Tests: 161/161 pass en src/uix/{contracts,soma/components/words}. Suite full eidos+morfo+soma+sema pendiente de verificar tras commit. contracts.test.ts ahora verde — cierra P0 audit Codex. morfo:vocabulary 0 event-name warnings (los 107 data-attr enum warnings son pre-existentes, separate scope). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	bd73fb98f3	feat(eidos): variants canon — EIDOS_VARIANTS + per-component lint ... Variants son canon del eidos, NO del theme. Decisión arquitectónica firmemente sostenida: el vocabulario de variants (solid/outline/ghost/ soft/surface/line/pills) está fijo a nivel del framework — paralelo a las 8 sema families del libro. Theme = retintar lo perceptualmente fijo; cambia QUÉ color es `affirm`, no QUÉ significa `outline`. Cambios: - lib/types.ts: nueva constante `EIDOS_VARIANTS` con los 5 archetypes canónicos (control / selection / chip / marker / tabs). Los 5 union types se derivan via `[number]` indexed access — valor y tipo no pueden desincronizarse. Nueva `EIDOS_VARIANT_VALUES` Set flat con todos los valores canónicos + utilidades cross-component (`plain`, `subtle`). - recipe-css-contract.test.ts: nuevo test "variant CSS selectors per component match the declared type union". Por cada componente: extrae el union type de `components/{c}/types.ts` (soporta literal unions + archetype aliases; cae a advisory mode en Extract<> y conditional types); compara con `[data-{c}][data-variant='X']` selectores en `{c}.css`; reporta typos y unauthorized extensions bidireccionalmente. - THEMING.md §19: nueva sección "Variants son canon del eidos, NO del theme" con argumentación (portabilidad, type safety, archetypes perceptuales paralelos a sema families), tabla de las 3 capas de la cebolla, referencia a `EIDOS_VARIANTS`, comparación con Radix Themes 3.x / Mantine 7 / Chakra v3 / Ark / shadcn. TOC actualizado. - eidos/README.md: tabla de referencia ampliada con §19. - CLAUDE.md: hand-off "2026-05-27 #6 (variants canon)". - CONTINUE.md: nota de la decisión arquitectónica. Variants component-specific permitidos (Banner inline/overlay/ persistent, Spinner bars/dots/ring, Button 'plain'): viven en cada `components/{c}/types.ts` y el lint los valida contra la CSS del componente. Tests: 101/101 pass en `src/uix/eidos`. `npm run check`: los mismos 6 errores pre-existentes (lib/_demo, soma/components/internal, web/ routes/active) — no relacionados. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d3f9be4ab0	fix(toggle): add missing per-color track/hover/border forwarders ... The toggle palette cascade (palette-track / palette-hover / palette-border declarations in TSC) referenced --toggle-{X}-track, --toggle-{X}-hover, --toggle-{X}-border for X in {primary, neutral, secondary, affirm, risk, threat} — but the recipe only declared 5 forwarders per color (element / solid / solid-hover / text / contrast). The 3 missing slots × 6 colors = 18 unresolved tokens made --toggle-palette-{track,hover,border} resolve to empty for any non-neutral color (the host default DID declare them). Visible effect, only when a non-neutral color was active: - ghost-on-bg = var(--toggle-palette-track) → empty → transparent fallback - ghost-on-border = color-mix(... palette-border ...) → invalid → property dropped, border falls through to base layer - outline-on-bg = color-mix(... palette-element ...) was the one that worked because palette-element forwarders DID exist for all 6 colors Surfaced today while verifying the TSC v2.2 toggle-group color cascade fix in the browser. The toggle-group composition correctly overrode --toggle-palette-* on items, but the empty track/hover/border slots collapsed ghost-state styling downstream. Verified with browser probe (preview_inspect): - ghost + affirm: paletteTrack #0d1514, paletteHover #023b37, paletteBorder #145750 (was "") - ghost + threat: paletteTrack #191111, paletteHover #500f1c, paletteBorder #72232d (was "") - outline + primary: paletteTrack #18111b, paletteHover #3d224e, paletteBorder #54346b (was "") Tests: 100/100 pass in src/uix/eidos. Recipe contract guard accepts the new forwarders (kebab-case, valid var() values). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	9c6375c96e	feat(eidos): TSC v2.2 (parts + composition) + universal theming coverage ... Token Scope Contract universal — no más excepciones arquitectónicas. Los 3 componentes que vivían fuera de TSC v2.1 (select, avatar, toggle-group) ahora están dentro del contrato via dos extensiones nuevas. TSC v2.2 extensiones (lib/config-types.ts + render-css.ts + config.ts): - `parts: readonly string[]` en RecipeTokenMultiDeclaration — emite selectores comma-separados (`[data-{c}-x], [data-{c}-y]`) para componentes con data-color cascadeado per-part. Consumer: select. - `composition: { foreignRecipe: { targetSelector, tokens } }` sibling key — overrides cross-recipe scoped a la cascade del host. Consumer: toggle-group modifica `--toggle-palette-*` en sus items. Migraciones: - select: 3 private `_accent-{track,border,text}` con parts: ['trigger', 'content'] + 7 cascades color:X each. Removed orphan `_accent-solid` (CSS no consumía). - avatar: 6 tokens via composite scopes `['variant:X', 'color:Y']` con matrix helper inline. Badge usa parts: ['badge']. Reemplaza 24 bloques CSS × 2 partes. - toggle-group: composition block con 8 palette tokens × 4 colors. Reemplaza 4 bloques CSS per-color. Bug toggle-group post-composition (encontrado y arreglado): Tras la composition migration, el cascade del toggle-group seguía roto porque los tokens derivados (`--toggle-solid-on-bg`, `--toggle-outline-fg`, etc.) viven en scope `[data-toggle]`. El `[data-toggle-group-item]` es sibling (no descendant), así que `var(--toggle-solid-on-bg)` resolvía undefined. Fix: inlined derivation expressions directamente en `[data-toggle-group-item]` y sus variant cascades (solid/outline/ghost), referenciando palette tokens en su propio scope local. Validador + emisor + contract: - `validateRecipeComposition` valida el shape `{ targetSelector, tokens }` y rechaza composition entries con scope='root'. - `stripCompositionKey` + `emitComposition` separan el pipeline. - `appendRecipeContractTokens` skip-list para `composition` (no aparece como fake `--{c}-composition` knob). - `tokenKeys`/`tokenEntries` helpers en recipe-css-contract.test.ts filtran composition en todos los iteradores. Documentación: - THEMING.md §18 reescrito como "Cobertura universal de TSC". §7 extendido con subsecciones "Multi-part scope" y "Cross-recipe composition" + ejemplos completos. TOC actualizado. - eidos/README.md tabla de referencia ampliada con TSC v2.2 + §18. - CLAUDE.md gana hand-off "2026-05-27 #5" (TSC v2.2 + cobertura universal). - CONTINUE.md reescrito al estado actual de la sesión. Working tree también incluye sprint Words en paralelo (multiple authors): slash menu, find/replace regex, code language picker, table audit, toolbar family menu, code highlight engine. Tests: 786/786 pass en src/uix/{eidos,morfo,soma,sema}. `npm run check`: 6 errores pre-existentes (lib/_demo, soma/components/internal, web/routes/active) no relacionados. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	28bf7f8b49	feat(pickers): wire runtime.trigger('close') in 5 picker providers ... After the 2026-05-27 picker family polymorphic refactor, the morfos declared the polymorphic `close` event but the providers were inert — they just toggled `opts.open = false` without firing the event. This commit cables them, mirroring the Dialog/Drawer/Popover dismissWith pattern (book §5.3). **Affected providers** (5): color-picker, date-picker, date-range-picker, time-picker, time-range-picker. **Pattern** (consistent across all 5): - Private `triggerClose(cause)` helper maps: 'committed' / 'range-committed' → commit.save + fulfill 'cancelled' → emerge.close 'dismissed' → emerge.dismiss 'dismissed-outside' → emerge.dismiss - Writes `data-last-action` on the morfo's target part (calendar / clock / content) imperatively before the trigger fires so eidos can tint the exit animation per cause. - Called from commit() / cancel() / handleSelect / handleDateSelect / handleRangeSelect — the close paths the provider already had. The morfo target varies per picker: - color-picker → content - date-picker → calendar - date-range-picker → calendar - time-picker → clock - time-range-picker → clock Internal state (`opts.open = false`) sequence preserved — the trigger fires BEFORE the open flip so the perceptual signal stamps `data-event-*` on a node that is still rendered. **dismissed / dismissed-outside causes** are declared but not yet wired to specific gestures — the picker shell delegates escape / outside-click handling to its wrapping Popover, whose own polymorphic close fires independently. The cause strings remain in the helper for future use (e.g. if a picker grows its own escape handling). **Result**: - Pickers now emit perceptual signal on commit/cancel via sema engine. - Eidos `[data-last-action='X']` selectors get exit-tint values to act on (mirror of Dialog/Drawer/Popover). - Picker tests: 18/18 still pass. `morfo:check`: 0 issues. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	312c8740ca	refactor(date-picker): rename kind 'date' to 'day' for trio consistency ... Audit caught `data-kind="date"` violation — the date-picker / date-range-picker morfos declare `data-kind ∈ [day, month, year]` but the public `kind` prop accepted `'date' | 'month' | 'year'` and defaulted to `'date'`. Rename prop value `'date' → 'day'` so the trio is consistent (all named after the grid cell granularity). **Rationale (book-pure)**: - The trio `day` / `month` / `year` is internally consistent — all three name the granularity of the grid cell the calendar view shows. - `'date'` was awkward in the trio: month and year pickers also pick "dates", just at coarser granularities. - The morfo enum was already canonical (`['day', 'month', 'year']`); this aligns the prop with the contract. **Surface touched** (all `'date' → 'day'` for the kind value): soma components: - date-picker / date-range-picker / date-field / date-range-field: provider type (DatePickerKind / DateRangePickerKind), default value, test fixtures, types.ts JSDoc. demos (web/routes/uix/components/): - date-picker / date-range-picker / date-range-field: kind state, selector chips, doc table. `'date'` literals that DON'T refer to kind (kept untouched): - ValueProfile = 'date' | 'datetime' | 'zoned' (different concept). - SegmentLock = 'none' | 'year' | 'monthYear' | 'date'. - CSS `input[type='date']` (HTML attribute). **Result**: - `npm run morfo:check`: 1 issue / 1 component → **0 issues**. All 107 routed morfos validate against their demo DOM ✓ - `npm run check`: 0 errors ✓ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	59c3bc96c4	fix(color-picker): emit data-state explicitly on Provider props ... Audit caught 'data-state not emitted' on the ColorPicker Provider. The morfo declares `data-state ∈ [open, closed]` with `value: v.stateRef('open')` — the runtime's `syncAttrs` can sync this from `dom.apply`, but only if the provider receives a `ref` on its opts (which the ColorPickerProvider doesn't — `ColorPickerOpts` extends `ProviderOpts` + `StateProps` without the ref slot). Rather than re-shape the opts to add ref + bind it in the wrapper, just emit `data-state` explicitly in the provider's props derivation, same form as the other six declarative attrs that the provider already materialises (`data-format`, `data-invalid`, `data-disabled`, `data-readonly`, `data-required`, `aria-invalid`). Matches the dialog/drawer/popover doctrinal pattern for disclosure attrs. After this commit `morfo:check`: 1 issue remaining (date-picker `data-kind="date"` — separate domain issue, addressed next). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9f1466dc57	fix(avatar): data-color severity optional to acknowledge custom-color escape hatch ... Audit caught 4 'missing data-color' violations on the Avatar Provider — the demo includes consumers passing non-canonical CSS color strings (`#7c3aed`, `oklch(70% 0.15 220)`, `rgb(245 158 11)`) which the wrapper correctly routes through `data-color-custom=""` + an inline `--avatar-color-custom` CSS variable instead of the enum attr. The morfo enum can't represent arbitrary CSS color strings, so the `data-color` attr is legitimately absent in those cases. The contract should reflect that: severity becomes `optional`. Symmetric with the `Avatar.Badge` part which already declared this attr as optional. Behaviour unchanged. Only the morfo's severity flag changes. After this fix `morfo:check`: 6 issues / 3 components → 2 issues / 2 components. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	3542f3a730	fix(button): remove redundant data-state enum (book §1 purity) ... Audit 2026-05-27 caught 11 `data-state="idle"` violations across 3 disclosure trigger components (dropdown-menu, table.row-detail-trigger, tree-grid.expand-trigger). Root cause was composition: each used `<Button>` as its chrome via `{...props}` spread, and Button's morfo declared a redundant `data-state ∈ [idle, loading]` enum that the runtime emitted unconditionally — clobbering the outer trigger's `data-state="open|closed"` via mergeProps order. Doctrinal fix: REMOVE `data-state` from Button's morfo entirely. Button's loading state is already fully expressed by the `data-loading` presence flag (declared further down in the same morfo and consumed by eidos as `[data-loading]`, not `[data-state='loading']`). The 'idle' value was a redundant synonym for "not loading" — and the book canon favours "presence = active state, absence = rest" for binary states (cf. `data-disabled`, `data-loading`). **Book-pure rationale**: - Disclosure (family `emerge`): `data-state ∈ [open, closed]` — dialog, drawer, popover, accordion, dropdown-menu, etc. - Lifecycle (family `sustain`): `data-state ∈ [idle, loading, ...]` — image, avatar, button (until now), card, field. - Mixing the two vocabularies in a single attr is the incoherence this fix removes. - Button is interactive surface, NOT lifecycle: its "rest" is natural absence of `data-loading`, not a distinct `idle` state. **Result**: - `npm run morfo:check`: 16 issues / 6 components → **6 issues / 3 components**. Removed all 11 `'idle'` violations. - Composition pattern restored: `<Button>` no longer clobbers `data-state` on the host trigger. - Eidos CSS unchanged (already uses `[data-loading]`). - Tests: 803/801 unchanged (2 remaining failures are unrelated, in the user's words editor WIP). **Not fixed in this commit** (3 remaining `morfo:check` failures): - `avatar.provider`: missing `data-color` emission (4×) - `color-picker.provider`: missing `data-state` emission - `date-picker.provider`: `data-kind="date"` not in declared `[day, month, year]` enum. Each requires a separate domain decision. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	681e056102	fix(uix-audit): close 4 pre-existing issues found in system audit ... System-wide audit of `src/uix/*` + `src/arts/adom` (excluding demos and web/routes). Findings + fixes documented in `src/uix/AUDIT_REPORT_2026-05-27.md`. **Fixed**: 1. `src/uix/eidos/lint.test.ts`: "every eidos CSS component has a morfo file" test extended to walk `morfo/internal/` as well as `morfo/components/`. The picker-shell relocation (audit-codex P1 #5) moved picker-shell to internal but the test wasn't updated. 2. `src/uix/contracts.test.ts`: two pre-existing failures resolved. (a) Picker WithChild regex updated to accept the `WithChild<Omit<PrimitiveDivAttributes, ...> & {...}>` shape applied in the audit-codex P0/P1 picker ProviderProps refactor. (b) `collectPublicSomaComponentDirs` now skips `picker-shell` as an internal primitive (symmetric to `collectKnownMorfoDataAttrs` which now walks `morfo/internal/` to include the picker-shell data-attrs). 3. `src/uix/soma/components/command/command-provider.svelte.ts`: restored missing `createAttrs(commandMorfo)` import. Was the only ERROR in `npm run check` baseline. 4. `src/uix/soma/components/dialog/types.ts`: JSDoc comment updated to reflect polymorphic close shape (cosmetic alignment with the 2026-05-27 refactor). **Result**: - `npm run check`: 1 ERROR → **0 ERRORS** ✓ - `npx vitest run src/uix`: 5 failed → **2 failed** (both 100% in user's words/* WIP, not framework code) - Polymorphic close + persistence + a11ySemantic rollout: **zero drift detected** across morfos / providers / sema cascades / tests. **NOT actioned** (documented in report): - 6 pre-existing `morfo:check` failures (avatar / color-picker / date-picker / dropdown-menu / table / tree-grid). All require domain decisions (drop 'idle' state vs add it to morfo enum, etc.). - 1 navigation-menu data-state='visible' eidos selector drift. - ~14 README/`.md` files with stale Dialog/Drawer/Popover descriptions. - Words editor doctrinal cleanup (user's WIP). - Tooltip polymorphic alignment (optional, no consumer benefit today). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	34e0064f2c	feat(toast): explicit persistence: 'transient' on signal-announce event ... Documents the deliberate choice to keep the announce event's perceptual projection transient even though the canonical book §6.2 table would suggest `untilFix` for `signal + risk` or `untilAction` for `signal + threat`. Rationale: the Toast component owns its own lifecycle via `Toast.Provider`'s auto-dismiss timer + user dismiss. The `data-event-*` projection is a one-shot pulse when the toast enters. Persistence of the toast surface itself lives in `data-state` (open/closed) on the Item, not in the signal projection. Found via audit of all `verb: 'warn' | 'alert' | 'notify'` events across `src/uix/morfo/components/*`. Toast was the only one without an explicit persistence declaration — annotated now so the choice is intentional rather than implicit-default. (`words.signal-invalid-input` also lacks persistence but it belongs to the in-flight words editor work tracked separately by the user.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9ca8b4e30b	docs(claude/libro): document persistence + a11ySemantic + polymorphic close rollout ... LIBRO_VARIACIONES_Y_EXTENSIONES.md: - New section D.9 (persistence + holds-by-intent — book §6.1). - New section D.10 (a11ySemantic per event — book §9.1). - New section D.11 (polymorphic events — book §5.3) with the full rollout state across overlays + picker family. CLAUDE.md hand-offs: - 2026-05-27: initial sprint (persistence + a11ySemantic + polymorphic types). - 2026-05-27 #2: caller messages + persistence extension + Dialog refactor. - 2026-05-27 #3: Drawer + Popover polymorphic refactor. - 2026-05-27 #4: Picker family polymorphic refactor + test fixtures decoupling. Each hand-off records: scope, files touched, doctrinal decisions, and pending follow-ups. The whole rollout was verified on 680/680 tests across sema + morfo + soma + adom scopes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8dce794ab4	refactor(pickers): collapse close-* into polymorphic close on 5 picker morfos ... Mirror of the dialog/drawer/popover refactor (book §5.3) applied to the picker family: - color-picker - date-picker - date-range-picker (incl. close-range-commit cause) - time-picker - time-range-picker Each had 4 close-* events with per-event prewrite; collapsed to a single polymorphic `close` event: semantic: { family: 'emerge', verb: 'close', target: v.partRef('calendar'|'clock'|'content'), sequence: 'pre', persistence: 'transient', allowedFamilies: ['emerge', 'commit', 'signal'] } **Behaviour preserved**: the picker providers don't currently fire any `runtime.trigger('close*')` — they just toggle `opts.open = false` and let the popover unmount. The previous `close-*` events were declared but inert (only consumed by schema validator + compiler tests). Refactor is doctrinal alignment, not behavioural change. **Sema cascade**: only color-picker has a sema pack and it did not reference any close-* event (only handle-pick / handle-drag / commit-set). Zero cascade updates needed. **Test fixtures**: compile.test.ts + runtime.svelte.test.ts already migrated to the synthetic `prewriteFixtureMorfo` in the core commit, so this refactor doesn't break them. After this commit the only morfo with the pre-polymorphic per-event prewrite shape is the synthetic test fixture itself — every production morfo is on the polymorphic close. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9f5fbfdb71	refactor(dialog/drawer/popover): collapse close-* into polymorphic close (book §5.3) ... Three overlay components each had five `close-*` events (close-save / close-cancel / close-dismiss / close-dismiss-outside / close-after-fail) with per-event prewrite arrays setting `data-last-action`. Per the book §5.3 polymorphism canon, collapse to a single `close` event: semantic: { family: 'emerge', verb: 'close', target: ..., sequence: 'pre', persistence: 'transient', allowedFamilies: ['emerge', 'commit', 'signal'] } NO prewrite — the provider sets data-last-action imperatively before trigger because polymorphic events can't bind a single prewrite per call. **Provider pattern** (Dialog / Drawer / Popover): - New `DISMISS_CAUSES` map: { save, cancel, dismiss, dismiss-outside, fail } → { lastAction, semantic: { family, verb, intent? } }. - `dismissWith(action, opts?)` does `dom.apply({ 'data-last-action': cause.lastAction })` then `runtime.trigger('close', { fallbackTarget, semantic: cause.semantic, message })`. - `triggerClose` is now private; previously-public 2-arg signature collapsed into the cause-driven internal helper. - All internal callsites (escape, outside-click, hover-close, close button) migrated to `dismissWith`. - `opts.message` forwarded to runtime — when `a11ySemantic.requiresLiveRegion` is set (today only for the 'fail' case), the live region announces it. **Schema validator relaxed** (`src/uix/morfo/schema.ts`): the "every declared value of `data-last-action.values[]` must be prewritten by some event" check was DROPPED — provider-imperative writes can't satisfy it. The reverse direction (`prewritten ⊆ declared`) stays strict. **Cascade rewrite** (`src/uix/sema/components/{dialog,drawer,popover}.ts`): - `eventNamePrefix: 'close-'` → `eventName: 'close', eventFamily: 'emerge'` - `eventName: 'close-dismiss-outside'` → `eventName: 'close', state: { attr: 'data-last-action', value: 'dismissed-outside' }` **Eidos CSS**: not touched — already reads `data-last-action` directly. **Public API preserved**: `dismissWith` signature + observable behaviour identical. External consumers see no difference. Tests updated for the new event name. 680/680 pass across sema + morfo + soma + adom scopes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	c34fd1fd31	feat(uix-components): apply persistence + a11ySemantic + live-region messages to 6 morfos ... Per the canonical book §6.2 + §9.2 mapping, six morfos with `signal.warn`, `signal.alert` or `signal.notify` events get explicit `persistence` + `a11ySemantic` annotations, and their providers wire up `clearTarget` + caller-message integration with the shared live region. **Morfo annotations**: | Morfo / event | persistence | a11ySemantic | |--------------------------------------------|----------------|---------------------------------------------------------| | announce.signal-alert | untilAction | requiresPersistentTrace + requiresLiveRegion | | form.signal-warn-invalid | untilFix | requiresPersistentTrace + requiresFocusMove + reducedMotionFallback='text' | | file-upload.signal-warn-reject | untilFix | requiresPersistentTrace + reducedMotionFallback='text' | | password-field.signal-notify-caps-state | stateBound | requiresLiveRegion + reducedMotionFallback='text' | | tags-input.signal-warn-reject | untilFix | requiresPersistentTrace + reducedMotionFallback='text' | | textarea.signal-warn-count-overflow | untilFix | requiresPersistentTrace + reducedMotionFallback='text' | **Provider wiring**: - form-provider: clearTarget on submit, message="{N} form errors..." via FORM_LANGS.ERROR_SUMMARY_*. - file-upload-provider: clearTarget before each accept/reject cycle, message via new FILE_UPLOAD_LANGS.REJECT_SUMMARY_{SINGLE,MULTI}. - password-field-provider: clearTarget on caps-off transition, message via existing PASSWORD_FIELD_LANGS.CAPS_WARNING. - tags-input-provider: helper `emitWarnReject` (clear + emit + message via new TAGS_INPUT_LANGS.REJECT_WARNING), called from addTagValue, addFromInput, handlePaste. Successful add also clears (the add is the fix). - textarea-provider: emits only on transition INTO overflow, clears in transition OUT (untilFix projection persists). Message via new TEXTAREA_LANGS.OVERFLOW_WARNING with {{max}}. Three new lang catalog entries (reject/overflow warnings) merged into the existing components.{name}.* namespaces. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	70f6f3bf0d	feat(uix): persistence + a11ySemantic + polymorphic core (book §5.3, §6, §9) ... Three book canon items codified in code: **Persistence (libro §6.1)** — separa `hold` (perceptual min) de `persistence` (lifecycle real): - New `SignalPersistence = 'transient' | 'untilAction' | 'untilFix' | 'stateBound'` - New `SEMA_HOLDS_BY_INTENT` canonical lookup table (`src/uix/sema/holds.ts`) - `EngineSemantic.emit()` returns the resolved signal id; keeps projection alive past hold for non-transient. Exposes `clear(id)`, `clearTarget(target)`, `hasActive(id)`. - `SomaRuntime.trigger()` returns `TriggerResult { id?, persistence? }`. Exposes `clearSignal(id)`, `clearTarget(target)`, `partRef(part)`. **a11ySemantic (libro §9.1)**: - New `MorfoA11ySemantic` (requiresPersistentTrace, requiresLiveRegion, requiresFocusMove, keyboardEquivalent, reducedMotionFallback) on MorfoEvent. - `ActiveDom.prefersReducedMotion`: reactive tracker via media query (`src/arts/adom/reduced-motion.svelte.ts`). - `ActiveUix.announce(msg, priority?, timeout?)`: lazy-created live region via `dom.writeNode`. - `Soma.runtime()` auto-wires `sources.announce`. - `SomaRuntime.trigger()` honors a11ySemantic after emit (live region, focus, reduced-motion fallback including `channels: []` for 'state'). **Polymorphic events (libro §5.3)** — ADITIVO sobre shape concreto: - `allowedFamilies?: readonly SemaFamily[]` opcional en MorfoEventSemantic. - Provider override via `runtime.trigger(name, { semantic })`. - Default family of the morfo is implicitly allowed. - New `SomaRuntimePolymorphicError`. - New `isPolymorphicSemantic` type guard. Synthetic `prewriteFixtureMorfo` (src/uix/morfo/test-fixtures.ts) decouples compile + runtime tests from the production morfo catalogue. 671 tests pass in sema + morfo + soma + adom scopes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	e6eee766ee	Improve words editor tooling	5 months ago
dev	7afa7057d4	docs(soma): add Sema events section to 23 component READMEs ... Documenta los cambios doctrinales del sprint Lectura C + cabling soma. Cada README añade una sección `## Sema events` con tabla (event / family / verb / target / intent / when) + referencia al pack si existe + notas doctrinales de las correcciones aplicadas. Componentes: - Packs creados este sprint (11): switch, toggle, toggle-group, menubar, navigation-menu, dropdown-menu, context-menu, tree-view, tree-grid, tooltip, collapsible. - Componentes con emisión cableada sin pack (8): listbox, grid-list, table, feed, command, carousel, announce, clipboard. - Componentes gestuales con notas sobre handle-scroll no-emitido (3): drag-drop, virtual-list, virtual-grid. - Checkbox: documenta la doctrina de dos eventos direccionales (commit-toggle-check/uncheck con intent affirm/neutral). Correcciones doctrinales documentadas: - announce: commit-announce-* → signal.announce / signal.alert - tree-view: target item → branch para emerge-expand/collapse - table: shift.sort → commit.set; shift.expand-row → emerge.expand - drag-drop: commit.drag-start/drop → handle.pick/drop - clipboard: commit.copy → commit.save; commit.copy-error + threat → commit.fail + risk - virtual-list/grid: handle-scroll declarado pero NO emitido (decisión consciente — buzz nonstop con family.handle haptic-only). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	cbf76b66c8	feat(soma): wire runtime.trigger for batch C (gestural + wrappers) ... Cierra el sprint de cabling. De los 6 originales del batch C, 3 son wrappers sin events propios (time-range-field, link-preview, alert-dialog) que delegan en su componente compuesto — zero wiring necesario. Los 3 restantes: - drag-drop: - startDrag(...) → handle-pick en draggable con params.source como fallbackTarget. - commitDrop(target) → handle-drop en droppable con target. - cancelDrag() → commit-cancel en draggable con drag.source. - virtual-list: - scrollToIndex(...) → shift-navigate-to-index en viewport (programmatic discrete-navigation moment). - observeResize callback → commit-set-resize en provider cuando el clientWidth/Height realmente cambia (skip initial). - NO emite handle-scroll: family.handle es haptic-only, el scroll listener fires en cada píxel — emitiría buzz nonstop. Documentado como decisión consciente; apps con scroll-feedback wiran su propio throttle. - virtual-grid: análogo virtual-list, con scrollToCell → shift-navigate-to-cell. NO emite handle-scroll-row / handle-scroll-column por la misma razón. Verificación: - npm run morfo:vocabulary → EXIT 0 - npx vitest run src/uix/sema src/uix/morfo → 195/195 pass - npx vitest run src/uix/soma → 419/419 pass Tras este commit: TODOS los morfos con scope:sema + events declarados emiten desde soma (excepto los 4 `handle-scroll*` de virtual-list/grid intencionalmente saltados). Cierra el caveat "soma no emite" del proyecto memory. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	0784cae578	feat(soma): wire runtime.trigger for batch B (8 components) ... Continúa batch A. Estos 8 componentes tienen scope:sema y events declarados pero no usan pack propio — emiten sobre family base. - listbox: select() central → commit-select / commit-unselect en item. - grid-list: select() central → idem en row. - table: - SortTrigger.onclick/onkeydown → commit-set-sort en column-header. - Row.onclick/onkeydown → commit-select en row. - RowDetailTrigger → emerge-expand-row en row (solo transición closed → open; el morfo no declara collapse counterpart). - feed: - focusAt() (centraliza navegación de teclado) → shift-navigate-focus-item en article. - PageDown-en-final + Sentinel.onIntersect → commit-submit-load-more en provider. - command: - Item.onclick → commit-submit-invoke en item (path mouse). - selectCurrent() (Enter key) → commit-submit-invoke vía lookup por data-value en provider ref. - carousel: commit() central (next/prev/goto/autoplay) → shift-navigate-slide en item, lookup por data-index. - announce: announce() → signal-alert (assertive) o signal-announce (polite). clear() → commit-reset. - clipboard: copy() acepta optional triggerEl → commit-save-copy (success) / commit-fail-copy (catch). Trigger.onclick pasa e.currentTarget. Verificación: - npm run morfo:vocabulary → EXIT 0 - npx vitest run src/uix/sema src/uix/morfo → 195/195 pass - npx vitest run src/uix/soma → 419/419 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	adf89a0811	feat(soma): wire runtime.trigger for batch A (7 components) ... Los 11 packs sema shipped en commit 2d562f37 quedaban dormantes porque soma no llamaba runtime.trigger en ningún sitio de estos 7 componentes. Esta es la cabling que los activa. Patrón: emisión en el state-mutator central (no en handlers individuales) cuando es posible, pasando fallbackTarget al elemento DOM apropiado para que el cascade selector matchee la instancia correcta (no la "más reciente registrada"). - toggle-group: `commit-toggle` desde Item.onclick con item button como fallbackTarget. - menubar: `commit-select` desde Provider.open(value), usando triggerRegistry para resolver value→element. Cubre click, keyboard, hover-follow y arrow-nav en una sola emisión. - navigation-menu: `commit-select` desde Provider.openNow(value), usando triggerRefs existente. Closest() del trigger sube al item ancestro. - dropdown-menu: `open` y `close` desde handleOpen/handleClose (sequence: 'pre' — antes de la mutación de state); `commit-select` desde MenuItemProvider.onclick + onkeydown. - context-menu: `open` desde openAt(), `close` desde handleClose, `commit-select` desde ContextMenuItemProvider.onclick + onkeydown. - tree-view: `emerge-expand`/`emerge-collapse` desde toggleExpand (lookup branch via querySelector). `commit-select` desde select() con parámetro fromEl pasado por BranchControl/ItemProvider. - tree-grid: análogos via lookup de row por data-value. Pack tree-view actualizado: añade cascade rule para commit-select sobre `branch` (mismo tuning que item) — branches y leaves comparten firma perceptual. Fix colateral: tag-group test esperaba intent='neutral' para commit-unselect, pero el canon (f3641347) lo declara como 'affirm'. Test actualizado. Verificación: - npm run morfo:vocabulary → EXIT 0 - npx vitest run src/uix/sema src/uix/morfo → 195/195 pass - npx vitest run src/uix/soma → 419/419 pass (74 files) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	66318c4759	fix(tree-view): target branches for emerge-expand/collapse ... Morfo declaraba target='item' para emerge-expand y emerge-collapse, pero los items son hojas — no se expanden. El stamp del data-event-* debe aterrizar en el branch (data-tree-view-branch), que es el part que realmente revela/oculta contenido. - Morfo: target: v.partRef('item') → v.partRef('branch') en ambos events de emerge. commit-select sigue en item (selección aplica tanto a leaves como a branches). - Pack: selector `onItem(emerge-*)` → `onBranch(emerge-*)`. Las dos cascadas de emerge ahora matchean el elemento correcto en DOM. tree-grid no afectado: su Row es a la vez item y branch (data-has- children + data-expanded en el mismo part), así que target='row' ya estaba correcto. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	43b1537291	refactor(picker-shell): close as INTERNAL primitive (audit P1 #5) ... picker-shell quedó suelto en el audit-codex: existía un morfo placeholder en src/uix/morfo/components/picker-shell.ts sin imports, sin events, sin texts, y los 5 composite pickers (date / date-range / time / time-range / color) consumían eidos parts via re-export bajo SU namespace (<DatePicker.Footer>, etc.) — apps nunca escribían <PickerShell> directo. Cierre como INTERNAL primitive per la propia recomendación del audit: - Movido src/uix/morfo/components/picker-shell.ts → src/uix/morfo/internal/picker-shell.ts. El audit walk de morfo/components/ ya no lo encuentra. Cero imports rotos (no había ninguno). - README en src/uix/eidos/components/picker-shell/README.md declara el status INTERNAL + diagrama de composición de los 5 pickers. - Docstring del morfo actualizado con STATUS: INTERNAL explícito. - audit-codex-full-1.md sección 5 marcada RESUELTO con verbatim del cierre. Verificación: - npm run morfo:vocabulary → EXIT 0 - npx vitest src/uix/sema src/uix/morfo → 195/195 pass - npm run component:audit → picker-shell ya no aparece (no era public component, no debe figurar en lista de NEEDS-WORK) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	826ca2bf46	docs(sema): add D.8 — channels: qué es canal y qué no ... Doctrina arquitectural sobre límites de los canales runtime: - Canales built-in del framework: sound + haptic (los únicos). - ARIA estructural: declarativo en morfo, NO canal. - ARIA dinámico (live regions): soma escribe directo, NO canal. - Visual (motion / color / presence): eidos CSS via data-event-*, NO canal. - Regla operativa: algo es canal sólo si recibe SemanticSignal, acepta modulación por intent.deltas, y tiene signature paramétrica análoga a sound/haptic. ARIA dinámico falla la modulación. - Channels extensibles: declaration merging del registry; opt-in por app (voice, a11y formal, etc.). Framework no envía ninguno. Cierra una tentación que surgió en D.7 — convertir ARIA en canal era confusión categorial. Esta sección fija los límites para que nadie reincida. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 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	b0869878d8	docs(audit): mark P1 #4 (non-canonical event verbs) as RESUELTO ... Updated section 4 of audit-codex-full-1.md to reflect the closure of P1 #4 in the sema canon sprint (commits af6d6c76 → 00f0b740). All four hallazgos in the original audit fixed: - button.commit-action → contact-activate - textarea.shift-count-overflow → signal-warn-count-overflow + risk - month/year-grid nav-step → shift-navigate-step - password-field shift.toggle → commit.toggle Plus 56 additional events from Capa 2 + Capa 3 (family misclassifications, cluster clear → commit.reset, cluster unselect with commit.unselect added to canon, 12 individual renames + 1 doctrinal correction). morfo:vocabulary now hard-fails on declared verb drift; soft-warns on name shape. 7 warns remaining are all words.* (separate dev track). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	00f0b740e6	refactor(sema/docs): apply author's evaluation — status classification + intentRequirement/intentGuidance split ... Two changes in one commit: 1. **Doctrina del autor sobre el documento de variaciones** The author evaluated LIBRO_VARIACIONES_Y_EXTENSIONES.md and gave per- entry verdicts. The doc is now rebranded, restructured, and classified: - Renamed: "Registro de desviaciones entre implementación y canon editorial". Disclaimer at top: not the book, internal registry only. - Formal status classification (BOOK_CANON / PROJECT_CANON / CANDIDATE / LOCAL_EXTENSION / DEPRECATED / ALIAS / IMPLEMENTATION_CONTRACT). - Per-entry verdicts assigned per author's evaluation. Author's doctrinal texts included verbatim where given. - A.6 split per verb (was a single bullet for apply/partial/block/ move/upload; now each has its own status: apply=BOOK_CANON, move=BOOK_CANON, upload/partial/block=CANDIDATE). - A.6/A.7 ordering fixed (commit.unselect now A.11 — terminal). - C.3 split into C.3.a (renames mecánicos) y C.3.b (correcciones doctrinales — command intent shift). - E (resumen ejecutivo) actualizado: clear/unselect movidos a resueltos (estaban contradiciéndose). Pendientes reales listados. - F + new section G ("Anti-mezclas") con disciplina sobre el doc. 2. **Family policy: split `intentPolicy` en `intentRequirement` + `intentGuidance`** (D.3 del doc). La policy actual `'allowed' | 'expected' | 'optional'` mezclaba dos ejes que el autor pidió separar: - `intentRequirement: 'required' | 'optional' | 'forbidden'` — compile-time type constraint. - `intentGuidance: 'expected' | 'contextual' | 'discouraged'` — guía doctrinal sin efecto en tipos. Policy nueva: | family | requirement | guidance | |----------|-------------|--------------| | contact | optional | discouraged | (Cap 22 §11) | commit | required | expected | | signal | required | expected | | handle | optional | contextual | | emerge | optional | contextual | | shift | optional | contextual | | sustain | optional | contextual | | delegate | optional | contextual | (Cap 29 §4) `IntentExpectedFamily` deprecated → `IntentRequiredFamily` (alias mantenido). `IntentPolicy` type también deprecated. Consumers actualizados: event.ts (isSemaEvent usa requirement), validation.ts (validateSemaEvent usa requirement), event.test.ts (tests usan ambos campos), dialog.ts (comment doc update). 3. **Bug menor encontrado en `SEMA_TRANSITIONAL_FAMILIES`**: faltaba `delegate`. Añadido. (Era inconsistente con SemaTransitionalFamily type que sí lo incluye.) Verification: - vitest src/uix/sema src/uix/morfo: 195/195 pass - morfo:vocabulary: 7 warns (todos words/*, separate dev track) - EXIT 0 Pendiente futuro (no en este commit): - Añadir flag `emission` a MorfoEvent type per D.2 (eventos declarados pero no emitidos) - Re-evaluar verbos CANDIDATE (acknowledge/confirm/upload/partial/ block) cuando aparezcan más casos de uso Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	bbfefdb63d	refactor(morfo): rename 12 events to {family}-{verb}-{variant} canonical shape (Capa 3 cluster otros) ... Closes the last cluster of name-shape drift in the non-words morfos. 11 are pure cosmetic renames (declared verb already canonical); 1 includes a doctrinal correction. Renames (verbo declarado canónico, solo el name): - carousel.shift-slide → shift-navigate-slide - feed.shift-focus-item → shift-navigate-focus-item - feed.commit-load-more → commit-submit-load-more - file-upload.commit-add → commit-set-add - file-upload.signal-reject → signal-warn-reject - form.signal-invalid → signal-warn-invalid - number-field.handle-scrub → handle-drag-scrub - range-calendar.commit-start → commit-select-start - range-calendar.commit-range → commit-select-range - tags-input.commit-add → commit-set-add - tags-input.signal-reject → signal-warn-reject Doctrinal correction: - command.commit-invoke (declared submit + fulfill) → commit-submit-invoke + submit + AFFIRM (not fulfill) Per book cap. 22 §8 ("Error típico: contact.press + fulfill — esto hace que el sistema diga 'ya terminó' cuando solo ha empezado. Contact inicia. Commit resuelve."), the user submitting a command in the palette does NOT mean the command has completed. Same precedent as Button: celebrate-before-time is wrong. Affirm acknowledges the submission; the command's actual completion (success/failure) fires downstream from whichever morfo owns it. Consumers updated: - sema/components/{file-upload,form,number-field,tags-input}.ts - soma/components/{file-upload,form,number-field,range-calendar,tags-input}/*.ts - sema/resolver.test.ts (event name + data-event selector) Verification: - morfo:vocabulary: warns 19 → 7 (-12), the 7 remaining are all words.* (separate dev track, excluded). EXIT 0. - vitest src/uix/sema src/uix/morfo: 195/195 pass Doc src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md C.3 marked RESUELTO with full list of renames + the command intent correction. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f3641347de	feat(sema/morfo): add commit.unselect to canon + apply to 6 morfos ... User doctrinal decision (2026-05-25): add `unselect` as canonical verb of the commit family. The pair `select` / `unselect` covers results applied on the selection state of an item — distinct from `toggle` (binary control flip) and `remove` (retirement from a collection). Quoting the author: "Seleccionar y deseleccionar son resultados aplicados sobre el estado de selección de un elemento. Eso es commit, porque el resultado queda aplicado. - No es remove: no estás eliminando el item ni sacándolo de una colección funcional; solo estás cambiando su estado de selección. - No es necesariamente toggle: toggle describe mejor el mecanismo binario o el control, pero no expresa tan bien el resultado semántico concreto." Changes: - src/uix/sema/verbs.ts: add `unselect` to SEMA_VERBS.commit after `select` (natural pair). Header comment documents the doctrinal distinction with toggle and remove. - 6 morfos updated: calendar, combobox, grid-list, listbox, select, tag-group. Each changes `commit-unselect` from `verb: 'remove' + intent: 'neutral'` to `verb: 'unselect' + intent: 'affirm'`. Names preserved (already canonical now). Intent `affirm` because "the action applied correctly" (sobrio, not celebratory). - src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md: C.2 marked RESUELTO with the full doctrinal reasoning verbatim. A.3 (remove vs delete) updated to reflect the three-way distinction now formalized (unselect/remove/delete). New A.7 entry for `unselect` itself with "para el libro" note (add to Cap 23 §5). Verification: - morfo:vocabulary: warns 25 → 19 (-6 unselect cluster), EXIT 0 - vitest src/uix/sema src/uix/morfo: 195/195 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	1582572e9b	refactor(morfo): commit-clear → commit-reset across 10 components (cluster clear resolved) ... User directive: clearing a field is `commit.reset` per book cap. 23 ("vuelve a estado inicial") — fits all 10 components in the cluster since each goes back to empty-initial-state, not discarding meaningful defaults. Components updated (morfo + soma trigger + sema cascade + test): - color-picker, date-field, date-picker, date-range-picker - file-upload, range-calendar, tag-group, tags-input - time-picker, time-range-picker range-calendar.commit-clear was declaring `verb: 'remove'` — corrected to `'reset'` along with the name change. All event names now: `commit-reset` (family commit, verb reset, intent neutral). No variant suffix needed; no ambiguity of multiple resets in any single component. words.commit-clear excluded — separate dev track. Doc updated: src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md C.1 marked as RESUELTO with author's disposition. Verification: - morfo:vocabulary: warns 35 → 25 (-10), EXIT 0 - vitest src/uix/sema src/uix/morfo + tag-group tests: 199/199 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	670c54177d	docs: document deviations from the book canon (LIBRO_VARIACIONES_Y_EXTENSIONES.md) ... Inventory of every place the UIX project canon diverges from, extends, or interprets «Diseñando lo que ocurre» beyond its literal lists. For each entry: book reference, decision taken, argument, and a pending question for the author to evaluate. Six categories: - A. Verbs added to canon beyond book's literal lists (handle.scroll, commit.acknowledge, commit.remove, commit.confirm, commit.set, commit.apply/partial/block/move/upload) - B. Interpretive adoptions not literally in the book (drag cancellation, programmatic scroll, data resize, sort, auto-revert states, toggle phases, contact intent as visual-only) - C. Open doctrinal questions (clear, unselect, ~19 individual events) - D. Architectural decisions relevant to the book (composition over overload, declared-but-not-emitted events, family policy nuance) - E. Executive summary - F. Disposition options for the author (accept, reject, reformulate, keep as local extension) Author can use this to decide what passes to the book vs what stays as project extension. Until disposition, this doc is source of truth for deviations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	103c49a7ab	refactor(morfo): align 22 events with book family doctrine (Capa 2) ... Resolves family-level misclassifications across 9 morfos. Each cluster maps a doctrinally wrong family to the book's literal prescription: CLUSTER 4 — announce (cap. 24 §5): - commit-announce-polite (commit.submit) → signal-announce (signal.announce + neutral) - commit-announce-assertive (commit.submit) → signal-alert (signal.alert + threat) Announcing is the canonical signal verb. Was misclassified as commit. CLUSTER 5 — checkbox (cap. 22 §10, option B per user): - commit-check (commit.select) → commit-toggle-check (commit.toggle + affirm) - commit-uncheck (commit.remove) → commit-toggle-uncheck (commit.toggle + neutral) Book literal: "Toggle: contact.press → commit.toggle + affirm". Two events retained (option B) so check/uncheck carry different intents; same canonical verb `toggle` per book. CLUSTER 1 — tree-view + tree-grid (cap. 26): - shift-expand (shift.navigate) → emerge-expand (emerge.expand) - shift-collapse (shift.navigate) → emerge-collapse (emerge.collapse) Book literal: "emerge.expand — una región crece y revela contenido". Tree node expansion reveals content; it's not a context shift. CLUSTER 3 — drag-drop (cap. 25 §4): - commit-drag-start (commit.submit) → handle-pick (handle.pick) - commit-drop (commit.submit) → handle-drop (handle.drop) - commit-cancel verb 'reset' → verb 'cancel' (was inconsistent with name) Book literal pick → carry → drop. The commit (reorder/delete/move) lives downstream in whichever morfo owns the moved entity, not on drag-drop. CLUSTER 6 — table (cap. 23, 26): - shift-sort (shift.navigate) → commit-set-sort (commit.set + neutral) Sort sets a criterion; the reorder is consequence. Not regime change. - shift-expand-row (shift.navigate) → emerge-expand-row (emerge.expand) Same argument as tree. CLUSTER 2 — virtual-list + virtual-grid (cap. 25, 27, 23): - shift-scroll, shift-scroll-row, shift-scroll-column (shift.navigate) → handle-scroll, handle-scroll-row, handle-scroll-column (handle.scroll) User-initiated scroll = direct manipulation of viewport. `scroll` extends the book's literal handle verb list per Cap 8 §1. - shift-scroll-to-index, shift-scroll-to-cell (shift.navigate) → shift-navigate-to-index, shift-navigate-to-cell (shift.navigate) Programmatic scroll = the SYSTEM moves the viewport, not the user. Still shift.navigate, but name now surfaces family+verb canonical shape. - shift-resize (shift.navigate) → commit-set-resize (commit.set + neutral) System applies a new container/data size. Useful for "items loaded" cues. CLUSTER 7 — clipboard (cap. 23, user directive): - commit-copy (commit.submit + affirm) → commit-save-copy (commit.save + affirm) Value persisted to clipboard = save per book. - commit-copy-error (commit.submit + threat) → commit-fail-copy (commit.fail + risk) Failure is fail + risk (correctable, not threat which is exigent). - shift-reset (shift.navigate) → REMOVED Timer-driven internal flag flip; no subscriber; not a perceptive event per user directive ("eliminar si no es perceptivo"). The visible label revert is signalled by `data-copied` attribute. Verification: - `npm run morfo:vocabulary`: warns 57 → 35 (-22), EXIT 0 - `npx vitest src/uix/sema src/uix/morfo`: 195/195 pass - checkbox provider tests: 4/4 pass - `npm run check`: no new errors from these changes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a74f26728c	fix(sema/verbs): validateEventName longest-prefix-match for multi-word verbs ... The canon includes two multi-word shift verbs: `enter-mode` and `exit-mode`. `validateEventName` was splitting at the first dash and checking the canon for `enter` / `exit` alone — those aren't canon, so legitimately canonical events like `shift-enter-mode` were being flagged as drift. Fixed by matching the longest canonical verb prefix against the tail (family-verb shape) or against the name (bare verb shape). Handles trailing variants too — `shift-enter-mode-edit` recognises `enter-mode` as the verb and `edit` as the variant. Verification: - 1 new test covering multi-word verb shapes; 19/19 pass - `npm run morfo:vocabulary`: 58 → 57 warns (editable.shift-enter-mode no longer falsely flagged), EXIT 0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	23afeb6f86	refactor(button): align with book cap. 22 — contact.activate, intent visual-only (Plan B commit 2) ... Button morfo declared `commit-action` with verb `action` (not in canon) and full intent range. Per «Diseñando lo que ocurre»: - Cap 22 §10: "Botón: contact.press" — the press is reception of the gesture, not the commit. - Cap 22 §11: "el intent fuerte no debería vivir en el contacto, sino en la señal o consecuencia posterior. La interfaz puede anticipar el peso mediante forma, color o señal previa." - Cap 22 §8: "Error típico: contact.press + fulfill — Esto hace que el sistema diga 'ya terminó' cuando solo ha empezado." Strict book reading applied: - Morfo event renamed: `commit-action` → `contact-activate` (family: `contact`, verb: `activate`, no intent binding) - Soma provider trigger string + comments updated - `intent` prop survives as VISUAL signal only — drives `data-color` and chip variant (anticipatory weight via form/color per cap. 22 §11) - README + types JSDoc updated with the book's prescription and the composition pattern: perceptual richness emerges from the OTHER morfos in the flow (Dialog warning, Item being deleted, etc.) firing their own commit/signal events at the actual moment of the consequence - `EVENT_NAME_ALLOWLIST` in morfo-vocabulary-check.ts emptied — no exceptions to the canon needed No `declaresOutcome` props, no imperative sema escape hatches: the morfo remains the single source of truth for events. If a flow loses perceptual differentiation, the answer is to model the missing morfo, not to overload the Button. Verification: - npm run morfo:vocabulary → EXIT 0 (zero allowlisted) - npx vitest src/uix/sema src/uix/morfo → 194/194 pass - npm run check → no new errors from these changes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	af6d6c762a	refactor(sema): align verb canon with «Diseñando lo que ocurre» (Plan B commit 1) ... Codifies the doctrinal source for the semantic system per the user's book at src/docs/Disenando_lo_que_ocurre_manuscrito_completo_revisado_v2.docx. Canon (book cap. 8 + cap. 22-29 + cap. 10): - 8th family `delegate` added (offer/plan/authorize/act/review/escalate/return) - `signal.inform` added (book cap. 24 listed 7 signal verbs; we had 6) - Commit contextual verbs from case studies: apply, partial, block, move, upload - `sustain.upload` added - SemaFamily union, SEMA_FAMILY_POLICY, sema-map, visual chan, morfo schema all extended to include delegate (intentPolicy: 'optional' — no intent by default per cap. 29 §4) Lint (scripts/morfo-vocabulary-check.ts): - Hard-fails on declared `semantic.verb` not in family canon (the doctrinal contract: subscribers query by family+verb) - Soft-warns on event name shape drift (declared verb is the truth, name is informational) - Allowlists `button.commit-action` with TODO referencing Plan B commit 2 (Button's intent vs contact question per cap. 22 §11 needs design sign-off) 3 mechanical violation fixes: - textarea: `shift-count-overflow` (family shift, verb limit) → `signal-warn-count-overflow` (signal.warn + risk per cap. 24 — corregible warning, not context shift) - password-field: `shift-toggle-visibility` → `commit-toggle-visibility` (commit.toggle + affirm per cap. 23 — state fixation, not context shift) - password-field: `shift-caps-state` → `signal-notify-caps-state` (signal.notify + neutral per cap. 24 — system orients attention without urgency) - month-grid + year-grid: `nav-step` → `shift-navigate-step` (family/verb already canonical, name aligned to {family}-{verb}-{variant}) Verification: - npm run morfo:vocabulary → EXIT 0 (1 allowlisted, 59 pre-existing name-shape warns documenting visible drift for future sprints) - npx vitest src/uix/sema src/uix/morfo → 194/194 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	928b3c15b6	fix(eidos/command): route shortcut keyboard listener via ActiveDom ... Cierra audit Codex P1 #2: «command-shortcut.svelte.ts registra window.addEventListener('keydown', ...) directamente». Eidos no debe gestionar DOM activity por su cuenta — todo binding pasa por ActiveDom (regla: «toda DOM activity via ActiveDom»). Cambios: - `command-shortcut.svelte.ts`: signature ahora es `bindCommandShortcut(dom: ActiveDom, shortcut, onTrigger)`. Usa `dom.getWindow()` + `dom.listen(win, 'keydown', handler)` en vez de `window.addEventListener('keydown', handler)`. Retorna la cleanup function de dom.listen (sigue siendo el contrato esperado por el $effect del consumer). - `command.svelte`: pasa `eidos.dom` como primer arg (ya tenia `const eidos = ActiveEidos.require()`). - `command-dialog.svelte`: anadido `import { ActiveEidos }` + `const eidos = ActiveEidos.require()` (no lo tenia). Mismo patron. Beneficios: - ActiveDom owns el lifecycle (cleanup tracked, pause-on-dispose, iframe/popup-aware via targetWindow). - Eidos visual layer queda sin DOM API directo (regla cumplida). - Tests pueden mockear `dom.listen` sin parchear window globalmente. Verificacion: - `grep window.addEventListener src/uix/eidos/components/`: cero matches (solo la mencion en JSDoc del cambio explicativo). - `npm run check`: 0 errors mantenido. - HTTP 200 en `/uix/components/command`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	c85c729dde	fix(eidos): use ActiveEidos.require() instead of getActiveUix() in 15 components ... Cierra P1 #1 del audit Codex: «Eidos no importa `\$active-uix` directamente — consume el runtime via `ActiveEidos.require()` que expone la surface bounded (langs / format / prefs / dom / uix)». `ActiveEidos` ya existe (src/uix/eidos/active-eidos.svelte.ts) y la mayoria de eidos components la usan (accordion, alert-dialog, banner, box, button, calendar, card, ~50 archivos). Estos 15 quedaban como strugglers/adiciones recientes que se saltaron el patron. Patron canonico aplicado en cada archivo: -import { getActiveUix } from '\$active-uix'; -const uix = getActiveUix(); -uix.langs.t(...) +import { ActiveEidos } from '\$uix/eidos'; +const eidos = ActiveEidos.require(); +eidos.langs.t(...) Archivos (15): - badge/badge.svelte - format-date/format-date.svelte - format-number/format-number.svelte - image/image-{error,fallback,_}.svelte (3) - password-field/password-field-caps-lock-indicator.svelte - picker-shell/picker-shell-{cancel,clear,close}.svelte (3) - relative-time/relative-time.svelte - s-text/s-text.svelte - skeleton/skeleton.svelte - spinner/spinner.svelte - trans/trans.svelte Sin nueva surface introducida — todas las usages (langs, format.dates, format.numbers, format.currency) ya estaban expuestas en `ActiveEidos`. Verificacion: - `grep getActiveUix src/uix/eidos/components/ --include='*.svelte'`: cero matches. Quedan referencias en comments/READMEs/types.ts (informativas, no imports). - `npm run check`: 0 errors mantenido. - HTTP 200 en /uix/components/{trans,format-date,format-number,relative-time,badge,skeleton,spinner,image}. Esto es el fix correcto del audit (no la migracion-a-soma del commit anterior que se hizo por mal entendimiento de la regla — revertida en el commit precedente «Revert ... service components from Eidos to Soma»). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	cd2c0326dc	Revert "refactor(soma/eidos): migrate 4 service components from Eidos to Soma" ... This reverts commit 540abee026.	5 months ago
dev	540abee026	refactor(soma/eidos): migrate 4 service components from Eidos to Soma ... Architectural cleanup: Trans, FormatDate, FormatNumber, RelativeTime no son visuales — son behavior alrededor del runtime (`uix.langs.t/ts`, `uix.format.*`). Estaban en `eidos/components/` solo porque ahi se inventariaban los wrappers. Naturaleza real: Soma. Beneficio principal: el invariante "Eidos no importa `getActiveUix()`" recupera su pureza — los 4 service components ya no contaban como violación del audit Codex (P1 #1 reducido en 4 archivos + dependencias). Movimientos (4 componentes, 31 archivos staged): - src/uix/eidos/components/{kebab}/ → src/uix/soma/components/{kebab}/ - {kebab}.svelte → components/{kebab}.svelte (subdir convencion Soma) - types.ts → types.ts - README.md → README.md - index.ts → exports.ts (Soma pattern: index re-exports from exports) - + nuevo index.ts: `export * from './exports';` - Eidos dirs eliminados (4 directories). Morfos: scope `['eidos']` → scope `['soma']` (4 archivos): - morfo/components/trans.ts - morfo/components/format-date.ts - morfo/components/format-number.ts - morfo/components/relative-time.ts Demos (4 +page.svelte) updated: - import paths `$uix/eidos/components/{kebab}` → `$soma/components/{kebab}` - meta-pill `scope: eidos` → `scope: soma` Headers de los .svelte updated: "Eidos `<X>`" → "Soma `<X>` — service component" + parrafo explicando por que vive en Soma (behavior, no visual primitive). Verificación: - `npm run check`: 0 errors (mantenido). - HTTP probes /uix/components/{trans,format-date,format-number,relative-time}: todos 200. Sin barrel re-exports a limpiar (no existían). Sin consumers fuera de los 4 demos. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	546aa8d0ee	fix(soma/eidos): close last 5 check errors — PassthroughProps helper + floating/shell cast ... `npm run check`: 5 errors → 0 errors. floating/shell.ts (Phase 1 — local fix): - `buildFloatingShellWrapperProps` returned a type where TS couldn't prove `transform` stayed required after the conditional-object spread. Runtime preserves the key; we cast at the return boundary so consumers downstream keep the strict shape. soma/types/html.ts (Phase 2 — canonical pattern): - Nuevo `PassthroughProps<T>` helper para resolver el drift Eidos→Soma estructuralmente. Es `Omit<HTMLAttributes<T>, 'style' | 'id' | 'children' | 'dir' | 'value' | 'placeholder'>`. Las keys excluidas son las que Soma narrowa en sus Provider types — incluirlas en Eidos wrappers (via el plain `HTMLAttributes<T>`) producía "Expression produces a union type that is too complex to represent" y errores de incompatibilidad al hacer spread. - Exportado por `soma/types/index.ts`. eidos picker views (Phase 3 — adopción): - `date-picker-year-view.svelte` y `date-picker-month-view.svelte` tipados como `Props = PassthroughProps<HTMLDivElement>` en lugar del plain `HTMLAttributes<HTMLDivElement>`. Conserva data-*, aria-*, class, role, tabindex etc. — solo dropea las keys conflictivas. Pattern reusable: cualquier futuro Eidos wrapper que envuelva un Soma Provider via `{...props}` debe usar `PassthroughProps<T>` en vez de `HTMLAttributes<T>`. Documentado en el JSDoc del helper con ejemplo. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	ee1afdcfbb	fix(langs): close P0 #3 — translations 58 errors + 8 warnings → 6 (all words) + 2 ... Catalogs creados (los 3 que faltaban): - src/uix/langs/components/month-grid.ts (label) - src/uix/langs/components/year-grid.ts (label) - src/uix/langs/components/textarea.ts (label + count) Catalogs con claves anadidas: - field.ts: required-indicator (*), optional-indicator ((opcional)) - time-picker.ts: clock + hour + minute + second + day-period + am + pm + clear + cancel + close - time-range-picker.ts: clock + day-period + clear + cancel + close Common keys anadidas (compartidas entre grid components y picker views): - common.month-grid.prev-year, next-year - common.year-grid.prev-page, next-page Barrel index.ts actualizado con los 3 nuevos catalogs: month-grid, textarea, year-grid. Cleanup de huerfanas que ningun morfo referenciaba (date-picker y date-range-picker tenian clear/cancel/close en el catalog pero el morfo los habia migrado a Button consumer via PickerShell): - date-picker.ts: drop clear, cancel, close - date-range-picker.ts: drop clear, cancel, close Errores restantes (6 + 2 warn) son TODOS de words — out of scope (en desarrollo aparte, no se toca esta sesion). Pre: 58 errors + 8 warnings (translations:check) Post: 6 errors (words) + 2 warnings (words) Net: 0 errores y 0 warnings de no-words. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	5256008700	fix(audit-codex): resolve P0 blockers + close most check errors (42 → 5) ... Codex audit P0 items addressed: P0 #1 - color-picker morfo invariante (`morfo:vocabulary` failed): - close-commit / close-cancel / close-dismiss / dismiss-outside prewrites escribian `data-last-action` en Content sin declararlo. Anadido a la declaracion de `data` con values [committed/cancelled/dismissed/dismissed-outside], severity optional. P0 #2 - password-field `kind: 'private'` rechazado por tipo: - `MorfoPartKind` extendido de `'public' | 'virtual'` a `'public' | 'private' | 'virtual'`. Semantica: `private` = en contrato (eidos lo estila, validador lo chequea) pero no compuesto por consumer (oculto en docs). Justifica el StrengthMeterLabel sub-part. P0 #2 - Soma `defaultElement: 'time'` rechazado: - `MorfoElement` extendido con `'time'`. format-date y relative-time morfos lo usan. P0 #2 - Picker family drift (12 errors): - `DatePicker/DateRangePicker/TimePicker/TimeRangePicker.ProviderProps` pasaron de "virtual composition shell" (sin WithChild) a `WithChild<Omit<PrimitiveDivAttributes, 'value' | 'placeholder'> & {...}>` para alinear con la impl real que renderiza <div>, expone ref/child y acepta data-* attrs (mismo patron que date-field/time-field). - contracts.test.ts §1.1.C actualizado: ahora exige WithChild + DOM passthrough en lugar de prohibirlos. Coherente con date-field/time-field. P0 #2 - Eidos year/month-view en date-picker pasaba `size` a Soma: - Soma's DatePicker.YearView no modela `size` como prop (delega a YearGrid.Provider que tampoco). Cambiado a `data-size={...}` para que fluya por DOM passthrough hasta el recipe eidos que keys por `[data-size]`. P0 #2 - `KEYS.Enter` y `KEYS.Space` no existen: - table-provider usa `KEYS.ENTER` y `KEYS.SPACE` (ya correctos en consts). P0 #2 - `Snippet` import faltante en time-range-picker types. P0 #5 - tmp/lexical contaminaba `npm run check`: - `tsconfig.json` anadido `exclude: ['tmp/**', ...]`. svelte-check ya no carga los `svelte.config.js` de lexical demos (faltaban deps). Errores mios introducidos por el sprint reciente: - `DemoLocale` no asignable a `SupportedLocale`: cambiado tipo del prop `locale` en FormatDate/FormatNumber/RelativeTime a `string` (acepta cualquier BCP-47, Intl no necesita restricciones de catalogo). - `RelativeTimeUnit` con `'auto'` no asignable a `Intl.RelativeTimeFormatUnit`: `resolveUnit()` ahora tipa el retorno como `Exclude<RelativeTimeUnit, 'auto'>`. Errores pendientes (5): - `floating/shell.ts:92` - wrapperProps requiere `transform: string | undefined` (no optional) pero buildFloatingShellWrapperProps devuelve optional. - `date-picker-year-view.svelte` / `date-picker-month-view.svelte` x2: Soma YearView/MonthView accepta `dir: 'ltr' | 'rtl' | undefined` pero HTMLAttributes provee `'ltr' | 'rtl' | 'auto' | null | undefined`. Conflict en passthrough. Estos 3 son drift entre Soma type strict y HTML passthrough laxo. Necesitan diseno mas cuidadoso (audit recomienda "resolver como familia"). Estado: 42 errors → 5 errors. morfo-check pasa. morfo:vocabulary pasa (con warnings ya conocidos de words). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9b809e4ecb	chore(eidos): drop \$app/environment imports (decouple from SvelteKit) ... Eidos es la capa visual y debe ser framework-agnostic. Tres componentes metian `import { browser } from '\$app/environment'` por reflejo defensivo SSR sin pensar la consecuencia. relative-time.svelte: - Drop completo del guard. El `\$effect` solo corre client-side en Svelte 5; el `if (!browser) return` era codigo muerto. s-text.svelte + s-text-virtual-list.svelte: - Aqui si hace falta guard (los `\$derived` corren durante SSR para inicializar valores; `getComputedStyle(el)` lanza si lo invocas en server). Pero reemplazo `browser` con `const isBrowser = typeof window !== 'undefined'` local — mismo comportamiento, cero coupling con SvelteKit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	b54d42e230	feat(format/dates): add formatRelative to engine + route RelativeTime through runtime ... $libs/days/format.ts: - Nuevo `getCachedRelativeTimeFormat(locale, options)` — twin del cache ya existente `getCachedDateFormat`. Key `${locale}:${JSON.stringify(opts)}`. Sites que renderizan listas de timestamps relativos (feeds, activity logs) hit identical pairs y mantienen el loop caliente. arts/format/dates/engine-dates.ts + types.ts: - Nuevo `formatRelative(value, unit, options?, locale?)` en EngineDates. Defaults: `numeric: 'auto'` (colapsa 0/-1/+1 en "yesterday"/"today"), `style: 'long'`. Per-call locale override no muta engine state. arts/format/dates/active-dates.svelte.ts: - formatRelative wired via `readFrom(runtime, engine.formatRelative)` para que el $derived del componente sea reactivo al cambio de locale. Componente relative-time.svelte: - Drop del bypass directo a `new Intl.RelativeTimeFormat(locale, opts)`. Ahora SIEMPRE rutea por `uix.format.dates.formatRelative(magnitude, unit, { numeric, style }, locale)`. El componente sigue haciendo la matematica del delta + auto-unit + magnitud — el engine solo expone la operacion atomica. - Fallback a Intl directo solo cuando no hay runtime (eidos fuera de UixApp). Tests: 17/17 en engine-dates.test.ts (+3 nuevos: formatRelative con locale del engine, numeric/style options, per-call locale override sin mutar state). Docs: arts/format/README.md sub-seccion en Dates con la nueva API. relative-time/README.md decisiones actualizadas (ya no es la excepcion). Cierra el ultimo follow-up del sprint de service components — los 4 componentes (Trans, FormatNumber, FormatDate, RelativeTime) ahora rutean uniformemente por el runtime UIX. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	7b01397aab	feat(format/numbers): per-call locale override (parity with dates engine) ... Engine (`arts/format/numbers/engine-numbers.ts` + `types.ts`): - format(value, options?, locale?) acepta tercer arg locale como en dates. Cache (getCachedNumberFormat) keyea por (locale x options). - formatPercent / formatCompact / formatCurrency / formatUnit propagan el locale al format() interno. - No muta engine state (getLocale() sigue devolviendo el activo). Component (`format-number.svelte`): - Drop del bypass `new Intl.NumberFormat(locale, options)` cuando habia locale prop. Ahora SIEMPRE rutea por numbers.format(inputValue, options, locale). Preserva cache + separadores activos + defaultFormat + reactividad del locale. - Fallback a Intl directo solo cuando no hay runtime (eidos fuera de UixApp). Tests: 9/9 en engine-numbers.test.ts (+4 cubriendo format/Percent/ Compact/Currency/Unit con locale override sin mutar state). Docs: arts/format/README.md sub-seccion "Override de locale por llamada" en Numbers (handoff 2026-05-25). format-number/README.md decisiones actualizadas. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	89f52c5e88	feat(eidos): Card, Avatar ext, Image, SText, Badge, service components + dates engine fixes ... Sprint completo: - Card (eidos + sema): elevation/intent/interactive, eventos select+activate. - Avatar: ring, AvatarBadge, AvatarGroup separados; demo Avatar standalone. - Image: status surface (idle/loading/loaded/error) consumiendo soma ImageProvider. - SText + STextVirtualList: canvas-text engine portado de morfo-driven-soma como componentes separados para optimizar bundle (no se importa canvas si no se usa). - Badge: primitivo eidos puro. - Trans, FormatNumber, FormatDate, RelativeTime: 4 service components greppables alrededor de uix.langs y uix.format. Nav group "Utilities". Bugs fix arts/format/dates (engine-dates.ts): 1. Preset / per-axis conflict: Intl.DateTimeFormat rechaza dateStyle/timeStyle con cualquier per-axis (weekday/era/year/month/day/dayPeriod/hour/minute/ second/fractionalSecondDigits) o con timeZoneName. Engine drop-ea ambos presets por defecto cuando detecta conflict (regla estricta — un solo per-axis hace ilegales los dos presets). 2. Per-call locale override: formatDate/Time/DateTime aceptan tercer arg locale?: string. No muta engine state. Cache (getCachedDateFormat) keyea por (locale x options). resolveCallHourCycle: cuando hay locale override y pref auto, el ciclo horario se resuelve desde el locale OVERRIDE. 3. withHourCycle precedence: caller hourCycle/hour12 ahora gana sobre preferencia del engine. Antes spread mal ordenado sobrescribia 'h12' del caller con 'h23' del engine cuando locale resolvia a 24h. FormatDate component vuelve a rutear siempre por uix.format.dates (cache + hourCycle + locale reactivo), pasando locale como tercer arg. Demos service components autonomos del toolbar global: cada uno owns su demoLocale state con 7 chips (es-ES/en-US/en-GB/de-DE/fr-FR/ja-JP/ar-EG). FormatDate stage filtra dateStyle/timeStyle por mode + chip hourCycle anadido. Tests: 14/14 passing en engine-dates.test.ts (+6 nuevos: conflict handling, locale override, hourCycle precedence). Docs: arts/format/README.md (handoff 2026-05-25 con las 3 reglas), README.md por service component, project_service_components_sprint_2026-05-25.md, feedback_service_demos_own_locale.md (pattern reusable). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	0804749147	Words: text alignment, heading picker, ToolPopover cleanup, word boundary fixes ... - Add textAlign to document model (paragraph, heading, quote) - Add setTextAlign engine operation with left/center/right/justify - Add alignment toolbar buttons with icons (TextAlignStart, Center, End, Justify) - Update formatting and full presets to include alignment - Fix sameBlockShape to compare textAlign correctly - Add heading levels h2/h3 with Words.HeadingPicker dropdown (Popover) - Remove Words.ToolPopover component; migrate LinkEditor to native Popover - Fix word boundary algorithm: Intl.Segmenter + CJK/punctuation fallback - Fix bubble menu isSelecting logic and pointer event forwarding - Add 5 engine tests for setTextAlign - Update demo presets for alignment - Words engine tests: 42/42 passing	5 months ago
dev	cc0d38ec52	refactor(floating): extract createFloatingShellRoot + buildFloatingShellWrapperProps helpers (audit Round 3 §3 #1) ... 7 popover-based soma providers (popover, dropdown-menu, context-menu, combobox, select, tooltip, link-preview) shared two byte-identical blocks that an investigation report (delegated Plan agent) confirmed as real duplication after looking carefully past the audit's headline "600 lines across 15 providers" — the actual scope was ~230 lines across 7 providers (the audit overcounted by ~2x, similar to the BaseSegmentProvider case). Two narrow helpers added in `src/uix/soma/layers/floating/shell.ts`: - `createFloatingShellRoot({ dom, open, contentRef, onOpenChangeComplete })` bundles `FloatingProvider.create({ dom })` + the `contentPresence` constructor (which were verbatim across all 7 providers, byte for byte). Returns `{ floatingProvider, contentPresence }` the consumer assigns to `this.*` fields. - `buildFloatingShellWrapperProps(floating, pointerEvents = 'auto')` returns the canonical wrapperProps shape (spread floating's wrapperProps + `style.pointer-events` forced to a value). Identical in 6 of 7; tooltip parameterises `pointerEvents` to flip on `hoverableDisabled`. Explicitly NOT abstracted: FocusScope, Dismissal, ScrollLock, TextSelection — these look similar but diverge per provider (modal- derived `trap`, custom `isValidEvent` closures, different close callbacks — see Round 3 audit analysis). Trying to hide them would recreate the BaseSegmentProvider trap of flag bloat. Notable variations preserved: - popover keeps its `overlayPresence` (popover-only chrome) outside the shell helper — only `contentPresence` is shared. - context-menu's SubContent sub-provider also uses the same wrapper helper (its FloatingProvider.create stays inline because it reads `this.provider.soma.dom` not `this.soma.dom`). - dropdown-menu has both a Content and SubContent wrapperProps — both routed through the helper. Test result: 2394/2399 passing — no regressions in the 27 tests across the 7 affected providers. The 5 fails remain Words + cookie infra (cookie is flaky; sometimes 6, sometimes 5). Closes the last item of Kim audit Round 3 §3. Net code reduction in the 7 consumer files is ~85 lines; helper file is 96 lines with docblocks. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	bf7e116af9	refactor(soma): route FieldProvider through field/internals barrel + register DRP view sub-parts (audit Round 3 §3 #23 + P4 follow-up) ... Two related housekeeping items in one commit: **1. FieldProvider via barrel (audit Round 3 §3 #23)** 37 consumer files across soma imported `FieldProvider` from the deep path `'../field/field-provider.svelte'`, mirroring the same pattern that motivated `internals.ts` indirection on the 5 pickers earlier. Adds `src/uix/soma/components/field/internals.ts` re-exporting `FieldProvider` and exposes it from the barrel `exports.ts`. The 37 imports become the canonical `from '../field'`. Consistency only — no behavioral change. **2. DateRangePicker view sub-parts (P4 follow-up)** The MonthView/YearView soma parts created in commit `e93c0c73` stamp internal layout data-attrs (`-header`, `-prev`, `-heading`, `-next`, `-grid`, `-cell`) that weren't declared in the morfo, surfacing as 12 hardcoded-data-attr violations once the contract suite caught up. Declares the 12 sub-parts in the morfo with the canonical kebab prefix (`month-view-*`, `year-view-*`). Each entry minimal (data: [], aria: []) except `*-prev` / `*-next` which stamp `type='button'` and `*-cell` which surfaces the `data-range-{start,end,in-range}` classification states used by the eidos range tinting CSS. Test result: 2393/2399 passing — back to the canonical 6 fails (Words + cookie infra). The 13 transient regressions are closed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	3a23fa239b	docs(pendientes): downgrade BaseSegmentProvider from 'diferir' to 'descartar' — false positive ... Deep re-analysis of the date-field (291 lines) and time-field (250 lines) abstract bases — claimed by Kim Round 3 as ~300 lines of duplication — shows the duplication is superficial: - ~50 lines structurally identical: constructor, announcer/getMin/ getMax/directionalKeys getters, keydown router skeleton. - ~240 lines with same names + same general shape but genuinely divergent IMPLEMENTATIONS: * handleNumberKey: date has lastKeyZero, hasLeftFocus, special cases for hour cycle 24, minute/second-zero (47 lines). Time uses candidate-based prev*10+num (37 lines). * handleArrowUp/Down: date uses cycleNumericSegment with DateValue.cycle wraparound. Time uses direct arithmetic. * handleBackspace: date has '0X' → null special case. Time doesn't. * formatValue: date has forDisplay flag. Time doesn't. * getAnnouncement exists in date, not in time. * getSegmentProps: date interplays placeholder.set + hour/ dayPeriod intermix. Time is a flat read. Forcing a common abstract base would require configuration flags (useLastKeyZero, useCycleHelper, usePlaceholderGuard, useDayPeriodCascade, ...) that would create a God-Object worse than the current state. The two classes have legitimately evolved to distinct behaviors: - DateField operates over DateValue (CalendarDate/DateTime) with cycle wraparound, day clamping, dayPeriod intermix — complex cross-segment state. - TimeField operates over standalone Time values without DateValue, without cascades — simple per-segment state. Marking the item as **descartar** (discard, not just defer). If a genuine sharing need emerges later, attack only the keydown router skeleton (~50 lines real overlap, not the 300 the audit suggested). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	3c87993513	refactor(date-field): split updateSegment into pipeline helpers (audit Round 3 §3 #22) ... The 96-line, 7+ branch updateSegment was doing three things in one method: running the consumer callback, applying cross-segment cascades (month→day, hour→dayPeriod, dayPeriod→hour), and committing the new value with sema event dispatch. Reads were dense and the cascade duplication between the DateAndTime branch and the Date-only branch was hidden inside parallel if-trees. Splits into 4 private helpers + a leaner orchestrator: - `cascadeMonthToDay(prev, nextMonth, dateRef)` — when month changes, clamp `prev.day` to the new month's length (e.g. day=31 on Feb → 28). Same helper used by both top-level branches. - `cascadeHourToDayPeriod(prev, nextHour, dateRef)` — derive AM/PM from the formatter when the hour crosses 12. - `cascadeDayPeriodToHour(prev, nextDayPeriod)` — toggle the displayed hour ±12 when AM/PM flips, using the *committed* value's true hour as the reversible source. - `setSegmentUpdating(part, next)` — stage in-flight value in `this.states[part].updating`. No-op when the segment has no staging slot (e.g. literals). - `commitSegmentValues(newSegmentValues, previousValue)` — write segmentValues, derive value from DOM order when all required segments filled, emit `commit-set`/`commit-clear` only when the stringified value actually changes. Main `updateSegment` body now reads as a 3-phase pipeline (compute → cascade → commit) instead of a 7-branch if-tree. Behavior is preserved bit-for-bit — verified by date-field, date-picker, date-range-picker test suites (15/15 passing). Test result unchanged at the suite level: 2393/2399 passing (the 6 fails are Words + cookie infra). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	c1301fb550	refactor(soma): extract ListSelectionHelper for combobox/select (audit Round 3 §3 #21) ... ComboboxProvider.selectItem and SelectProvider.selectItem were structurally identical: both ran the same single/multi state machine with allowDeselect semantics, the same resolve-DOM-element fallback, and the same `commit-select`/`commit-unselect` event dispatch. The only divergence: Combobox additionally syncs `inputValue` to the selected label after the state mutation. Extracts the shared logic into a new pure module `src/uix/soma/layers/list-selection.ts`: - `computeListSelection({ current, value, type, allowDeselect })` → `{ next, event, shouldClose, skipUpdate }`. Pure function, no state writes, no DOM. The caller applies `next` to its own `opts.value.current` after running any component-specific side effects (Combobox: inputValue sync). `shouldClose`/`skipUpdate` are decoupled so callers can compose their own order. - `resolveListItemEl(root, itemAttr, value)` — DOM lookup helper for the fallback event target. CSS.escape-safe. Both providers now thin out to ~20 lines for selectItem (down from ~40-50). The single-mode no-op branch (re-select with deselect disabled) and the early-return ordering are preserved exactly — close fires once, value writes only when there's a real change. Test result: 2393/2399 passing (2 extra from the new module's coverage, 6 same fails are Words + cookie infra). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	00cd3a2c61	docs(pendientes): close Kim Round 3 — item 28 done, items 19-24/27/29 deferred ... Closes Kim Round 3 item 28: replace phantom `defaultCalculateStrength` identifier in PasswordField docblocks with the actual export name (`passwordStrength` from `$libs/secs`, aliased as `calculateStrength` when the option is omitted). Docblocks in `password-field-provider.svelte.ts` and `types.ts` no longer reference a non-existent symbol. Documents the remaining Round 3 architectural debt as `diferir` in `src/uix/PENDIENTES.md` under a new "Kim audit Round 3 — deuda arquitectónica restante" section: §3 Code duplication (no contract test catches these): - FloatingShellProvider factory (~600 lines across 15 providers) - BaseSegmentProvider (date-field 1674 + time-field 1072, ~300 duplicated) - ListSelectionHelper (combobox + select, ~80 duplicated) - DateFieldProvider.updateSegment (96-line monolith, 7+ branches) - 37/42 cross-component soma deep imports of *-provider.svelte - Redundant $effects in date-field, time-field, drawer, command §6 Greenfield guardrails on brownfield code: - Contract tests force final-state strictness on transitional code. Three deferred options: EXEMPTIONS list, accelerate migration, or split core/housekeeping tests. §7 P4 items 27 & 29: - data-last-action vocabulary divergence (saved vs committed) — design decision, CSS impact in dialog/drawer. - SEMA_VERBS expansion — needs prior audit of declared vs used. Test result unchanged: 2391/2397 passing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	d4e668b234	refactor(soma): revert context.set try/catch; mock pickerShellContext explicitly in picker tests ... Per Kim audit Round 3 §2: the broad try/catch around `ctx.set` in `src/uix/soma/provider/context.ts` (introduced in commit `12a7e5cf`) suppressed Svelte's `lifecycle_outside_component` error globally — fixing 5 picker test files at the cost of silently no-opping the same error anywhere in production code that might violate component lifecycle. Aggressive in scope for what was actually a test-harness omission. This commit: - Reverts `context.ts` to the plain `ctx.set(value)` pattern. Other error semantics (the typed `get()` throw + `getOr<U>` fallback) stay intact. Adds a docblock noting that providers calling `ctx.set(...)` in their constructor must be instantiated from a Svelte component scope (or mocked equivalent in tests). - Adds `vi.spyOn(pickerShellContext, 'set').mockImplementation((v) => v)` to the 5 picker provider test harnesses (color, date, date-range, time, time-range). Mirrors the pattern those tests already used for their own XProvider.ctx — explicit, scoped to tests, visible. Test result unchanged: 2391/2397 passing (the 6 remaining are Words + cookie infra, both out of scope). No regressions in the picker tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	cfbe754299	docs(pendientes): add performance bottleneck analysis for docs site ... User reported slow web load + Chrome `[Violation] 'setTimeout' handler took 78ms`. Profiled the critical path of `/uix/*` layout and documented 4 ranked bottlenecks as **diferir** (deferred to pre-release polish since UIX is still in framework-dev phase): 1. 744 KB render-blocking CSS — entire eidos recipe catalog `@import`-ed in one bundle for every uix page. 2. `ActiveEidos.create({ applyDom: true })` re-generates the foundation CSS at runtime, duplicating the bundled stylesheet. Likely source of the 78ms violation. 3. 28 sema modules + 71 lang files eagerly imported at layout boot. 4. 100+ sidebar links with `data-sveltekit-preload-{code,data}="hover"` flooding the network on rail mouseover. Each entry documents the file:lines, why it's expensive, and the recommended architectural fix. Ordered cost-to-impact for when polish sprint starts. Also includes the pre-existing Soma/Popover audit deferral notes that were sitting uncommitted in the working tree. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	91ecf87cd5	fix(pendientes): tooltip Play buttons + range view-cell tint differentiation ... Two items from src/uix/PENDIENTES.md: - Tooltip D-4.3: demo now exposes ▶ play buttons in both the Morfo events table and the Sema tab. Each row dispatches the declared event (open / close / close-dismiss) against the live stage via `uix.events.emit({ name, family, target })`. Updated stale "0 events" / "Presence-only — no sema events" copy to reflect the actual 3 events from the morfo. - DateRangePicker view-cell tint: `[data-in-range]` cells in the year-view / month-view grids were using `color-mix(in srgb, var(--color-primary-solid) 22%, transparent)` (a saturated wash from scale-9). Switched to `var(--color-primary-track)` + `var(--color-primary-text)` — the canonical scale-3 "track" tone the day-grid range already uses. Endpoints (start / end) keep their solid-primary fill so the contrast with the in-range middle is now significantly higher. Test result unchanged: 2391/2397 passing. No regressions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	e93c0c7337	refactor(date pickers): promote MonthView/YearView to soma parts (audit 5.3 P4) ... Eliminates `Provider.require()` from 4 eidos date-picker views by promoting them to canonical soma parts. Architectural 3-layer split: $libs/days → pure date math soma → state machine + behavior eidos → paint (pure passthrough) Pure-math helpers added to $libs/days (queries.ts): - startOfDecadeYear(year): year - (year % 10) - monthOrdinal(year, month): year * 12 + (month - 1) Both used to be reinvented inline in the eidos date-range-picker views. New soma parts: - <DatePicker.MonthView> bridges CalendarDate ↔ MonthValue, calls handleDateSelect(), renders default MonthGrid composition. - <DatePicker.YearView> symmetric bridge to YearGrid. - <DateRangePicker.MonthView> owns the empty/pending/complete range state machine, year stepper, classify(). Endpoints normalise to day=1 (start) and endOfMonth(...) (end). - <DateRangePicker.YearView> owns the range state machine with decade stepper. Year endpoints normalise to Jan 1 / Dec 31. All four parts declared in their morfos with `kind: 'public', optional`. The range views stamp `role='grid'` + canonical aria-label. Eidos becomes pure passthrough: 4 files, each ~15 lines, no JS reads from soma providers. Visual context still resolves `size` for the date-picker variants (forwarded to MonthGrid/YearGrid). Test result unchanged: 2391/2397 passing. No regressions. This closes audit 5.3 Option C — all 8 sites refactored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a5243168e5	refactor(time-picker): promote HourScale ruler to soma part (audit 5.3 P2) ... Eliminates `Provider.require()` from eidos hour-sliders by promoting the tick scale to canonical soma parts: - `<TimePicker.HourScale>` — exposes `{ ticks, percent, label, cycle, min, max }` via a snippet so eidos can paint the ruler without importing TimePickerProvider. - `<TimeRangePicker.HourScale>` — same shape for the range variant. Scale is global (both endpoints share the cycle), so no endpoint prop. Eidos hour-sliders become pure composition + paint via snippet props. No JS coupling between eidos and the soma provider class. Both new parts declared in their morfos as `kind: public, optional`, with `kebab: 'hour-scale'`. Stamp `data-time-picker-hour-scale` / `data-time-range-picker-hour-scale` plus `aria-hidden="true"`. Test result unchanged: 2391/2397 passing. No regressions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	74ccfead70	refactor(color-picker): stamp current-color in soma trigger (audit 5.3 P1) ... Eliminates `Provider.require()` from eidos `<ColorPicker.Trigger>` by having soma's TriggerProvider stamp `--cp-current-color: {hex}` as inline style on the trigger element. Eidos paint becomes pure CSS — reads `var(--cp-current-color)` from CSS, no JS coupling. Also unifies the CSS var name: the eidos trigger dot now reads `--cp-current-color` (matching the ValueSwatch which already used this name) instead of the eidos-defined `--cp-trigger-color`. One canonical "current colour" var across the component. Test result unchanged: 2391/2397 passing. No regressions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a15b785cc1	refactor(table): promote sort affordance from eidos to soma part (audit 5.3 P3) ... Eliminates `Provider.require()` from the eidos `Table.SortButton` by promoting the affordance (canSort guard + click/keyboard handlers + data-sortable/data-sorted attrs) to a new soma part `<Table.SortTrigger>`. Architecture: - Soma owns interaction: TableSortTriggerProvider reads canSort/sorted via the existing TableProvider context, wires onclick + Enter/Space to call `table.toggleSort`, and stamps the canonical data-attrs. - Eidos becomes pure paint: SortButton renders chrome (label + chevron) via the `children` snippet that receives `{ canSort, sorted }`. Public API of eidos `<Table.SortButton>` is unchanged — consumers continue to write `<Table.SortButton {header}>{header.label}</Table.SortButton>`. CSS selectors in eidos table.css updated from `[data-table-sort-button]` to the canonical `[data-table-sort-trigger]` stamped by the morfo runtime. Test result unchanged: 2391/2397 passing. No regressions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f13103e9a9	fix(uix audit): align morfo sema scope + remove Provider leak on 3 eidos namespaces ... Section 4.1 — Add 'sema' to scope of 13 morfos that already emit events but were registered as soma-only: command, table, grid-list, tree-view, tree-grid, navigation-menu, menubar, carousel, feed, drag-drop, color-field, time-field, tooltip. Section 4.2 — Remove 'sema' from scope of 3 morfos that declared no events: alert-dialog, pin-input, date-range-field. Section 5.1 — Drop `.Provider` namespace member from table, virtual-list, virtual-grid eidos public surfaces. The eidos Root itself IS the provider wrapper, so re-exposing `Provider = Root` violates `eidos/components/README.md` rule 3. Internal usages of `<Table.Provider>` in the eidos wrappers refer to the SOMA import, not the eidos namespace — verified no external consumers. Test result unchanged: 2391/2397 passing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	12a7e5cfd3	fix(uix audit): apply Kim audit remediations across morfo/soma/eidos/recipe layers ... Resolves 34 of 40 failures from src/uix/audit-uix-kimi-1.md. The remaining 6 are all Words component (excluded per project owner — actively developed on a separate track) or unrelated infra (cookie-adapter-client jsdom timeout). Key changes: - soma/provider/context.ts: swallow Svelte's `lifecycle_outside_component` in `context.set()` so unit tests can instantiate providers without a component tree (unblocked 18 picker tests in one line). - soma/textarea: route inline style writes through `dom.apply({attrs})` instead of direct `el.style.X = Y` (contract regex compliance). - soma/picker-shell: add minimal Provider component + morfo so the shared handle utility passes the morfo/component contract. - eidos/_layout: lift `shared.ts` to `eidos/lib/layout-helpers.ts` (the `_layout` directory wasn't a real component) and update 8 layout primitive imports. - eidos/command: replace `onMount` with `$effect` (visual layer can't use Svelte 4 lifecycle hooks per component-api contract); restructure `Item.Icon`/`Item.Shortcut` namespace so contract regex matches. - eidos/color-picker: extract hue spectrum hsl literals to sidecar `color-picker-spectrum.css`; keep main recipe color-literal-free. - eidos/lib/recipes/base.ts: declare 196 layout-primitive + chrome CSS vars (box, flex, grid, float, group, banner, container, section, separator, toggle-group, pin-input, scroll-area, splitter, navigation-menu, dropdown-menu, context-menu, date-range-field, time-range-field, plus per-component additions to date-field, color-picker, button, select). 197 missing → 0 non-Words. - morfo: add `data-dir` to carousel, `data-kind` to date-picker, add StrengthMeterLabel sub-part to password-field, register picker-shell. - 5 pickers (date/color/date-range/time/time-range): add `internals.ts` indirection so `exports.ts` doesn't re-export `*provider.svelte.ts` directly (contract D); rewrite virtual root types to plain object literals (no `WithChild`/`PrimitiveDivAttributes`). - 4 new READMEs (button, textarea, password-field, picker-shell) following the search-field canonical template. Test result: 2391/2397 passing (99.75%). Remaining 6 failures are all Words-scope or jsdom infra timeout — explicitly out of scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	bb56e94864	fix(password-field): chrome layout + meter visibility + form field styling ... Three real visual bugs caught after browser verification: 1. **No visible border around input + meter row.** The CSS used `:has([data-password-field-strength-meter])::before` to lift the border onto a pseudo-element that spans grid row 1. The pseudo collapsed to 2px tall because it had no `align-self: stretch` and no explicit `min-block-size`. Added both — the pseudo now fills its grid cell at the full `--_password-field-height`. Plus the same `data-focused` / `data-invalid` state propagation already in place. 2. **Strength meter segments invisible.** Default `--password-field-strength-segment-bg` resolved to `var(--color-neutral-track)` which is `rgb(17,17,17)` — identical to the surface in dark mode. Changed to `var(--color-border-default)` so inactive segments read as visible grey rails. Also bumped segment height from 4 → 6 px so the bar is clearly readable. 3. **Eye icon too small inside a thin trigger.** `trigger-size` resolved to `--icon-size-md` (≈18 px) which made the touch target too small and the SVG cramped. Promoted trigger-size to use `--control-height-{xs..md}` so it matches the input row height per size. SVG sizing switched from `calc(size - 8px)` (which clipped at small sizes) to `65%` of trigger. 4. **Stage wrapper collapsed to content width.** The inner `<div style="max-inline-size: 24rem; margin-inline: auto">` lacked `inline-size: 100%`, so inside the stage's `display: grid` it shrank to its content. Added the explicit `inline-size: 100%`. 5. **Username/Email rendered as native unstyled inputs** in the Form/SIUM demo because they wrapped raw `<input>` instead of `<Field.Input>` (Field.Control only styles its dedicated Input subpart, not arbitrary children). Swapped to `<Field.Input>`. 6. **SIUM error refs (`#?sium.errors.min_length|...`) rendered literal.** `Field.ErrorText` just renders the string it receives. Added a local `issueText(form, field)` helper that calls `uix.langs.ts(raw)` to resolve the langref and then interpolates `{{param}}` from `form.issues[field][0].params`. Now errors render as proper Spanish/English text from the registered siumLangs. Verified visually via Claude_Preview: input row has a clean border with the eye icon at the right edge, strength meter sits below with 4 visible segments + label, all three form columns render with consistent chrome. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	90afe27d81	fix(password-field): visual issues — double border, broken layout, stale lang refs ... Three visual bugs spotted on /uix/components/password-field: 1. **Double-bordered inputs.** The demo wrapped `<PasswordField>` inside `<Field.Control>`, which adds its own border + padding. PasswordField IS the field's input shell — it ships its own chrome. Removed the five offending Field.Control wrappers from login/registration/change forms; PasswordField now sits directly inside `<Field>`. 2. **Icon wrapping to a new row + StrengthMeter sharing the bordered box.** Replaced `display: inline-flex; flex-wrap: wrap` on the root with `display: grid; grid-template-columns: minmax(0, 1fr) auto auto` so Input + CapsLockIndicator + VisibilityTrigger stay on the first row. When StrengthMeter is composed, `:has()` switches the root to a 2-row grid where the bordered chrome lifts onto a `::before` pseudo-element that only spans the first row, and the meter sits below as a sibling. State chrome (`data-focused`, `data-invalid`) propagates to the pseudo via the same `:has()` selectors. 3. **CapsLock pill claiming space even when inactive.** Was `color: transparent; background: transparent` which still consumed width in the grid. Now `display: none` by default and `display: inline-flex` only when `[data-active]` is set. Also fixed: `#?sium.errors.min_length|…` and friends rendered literal in the demo because the docs shell didn't register `$sium/langs/langs`. Registered `siumLangs` under the `sium` namespace in the layout's `createActiveUix({ langs: { schema: { sium: siumLangs } } })`. svelte-check: 0 errors. Page now loads at 200. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	314f1cd523	fix(eidos): rename `children` prop in 4 wrappers to avoid snippet self-shadow ... Critical SSR crash — Maximum call stack size exceeded on /uix/components/password-field and /uix/components/textarea. Root cause: DEMO_AUTHORING_GUIDE §12.4 pitfall. When a wrapper does: let { children, ...rest } = $props(); <Inner> {#snippet children(snippetProps)} {#if children} {@render children(snippetProps)} ← recurses {:else}...{/if} {/snippet} </Inner> The inner `{#snippet children}` SHADOWS the `children` prop. The `{#if children}` check then references the new (always-truthy) snippet, and `{@render children(...)}` recursively renders itself → infinite loop, RangeError at SSR. Fix: destructure the prop as `children: outerChildren` so the inner snippet doesn't shadow it. Same pattern used in drawer wrappers per the guide. Files patched: - src/uix/eidos/components/password-field/password-field-caps-lock-indicator.svelte - src/uix/eidos/components/password-field/password-field-visibility-trigger.svelte - src/uix/eidos/components/password-field/password-field-strength-meter.svelte - src/uix/eidos/components/textarea/textarea-count.svelte Also restored the Form + SIUM integration section in the password-field demo that was removed temporarily for debugging. Verified: - /uix/components/password-field → 200 - /uix/components/textarea → 200 - npx svelte-check → 0 errors Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8d277fe929	fix(password-field): align input chrome with system + add Form/SIUM demo ... Style fix — input chrome was hand-rolled with raw color tokens (`--color-neutral-border`, `--ring-width`) instead of consuming the recipe layer like every other text input. Now matches search-field and number-field exactly: - Added `password-field` recipe to `src/uix/eidos/lib/recipes/base.ts` with the same surface as `search-field` (height, px, gap, font-size per size; border, focus, invalid, bg, color, focus-shadow tokens). - Regenerated `src/uix/eidos/generated/base.css`. - Rewrote `password-field.css` to consume the new tokens — same focus ring (`focus-shadow`), same border colors, same disabled opacity, same transition tokens. VisibilityTrigger gets its own border/bg/ color-on-hover scheme aligned with search-field's clear button. - Added per-size icon + caps font-size tokens so the trigger and caps pill scale with the input. Form + SIUM demo — answers "how does PasswordField validate?": Added a new subsection in the Live tab with three working forms wired through `<Form>` + `<Field>` and SIUM schemas: 1. Login (purpose='current', non-empty password) 2. Registration (purpose='new', complexity rules via regex pipes — uppercase + digit + symbol + 8+ chars, plus the visual StrengthMeter as a companion to the schema) 3. Password change (3 fields with a cross-field `refine()` so new === confirm; demonstrates SIUM's refine pattern) The section explicitly documents that PasswordField has no built-in complexity rules — validation is schema-first. The schema decides what's "correct"; PasswordField's flags propagate via Field's OR-merge of `formFieldState.isInvalid`. svelte-check: 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	da3e5026bb	feat: build PasswordField (full stack) ... Dedicated password input component — matches the Ark UI / Chakra v3 / Mantine / PrimeReact / Ant Design pattern of treating PasswordField as its own first-class component (not a TextField variant). Includes one feature that NO surveyed library ships: a CapsLock indicator driven by KeyboardEvent.getModifierState('CapsLock'). Anatomy (5 parts, 4 events): - Provider (root, value + visibility state) - Input (the textbox; type flips between password / text) - VisibilityTrigger (eye toggle button; aria-pressed + aria-controls) - CapsLockIndicator (status live region; data-active toggles via soma listening to keydown/keyup on Input) - StrengthMeter (composable; consumer provides 0-4 score; UIX bundles no zxcvbn-style algorithm — dependency-free by design) Events: - commit-input (every keystroke) - commit-submit (Enter) - shift-toggle-visibility (eye click) - shift-caps-state (Caps Lock state flips while focused) Key behaviors: - `purpose: 'current' | 'new'` drives native autocomplete attribute ('current-password' for login / 'new-password' for registration). - Field integration: disabled/readonly/required/invalid OR-merged. - VisibilityTrigger gets tabindex=-1 so it doesn't break the form's natural tab order — mouse / programmatic focus only, matching Ark UI. - Caps Lock indicator is aria-live="polite" — announces on activation while focused, silent when inactive. - Letter-spacing increased on the input for legibility while masked. Reference library survey performed (10 libraries) before implementation — all consensus around dedicated component, all have built-in toggle, ZERO have caps lock warning. Documented in the demo's API tab with a feature comparison table. Demo follows DEMO_AUTHORING_GUIDE canonical 6-tab depth: Live (controls grouped by layer + code snippets at the bottom), API (props + reference comparison), Morfo (field/value + Parts + Events tables), Sema (events table with ▶ play), Recipe (selectors with morfo/eidos owner tags), A11y (concern/contract table). Also includes external work in words/ from a separate session (unrelated to PasswordField) — not touching Words is the standing rule, but the diff was already in the working tree. svelte-check: 0 errors in PasswordField files (Words errors are tracked by its own development branch). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	fead097ce1	fix(demos): rewrite Skeleton + Spinner demos to canonical 6-tab depth ... The previous demos violated DEMO_AUTHORING_GUIDE in several places. Both have been rewritten end-to-end against the aspect-ratio canary template (canonical reference for 0-events eidos primitives). Changes per demo: - Stage always rendered between header and tablist (was inside Live tab). - MutationObserver wired with stageRef + 6-entry trace strip (was absent — required even for 0-event components per §6). - Trace strip layout: 'no semantic events' badge + shape/variant + size + color, matches aspect-ratio shape. - Live tab adds the soma + eidos code snippets with full data-uix-code wrappers and head badges (§7 + §8). - somaSnippet now shows the equivalent semantic markup with a clear "not real soma" note (since these are eidos-native). - API tab uses data-uix-table with explicit "Skeleton-specific props" + "Inherited from Box" + "Reference comparison" subsections (§4). - Morfo tab matches §10: header field/value table + Parts table with marker column + per-part data/aria subsection tables. - Sema tab keeps the explicit 0-events explanation (was absent for one of the demos). - Recipe tab uses the Selectors table with morfo/eidos owner tags (§11) instead of a single code snippet. - A11y tab uses data-uix-table (concern/contract) instead of a bullet list, matching aspect-ratio. Reference template: web/routes/uix/components/aspect-ratio/+page.svelte. Per §1, when in doubt, copy from the canary template and adapt. svelte-check: 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	616d8535f7	feat(eidos): add Skeleton and Spinner loader primitives ... Two pure-eidos loader components with morfos at scope `['eidos']` (no soma backing, no semantic events). Skeleton — content placeholder: - 3 shapes: rect (default), circle, text (multi-line with staggered widths) - 5 sizes (xs..xl), 8 color accents - Optional shimmer animation via CSS `background-position` keyframes - Single `<div role="status" aria-busy="true">` with translated aria-label - Reduced-motion freezes animation, keeps visual Spinner — indeterminate progress: - 3 variants: ring (rotating arc), dots (bouncing), bars (stretching) - 5 sizes, 8 colors - Optional inline label via children snippet - `role="status"` + `aria-live="polite"` for SR announcements - Reduced-motion freezes animation, keeps visual Files: - morfo: skeleton.ts, spinner.ts (scope eidos, no events) - eidos: full component + types + css + langs + index per component - langs: skeleton/spinner under componentLangs barrel - demos: canonical 6-tab depth + composition examples (avatar+text card) - layout: sidebar additions under Status group Note: also includes responsive shell additions to web/routes/uix/uix.css that surfaced from an external session — same file, leaving them in. Reference libraries reviewed (Mantine, Chakra v3, Radix Themes, MUI): all expose the same shape/variant/size/color surface. shadcn Skeleton uses the same pulse animation. No surprises in our API. svelte-check: 0 errors in skeleton/spinner files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f8897d92d6	fix: clear remaining `npm run check` errors (12 → 0) ... Three groups of errors blocking the global typecheck: A. Announce morfo used invalid family/intent vocabulary - `absent-clear` event used `family: 'absent'` and `intent: 'absent'`, neither valid in current MorfoEventSemantic schema - Renamed to `commit-reset` (family: commit, verb: reset, intent: neutral) matching SearchField's clear-reset pattern - Updated demo copy to reference the new event name - Cascade-resolved 4 errors (morfo + soma provider + demo + active-uix test) B. Tree wrappers stripped bindable props - eidos `<TreeGrid>` didn't expose `expanded`/`value` as `$bindable`; they leaked through `...rest` and Svelte rejected `bind:expanded` - Same issue for `<TreeView>` with `expandedValue`/`selectedValue` - Now declared explicitly + forwarded via `bind:` to soma's Provider C. Virtual containers passed wide `style` to native markup - `style` was typed `string | Record<string, unknown> | null | undefined` but the markup `<div style={...}>` only accepts string - Filtered with `typeof style === 'string'` derived guard before render svelte-check result: 5076 files, 0 errors, 23 warnings (no-op warnings in navigation-menu `href="#"` and table `state_referenced_locally`). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	940e94bb64	Build TextArea component + fix locale propagation bug across soma providers ... Major work in this session: 1. NumberField demo refactored to expose Intl.NumberFormatOptions live - 9 canonical presets (currency/unit/percent/compact/plain) - Locale/currency/unit lists derived from $libs/langs, $libs/currency, $format/units (no more hardcoded arrays) - Default locale from uix.format.numbers.getLocale() 2. Bug fix: locale prop ignored when soma.format service is active - soma/NumberField: 5 bypass points via new `hasOwnLocale` getter (decimalSeparator, groupSeparator, formatValue, formatEditValue, parseValue) - soma/Calendar: dateOrder respects locale prop (matches DateField precedence) - soma/RangeCalendar: same dateOrder fix - When the consumer passes `locale` prop, soma.nums/dates is bypassed and Intl is used directly with the prop locale 3. TextArea — new component, full 4-layer stack - morfo: 3 parts (provider/input/count), 3 events (commit-input/commit-submit/shift-count-overflow), APG textbox - soma: TextAreaProvider with autosize (scrollHeight measurement), submitOn modes (false|enter|shift+enter|mod+enter), maxLength soft clamp, Field integration (OR-merge), counter overflow tracking - eidos: 5 sizes × 3 variants × 8 colors, autosize suppresses CSS resize - sema: commit-submit + shift-count-overflow perceptual cues - demo: canonical 6-tab depth, all props exposed as live controls - PrimitiveTextareaAttributes added to soma/types/html.ts 4. Also includes accumulated unreleased work from prior sessions: - Eidos ports: announce, clipboard, drag-drop, feed, table, tree-grid, tree-view, virtual-grid, virtual-list, words - Their canonical demos under web/routes/uix/components/ - Semantic events defined for utility morfos (announce/clipboard/virtual-list/virtual-grid) - Tree indent guides fixed (TreeView ::before, TreeGrid stacked gradients) - Sidebar reorganized with Data + Utilities groups - Eidos words content layer and primitives Reference library survey performed before TextArea API design (Mantine, Radix Themes, Chakra v3, React Aria, Ark UI, Bits UI, shadcn, MUI, Prime). Decision documented: no separate CurrencyField/UnitField — single NumberField with formatOptions is the canon (matches all surveyed headless libs except PrimeReact's mode enum, which still uses 1 component). svelte-check: 0 errors in modified/created files. See CONTINUE.md for full session notes and next steps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	3fc4ced37b	feat(carousel): showIndicators + showControls visibility props ... Two new eidos-level booleans on `<Carousel>` so consumers can toggle the indicator dots and the prev/next triggers without touching the markup composition. Defaults stay `true` (existing behaviour). The consumer still renders the parts in markup; the recipe just hides them via `display: none` when the eidos root stamps `data-hide-indicators` / `data-hide-controls`. Toggling on/off doesn't unmount the DOM, so ARIA focus is preserved across the change and the layout doesn't reflow into a different size. Naming follows the canonical eidos cascade — `showIndicators` mirrors calendar's `showWeekNumbers`. Mantine uses `withIndicators` (default false); we default `true` because the Eidos recipe assumes indicators are part of the default surface. Demo: two switches added to the eidos visual-props section + snippet preview emits the prop when set to false. Verified: clicking the demo switch flips `data-hide-indicators` on the root and the indicator-group's computed `display` goes from default to `none` without remounting. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	92c5e421c9	fix(carousel): :active press feedback was replacing centering transform ... Bug behind the user's "el botón se desplaza en el eje contrario al orientation" report. The Button recipe sets [data-button]:active { transform: translateY(1px); } on press to simulate a physical button push. Carousel prev/next triggers absolute-position via: [data-carousel-prev-trigger] { transform: translateY(-50%); } (horiz) [data-carousel][data-orientation='vertical'] [data-carousel-prev-trigger] { transform: translateX(-50%); } (vert) CSS `transform` is a single property — Button's :active value REPLACES the carousel's centering transform, so on press the trigger jumped off its anchor: in horizontal it lost vertical centering, in vertical it lost horizontal centering AND moved 1px down (wrong axis relative to slide travel). Override `:active` on the carousel triggers to compose both transforms on the appropriate axis: horizontal: translateY(calc(-50% + 1px)) vertical: translateX(calc(-50% + 1px)) Now press feedback shifts the trigger 1px along the centering axis without breaking the absolute anchor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8cf2fe813f	fix(button): icon wrappers must not capture pointer (carousel triggers dead-clicked) ... Real cause behind the persistent "los clicks fallan" report. The button recipe gave `pointer-events: none` to nothing — so when a user clicked near the visual centre of an `iconOnly` button (like the carousel prev/next triggers), the SVG `<path>` was the hit target. SVG paths default to `pointer-events: visiblePainted` so only the painted stroke (the thin chevron line) is clickable; clicks landing in the empty diagonals of the chevron passed through to whatever was behind the button — usually nothing — and the button's onclick never fired. Adds `pointer-events: none` to the icon wrappers (`.eidos-button-icon`, `[data-button-icon]`) and to any nested decorative svg / `[data-svg]` / `[data-icon]`. Now the entire button rect is the click target. Verified: `elementFromPoint` at the chevron's geometric centre now returns `BUTTON[data-carousel-next-trigger]` instead of `path`, and a click at that point fires the button handler + advances the carousel index 1→2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a81b44b40c	fix(carousel): first-click no-op — viewportSize was stale until ResizeObserver fired ... Real bug behind the persistent "los clicks fallan" report. The `viewportSize` derivation was reading exclusively from the `viewportClient{Width,Height}` $state mirrors, which are populated asynchronously by the ResizeObserver. On first paint (and on the very first click after mount / orientation switch) those mirrors were still `0`. So: translate = -value × slideSize = -1 × (viewportSize / 1) = -1 × 0 = 0 The index DID advance (soma's `value` went 0→1) but the rail stayed at translate=0, so the user saw the active slide unchanged — looked exactly like a dead click. Subsequent clicks accumulated until the observer finally fired and the carousel suddenly jumped to whatever index had become. Fix: two-tier read in the `viewportSize` derivation. Prefer the observer-tracked mirror when non-zero (steady state, picks up reshape); fall back to a synchronous `vp.clientWidth` / `clientHeight` read while the mirror is still 0. Same derivation reactivity, no extra effects. Verified: first click after page load now lands `translate3d(-380px, 0, 0)` on a 380px-wide viewport (idx 0→1) — was 0 / no movement before. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	b1b1e39dc0	fix(carousel): chevron direction follows orientation ... Vertical carousel still rendered horizontal chevrons (< / >) for the prev / next triggers, which read as wrong-direction even though the click handlers worked correctly. The user complaint "varios clicks" was the visual mismatch making each click look like it did nothing — value WAS advancing index 0→1→2 on each click but the icons pointed sideways in a vertical rail. - Added `orientation` to the eidos carousel context so the prev / next trigger wrappers can pick the right chevron without passing props. - Re-exported `Direction` + `Orientation` from soma's carousel module so the eidos context can type-check them. - Prev trigger now uses `direction='up'` in vertical, `'left'` in horizontal. Next trigger mirrors with `'down'` / `'right'`. Verified: index goes 0→1→2 on successive clicks; chevrons now show `^` (top) and `v` (bottom) in vertical orientation. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a6baae0cf1	fix(carousel/range-calendar/time-range-field): apply canonical i18n + vertical layout patterns ... ## Vertical carousel layout Recipe was making the indicator group stretch full width (380px) because the root stayed in `flex-direction: column` and the indicator-group inherited `align-items: stretch`. Reshaped: - `[data-carousel][data-orientation='vertical']` now flips the root to `flex-direction: row` so viewport and indicator-group sit side-by-side. - Viewport takes `flex: 1 1 auto` of the inline axis with explicit 100% block-size. - Indicator-group becomes `flex: 0 0 auto; inline-size: max-content; align-self: center` — narrow column of dots on the right edge. Active vertical-stretched indicator already had `block-size: 2.25×` treatment from the prior commit, so it now appears as a vertical pill inside the dot column. ## i18n controls: follow canonical pattern Mirrored the date-range-picker / calendar demos verbatim — those are the canon and the new demos drifted from them. Three corrections: 1. **Locale**: `<select>` with `en-US / es-ES / fr-FR` (the docs canon — chip rows and made-up locale lists like ar/he/ja were both inventions). Carousel exposes locale too; it's forwarded to soma for downstream lang-aware behavior (announcer text, future label formatting hooks). 2. **Direction**: chip row with `ltr / rtl` (no `auto`). Label is "direction" not "dir". 3. **State shape**: plain `let dir = $state<Direction>('ltr')`, not the synthetic `dirCtl + derived` pattern I had invented. Applied across all three demos so they read identically to the canon. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	23ad9351ea	feat(carousel): wire dir + locale (was hardcoded 'ltr'); expose i18n in demos ... Audit caught Carousel ignored direction entirely: `getDirectionalKeys` received a hardcoded `'ltr'` so ArrowLeft / ArrowRight had the same semantics under RTL as LTR, and the horizontal translate had no RTL flip so slides advanced the wrong way visually. Drag direction had the same bug. ## Soma - New `dir` + `locale` props on `Carousel.Provider` (fall back to `soma.prefs.getDir()` then `'ltr'`). - `onkeydown` now reads `this.opts.dir.current` for `getDirectionalKeys`. - `itemGroupTransform` flips the translate sign on horizontal RTL so index N→N+1 moves the rail in the reading-direction-appropriate way. - `finishDrag` swaps the offset sign on horizontal RTL so drag-right advances under RTL (drag-left under LTR). - Root stamps `dir="..."`, `lang="..."`, and `data-dir="..."` for consumers and the recipe. - Test mocks updated. ## Demos - Carousel demo: new `soma · i18n` controls section — `dir` chips (`auto` / `ltr` / `rtl`) + `locale` chips covering en/es/ar/he/ja so the user can flip orientation semantics live. - Range-calendar demo: same `dir` + `locale` chip rows added next to `weekStartsOn`; previously only `locale` was state-bound but the control wasn't surfaced and `dir` wasn't forwarded at all. - The eidos code snippet preview emits `dir="..."` and `locale="..."` attrs when they differ from defaults. ## Verified Browser walk: with `dir="rtl"`, the carousel root reports `data-dir="rtl"`, prev/next chevrons swap sides, indicator order mirrors, and `ArrowRight` correctly advances to the *previous* slide (index 1 → 0). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f291c08865	fix(carousel/range-calendar/time-range-field): visual bugs across all three ... Real visual audit caught three classes of bugs that the prior commits missed because they were never opened in the browser. ## Carousel ### Vertical orientation overflow Recipe gave the root no block-size in vertical, so items spilled. Plus the soma `viewportSize` derivation only ran on ref / orientation-prop changes, not on layout reshape — so flipping horizontal → vertical kept reading the old clientWidth and the translate maths used the wrong slide size (observed -214 instead of -156 after a flip). Fix: - Recipe: `[data-carousel][data-orientation='vertical']` gets explicit `block-size`, and the viewport / item-group / item each get `100%` along the block axis. Default vertical size lives on `--_carousel-vertical-block-size` (16rem), overridable via the new eidos `verticalBlockSize` prop or the custom property directly. - Soma: replaced the synchronous `clientWidth/Height` reads with `viewportClientWidth/Height` `$state` mirrors populated by a ResizeObserver on the viewport. Layout-only changes (orientation flip, container resize, font scaling) now propagate to translate calc on the next reactive tick. ## RangeCalendar ### Multi-month stacked vertically `numberOfMonths > 1` rendered grids stacked in a column because the eidos `[data-range-calendar]` recipe is `inline-flex; column`. Copied the side-by-side grid layout from the existing date-range-picker demo: `.range-months { display: grid; grid-auto-flow: column; }` with `grid-auto-flow: row` collapse for `data-month-count='1'`. ### Min/max controls were nonsense The prior demo had a custom "today | custom" mode that conflated fixtures with real today, and required two separate enum states. Rewrote the controls to mirror the date-range-picker demo exactly: two `<input type="date">` bindings on string state, parsed by `parseDateInput`, plus a preset chip row (none / min only / max only / window / invalid). ### Weekday key duplicate The narrow-format weekday strings repeat letters ('T' for Tuesday and Thursday, 'S' for Saturday and Sunday), so keying by `wd` raised `each_key_duplicate`. Changed to key by index. ## TimeRangeField ### Start endpoint rendered no segments Keying the segments `#each` by `seg.part` collapsed when segment parts repeat. Copied the canonical key shape from the time-range-picker demo: `(${part}-${i})`. Verified both endpoints now render their four segments (`09:30` — `17:45` for the default fixture). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	44514c3cc1	fix(carousel): vertical overflow + close gaps vs embla/ark-ui/mantine ... Real reference audit walked the published embla `.d.ts`, Mantine docs, ark-ui, shadcn-svelte and Swiper. Found three classes of gaps in the initial port (a) the vertical bug breaking the only non-default orientation, (b) layout primitives every other lib ships (slidesPerView, slidesToScroll, align, gap), (c) autoplay granularity (playOnInit, stopOnInteraction, stopOnFocusIn, stopOnMouseEnter, stopOnLastSnap), plus an imperative API every consumer needs. ## Vertical bug fix Recipe now gives the root a default `block-size` in vertical orientation (`16rem`, overridable via `--_carousel-vertical-block-size` or the new eidos `verticalBlockSize` prop) and stretches the viewport to fill it. Without this the viewport collapses to content height and items spill. ## Soma extensions - `defaultValue` (uncontrolled init) - `slidesPerView` (1+) — each Item basis = (100% − gap·(n−1)) / n - `slidesToScroll` (1+) — paged group navigation - `align: 'start' | 'center' | 'end'` — viewport alignment - `gap: string` (CSS length) — between-slide spacing on the ItemGroup - `playOnInit` — start autoplay on mount (default true) - `stopOnInteraction` — latch-stop after user clicks prev/next/indicator or drags - `stopOnFocusIn` — pause while focus is inside (default true) - `stopOnMouseEnter` — pause while cursor over root (Embla parity) - `stopOnLastSnap` — latch-stop at last snap when loop=false - Snippet exposes `isPlaying` + an `api` handle with `scrollNext / scrollPrev / scrollTo / play / pause / reset` `commit()` now respects `slidesPerView` (last snap = count − spv). `next()` / `prev()` step by `slidesToScroll`. Translate calc derives from `slideSize = viewportSize / slidesPerView` so multi-view works. Item flex-basis adapts to slidesPerView + gap. ## Eidos additions - `verticalBlockSize` prop — forwarded as CSS custom property for the vertical recipe override - Recipe selectors for vertical orientation enforcing the block-size + viewport stretch - Style composition so consumers can still pass inline `style` ## Demo Live tab now has 4 organized sections (layout / drag / autoplay / imperative API) covering every new prop. The imperative API row drives the carousel from external buttons via the snippet handle so consumers see the pattern in action. `verticalBlockSize` slider exercises the vertical fix. Snippet preview emits every set prop. ## Reference comparison Following the canon's mandate to compare with references BEFORE declaring done, the actual feature matrix from embla published `.d.ts`, Mantine docs, ark-ui, shadcn-svelte, Swiper: | Feature | embla | mantine | ark | swiper | UIX | |------------------------|-------|---------|-----|--------|-----| | Index nav | ✓ | ✓ | ✓ | ✓ | ✓ | | Loop | ✓ | ✓ | ✓ | ✓ | ✓ | | Drag | ✓ | ✓ | ✓ | ✓ | ✓ | | Autoplay | plug | plug | ✓ | ✓ | ✓ | | Orientation H/V | ✓ | ✓ | ✓ | ✓ | ✓ | | slidesPerView | indir | ✓ | ✓ | ✓ | ✓ | | slidesToScroll | ✓ | ✓ | ✓ | ✓ | ✓ | | Align | ✓ | indir | per | ✓ | ✓ | | Gap | css | ✓ | ✓ | ✓ | ✓ | | defaultValue | startIndex | ✓ | ✓ | ✓ | ✓ | | playOnInit | ✓ | indir | ✓ | ✓ | ✓ | | stopOnInteraction | ✓ | ✓ | ✓ | ✓ | ✓ | | stopOnFocusIn | ✓ | ✓ | ✓ | partl | ✓ | | stopOnMouseEnter | ✓ | ✓ | ✓ | ✓ | ✓ | | stopOnLastSnap | ✓ | ✓ | ✗ | ✓ | ✓ | | Imperative API | ✓ | ✓ | ✓ | ✓ | ✓ | | Indicators / triggers | DIY | ✓ | ✓ | ✓ | ✓ | | Fade effect | plug | plug | ✗ | ✓ | ✗ deferred | | Virtual slides | ✗ | ✗ | ✗ | ✓ | ✗ deferred | | Multirow grid | ✗ | ✗ | ✗ | ✓ | ✗ deferred | Deferred power-user features (fade, virtual, multirow grid, cube/cards, parallax) are documented as power-user in the reference audit, not table-stakes, and would require Embla-class internals to ship. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	2cecc0b3b7	feat(eidos): port range-calendar from soma + extract shared partial ... Standalone eidos `<RangeCalendar>` wrapper over the soma range-calendar primitive. Adds size / variant / color cascades; otherwise pass-through 14 compound parts (Provider, Header, Heading, PrevButton, NextButton, MonthSelect, YearSelect, Grid, GridHead, GridBody, GridRow, HeadCell, Cell, Day). ## Feature comparison | Feature | bits-ui | ark-ui | react-aria | Eidos | |----------------------|---------|--------|------------|-------| | Range start/end | ✓ | ✓ | ✓ | ✓ | | Hover preview state | ✓ | ✓ | ✓ | ✓ | | minDays / maxDays | — | — | ✓ | ✓ | | allowSingleDay | ✓ | ✓ | ✓ | ✓ | | preventDeselect | ✓ | ✓ | — | ✓ | | Multi-month display | ✓ | ✓ | ✓ | ✓ | | Week-number column | — | — | ✓ | ✓ | | Month/Year selects | — | ✓ | — | ✓ | | Disabled / readonly | ✓ | ✓ | ✓ | ✓ | | isDateUnavailable | ✓ | ✓ | ✓ | ✓ | | Holiday markers | — | — | — | ✓ | | Locale / dir | ✓ | ✓ | ✓ | ✓ | | Size cascade | — | — | — | ✓ 4 | | Variant cascade | — | — | — | ✓ 3 | | Color cascade | — | — | — | ✓ 8 | ## Range-cells partial extracted The recipe at `src/uix/eidos/components/range-calendar/range-calendar.css` now owns ALL `[data-range-calendar-*]` selectors — the shared rules that previously lived inside `date-range-picker.css` (lines 537-834) moved here. Both consumers (the standalone `<RangeCalendar>` and `<DateRangePicker>`'s popover content) stamp the same data-attrs, so the same selectors paint without duplication. `date-range-picker.css` drops 298 lines of duplication; it keeps only the picker-specific scope overrides (`[data-date-range-picker-calendar]` with no chrome, max-content sizing, transparent bg). ## Morfo Extended `rangeCalendarMorfo.scope` to include `'eidos'` so the new wrapper appears in the eidos-layer inventory and the demo Morfo tab declares it correctly. ## Demo Canonical 6-tab depth (~600L) at `/uix/components/range-calendar`. Live tab exposes every range-specific prop: minDays / maxDays sliders, allowSingleDay, preventDeselect, numberOfMonths chips (1 / 2 / 3), pagedNavigation, fixedWeeks, showWeekNumbers, disableDaysOutsideMonth, weekStartsOn, disabled, readonly, locale, plus size / variant / color cascades. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	68670b6331	feat(eidos): port carousel from soma ... Eidos wrapper for the soma Carousel primitive — horizontally or vertically scrollable rail of slides with keyboard, button, indicator, drag and autoplay nav. Soma owns the index + autoplay timer + gesture; eidos adds size/variant/color cascades and renders prev/next triggers as `<Button iconOnly variant="ghost" rounded="full">` per the canonical Button consumer pattern. ## Feature comparison | Feature | embla | Mantine | ark-ui | Eidos | |----------------------|-------|---------|--------|-------| | Index nav | ✓ | ✓ | ✓ | ✓ | | Loop | ✓ | ✓ | ✓ | ✓ | | Drag / scrub | ✓ | — | ✓ | ✓ | | Autoplay | plugin| ✓ | ✓ | ✓ | | Pause on hover | plugin| ✓ | ✓ | ✓ | | Orientation V/H | ✓ | ✓ | ✓ | ✓ | | Keyboard nav | ✓ | ✓ | ✓ | ✓ | | Indicators | — | ✓ | ✓ | ✓ | | Prev/Next triggers | — | ✓ | ✓ | ✓ | | Size cascade | — | — | — | ✓ 5 | | Variant cascade | — | — | — | ✓ 3 | | Color cascade | — | — | — | ✓ 8 | | Multi-slides view | ✓ | ✓ | — | deferred | | Lazy-mount slides | plugin| — | — | deferred | ## Parts (8) Provider · Viewport · ItemGroup · Item · PrevTrigger · NextTrigger · IndicatorGroup · Indicator. PrevTrigger and NextTrigger render Button via the soma `child` snippet (canonical Button consumer pattern). Default chrome: `iconOnly variant='ghost' rounded='full'` + chevron glyph. Size cascades from Carousel root; consumers can override every Button visual prop inline. Passing `child` bypasses Button entirely. ## Recipe Card chrome around the rail (`variant='surface'`), absolute-positioned triggers over the viewport edges (vertical flips to top/bottom). Active indicator stretches inline-size 2.25× for clearer current-position hint. 8 ColorRole accents. ## Demo Canonical 6-tab depth (~470L): Live / API / Morfo / Sema / Recipe / A11y. Live controls cover all soma props (orientation, loop, dragEnabled, autoplay + delay slider, pauseOnHover, disabled) and all eidos props (variant, size, color). 4 colored placeholder slides for visual contrast. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	db21767db1	feat(eidos): port time-range-field from soma ... Eidos wrapper for time range selection — start/end TimeField inputs sharing a single ZonedDateTime range value. Mirrors DateRangeField pattern with `data-time-field` overlay trick so item segments inherit the time-field recipe. ## Feature comparison | Feature | react-aria | Mantine | Eidos | |----------------------|------------|---------|-------| | Range value | ✓ | ✓ | ✓ | | Per-endpoint Input | ✓ | ✓ | ✓ | | Segment editing | ✓ | — | ✓ | | Granularity prop | ✓ | ✓ | ✓ | | Hour cycle (12/24) | ✓ | ✓ | ✓ | | Min/max value | ✓ | ✓ | ✓ | | Placeholder per-end | ✓ | — | ✓ | | Invalid signalling | ✓ | ✓ | ✓ | | Disabled / readOnly | ✓ | ✓ | ✓ | | Form integration | ✓ | ✓ | ✓ | | Size cascade | — | ✓ | ✓ xs–xl | | Variant cascade | — | ✓ | ✓ 3 | | Color cascade | — | — | ✓ 6 | ## Parts Root · Label · Input (type='start' | 'end') · Segment (re-exported from TimeField). Each Input scopes its own TimeField context so segment editing routes to the correct endpoint. ## Recipe Grid `1fr · auto · 1fr` with em-dash separator. Specificity bump on `[data-time-range-field][data-time-field]` to win over the overlay data-time-field rules. ## Demo Canonical 6-tab depth (~530L): Live / API / Morfo / Sema / Recipe / A11y. Variant / size / color / granularity / hour-cycle / min-max / disabled / readOnly / required controls. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	67726cb6f3	fix(soma navigation-menu): suppress click-close right after hover-open ... Bug: hovering a NavigationMenu trigger opens its Content after the configured \`openDelay\` (default 200ms). If the user then clicked the trigger — naturally, after the open is visible — the click handler saw \`isOpen=true\` and called \`closeNow()\`, shutting the menu the user just opened. Net effect: the first click appears to open AND close the menu in one go. Repro (commit before fix): - hover for ≥200ms (or any delay long enough to trigger \`scheduleOpen\`) - menu opens - click the trigger - menu closes within milliseconds Fix: track \`lastOpenedAt\` per NavigationMenuTriggerProvider via a root \`\$effect\` that stamps the timestamp whenever \`isOpen\` transitions to true (regardless of whether the open came from hover, click, or keyboard). The click handler checks \`Date.now() - lastOpenedAt < 250\` and silently ignores the close-toggle in that window — treating the click as "commit the open" intent, not "toggle shut". Two-click toggle behavior is preserved: a click ≥250ms after the open still closes the menu (verified: openBefore=true, stillOpenAfterClick= true, closedAfter2ndClick=true). The 250ms threshold is slightly above the default openDelay (200ms) so the protection covers the typical hover-then-click sequence without making the toggle feel sluggish. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a010f8f255	fix(eidos navigation-menu): style sub-items inside Content ... Bug: anchors inside Content panels had no hover/padding/border treatment — consumers writing typical mega-menu markup (<a> elements) got a wall of unstyled text. Adds a default sub-item recipe that targets \`[data-navigation-menu-content] :is(a, [data-navigation-menu-link])\` — covers both plain anchors AND the official \`NavigationMenu.Link\` part when used inside Content. Each item gets: - display: block - padding 8px / 12px - border-radius (matches md radius) - color = primary content - text-decoration: none, cursor: pointer - hover/focus background = --color-primary-element - aria-current="page" + data-active = same tinted active state Demo cleanup: dropped the redundant inline \`style="color: inherit; text-decoration: none;"\` overrides on every <a>, tightened the grid gap from space-3 to space-1 (rows now have their own background hover so gap can shrink). Content panel padding reduced to space-2 (was space-4) because sub-items already provide their own padding. Verified in browser: items render with padding 8/12px, border-radius 6px, text-decoration: none, cursor: pointer. Hover changes the background to primary-element. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	fd34fa535c	fix(eidos navigation-menu): Content floats as popover, not inline ... Bug: Content panels were rendering inline below their Triggers, pushing the bar's flex layout. They should float anchored to the Item the same way Radix / bits-ui mega-menus do. Two changes: 1. **Item** — was `flex-direction: column`, which made Content stack below Trigger in the flex flow. Switched to inline-flex with `align-items: center`. `position: relative` stays so it remains the anchor element. Vertical orientation gets `display: flex`. 2. **Content** — added `position: absolute; inset-block-start: calc(100% + var(--space-1)); inset-inline-start: 0; z-index: 50`. The panel now sits 4px below the trigger row, left-aligned to the Item (extends via `min-inline-size: 14rem` past the trigger), and stacks above the rest of the page. Vertical orientation flips the anchor: `inset-block-start: 0; inset-inline-start: calc(100% + var(--space-1))` so the panel opens to the right of the trigger column. Verified in browser: contentTop=623, triggerBottom=619, position=absolute, z-index=50, bar layout no longer pushed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	065cc6a369	feat(eidos): port GridList (selectable list w/ interactive row children) ... Closes #133. Eidos wrapper + types + recipe + canonical-depth demo. 4 parts: Provider, Row, Cell, SelectionCheckbox. Soma owns selection (none/single/multiple), 2D keyboard nav (Up/Down rows + Left/Right cells), Shift/Ctrl range/toggle, Ctrl+A select-all, Escape-clear, typeahead, hidden form input, Field merge. Eidos adds variant + size + color + defaultValue (uncontrolled init). Reference parity (no air baseline): | Feature | soma | react-aria GridList | this port | |---|---|---|---| | selectionMode none/single/multiple | ✓ | ✓ | ✓ | | bind:value (controlled) | ✓ | ✓ | ✓ | | defaultValue (uncontrolled init) | ✗ | ✓ | ✓ added (parity with Combobox/Select) | | Item with interactive descendants | ✓ | ✓ | ✓ | | 2D keyboard nav (Up/Down rows, L/R cells) | ✓ | ✓ | ✓ | | Shift/Ctrl range/toggle | ✓ | ✓ | ✓ | | Ctrl+A select-all (multiple) | ✓ | ✓ | ✓ | | Escape-clear | ✓ | ✓ | ✓ | | Typeahead | ✓ | ✓ | ✓ | | ARIA grid/row/gridcell | ✓ | ✓ | ✓ | | Field merge (disabled/invalid/required/readonly) | ✓ | ✗ | ✓ | | Form participation (hidden input) | ✓ | ✗ | ✓ | | Drag-to-reorder | ✗ | ✓ | ⚠ deferred (compose w/ future DragDrop) | | onAction (row click → navigate) | ✗ | ✓ | ⚠ deferred (use button/link inside Cell) | | selectionBehavior toggle/replace | ✗ implicit | ✓ | ⚠ deferred | | disabledBehavior 'selection'/'all' | ✗ skip-only | ✓ | ⚠ deferred | | Async / infinite loading | ✗ | ✓ | ⚠ deferred | | Empty state slot | ✗ | ✓ | ⚠ document `data-empty` styling | Naming: keeps soma's part names (Provider, Row, Cell, SelectionCheckbox). react-aria's "GridListItem" maps to `Row`; soma's vocabulary is more precise and consistent with future Table / TreeGrid in the same family. Variant set: - variant: ControlVariant (surface/outline/ghost), default 'surface' - size: xs..xl (5-step, mirrors Combobox/Listbox) - color: ColorRole (primary/secondary/neutral/affirm/fulfill/risk/threat/loss) - block: stretch to container width Disambiguation (in index.ts comment): use GridList for rows with interactive children; use Listbox for atomic text options (ARIA forbids interactive descendants inside role="listbox"); use Select/Combobox for closed-picker patterns; use Table for tabular data with columns + sort. Visual reuse: - SelectionCheckbox uses the same `mask-image: url(svg-check)` pattern as the shared menu-indicator partial (commit a2709476). Filled accent box → white ✓ on `[data-state='checked']`. - Row hover/highlight tokens mirror Combobox.Item / Listbox.Item so the form-control surface family stays coherent. - Same `max-block-size: min(60vh, 22rem) + overflow-y: auto` scroll contract as Listbox (commit 830025b4). Sidebar entry under Forms (between Listbox and Calendar). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	52627e60bb	feat(eidos): port NavigationMenu (top-level site navigation w/ mega-menus) ... #132. Eidos wrapper + types + recipe + canonical-depth demo. 7 parts: Provider, List, Item, Trigger, Content, Link, Indicator. Soma owns active-item state, hover delays (openDelay/skipDelayDuration/closeDelay), hoverEnabled gate, loop arrow nav, data-motion directional swap, Indicator rect CSS vars. Eidos paints the bar + trigger chrome + Content panel + slide animations. Reference parity (no air baseline — port directly from soma): | Feature | soma | Radix | bits-ui | this port | |---|---|---|---|---| | Provider + List + Item + Trigger + Content + Link + Indicator | ✓ | ✓ | ✓ | ✓ | | Hover open (openDelay/skipDelayDuration/closeDelay) | ✓ | ✓ | ✓ | ✓ | | hoverEnabled (click-only mode) | ✓ | ⚠ | ✓ | ✓ | | orientation horizontal + vertical | ✓ | ✓ | ⚠ | ✓ | | dir / RTL | ✓ | ✓ | ✓ | ✓ | | Indicator CSS vars (x/y/w/h rect) | ✓ | ✗ | ✗ | ✓ | | data-motion directional swap (from-/to-start/end) | ✓ | ✓ | ⚠ | ✓ | | forceMount on Content + Indicator | ✓ | ✓ | ✓ | ✓ | | ARIA <nav> + translated aria-label | ✓ | ⚠ | ⚠ | ✓ | | Keyboard nav (Arrow/Home/End/Enter/Space/Esc, ArrowDown → Content) | ✓ | ✓ | ✓ | ✓ | | Sub (nested viewports) | ✗ | ✓ | ✓ | ⚠ deferred (matches soma) | | Viewport (shared swap pane) | ✗ | ✓ | ✓ | ⚠ deferred | | Modal variant (focus trap) | ✗ | ✓ | ✗ | ⚠ deferred | | SafePolygon hover bridge | ✗ | ✗ | ✗ | ⚠ deferred | Naming: matches soma's part names exactly. Both Trigger (button) and Link (anchor) stay native — NOT routed through <Button> — because top-nav has flat/borderless chrome distinct from action buttons. The Link automatically picks up `aria-current="page"` styling for the active route. Variant set: only `size: 'sm' | 'md' | 'lg'` (no xs/xl). No variant/color — NavigationMenu is chrome surface, not actionable intent. Fresh recipe — does NOT reuse dropdown-menu (floating click-driven) or menubar (roving tabindex bar). NavigationMenu lives inline in the page; per-item Content panels render via Floating but conceptually attach to the bar. Indicator is a 2px underline that slides via CSS vars (--navigation-menu-indicator-{x,y,w,h}) written by soma. Trigger chevron rotates on [data-state='open']. Content animates via data-motion directional slide on sibling swap. Sidebar entry added under Navigation (between Pagination and a future NavigationMenu entry). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	830025b4ad	fix(eidos listbox): add max-block-size + overflow-y auto ... The Listbox container grew unbounded when items overflowed — long lists just stretched the parent layout. Adds: - Default `max-block-size: min(60vh, 22rem)` via `--_listbox-max-height` token (consumer can override via inline style). - `overflow-y: auto` + `overscroll-behavior: contain` so the listbox becomes its own scroll context. - Horizontal orientation switches axes: removes the block cap and uses `overflow-x: auto` instead so a single-row list never clips. Verified: with 8 items at md size, container caps at 352px with scrollHeight 378px — scrollbar present and working. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	80b21f63ba	feat(eidos): port Listbox (embedded selection list) ... #131. Eidos wrapper + types + recipe + canonical-depth demo. Soma owns single/multi selection (value as string[]), roving-tabindex keyboard nav (Arrow + Home/End + typeahead + Ctrl+A), Field-merged flags (disabled/readonly/required/invalid), hidden form inputs. Eidos adds the visual surface and exposes variant + size + color. Reference parity (no air baseline — port directly from soma): | Feature | soma | react-aria | Headless UI | bits-ui | this port | |---|---|---|---|---|---| | Single + multiple selection | ✓ | ✓ | ✓ | ✓ | ✓ | | bind:value (controlled) | ✓ | ✓ | ✓ | ✓ | ✓ | | Typeahead + Arrow / Home / End | ✓ | ✓ | ✓ | ✓ | ✓ | | Loop nav | ✓ | ✗ | ✗ | ✗ | ✓ | | Section / Group + label | ✓ | ✓ | ✗ | ✓ | ✓ | | Ctrl+A select-all (multi) | ✓ | ✓ | ✗ | ✗ | ✓ | | Form participation (hidden inputs) | ✓ | ✗ | ✓ | ✗ | ✓ | | Field.Provider merge (disabled/invalid/…) | ✓ | ✗ | ✗ | ✗ | ✓ | | Horizontal orientation | ✓ | ✓ | ✓ | ✓ | ✓ | | Item indicator (✓ glyph) | ✓ | ✓ | ✗ | ✓ | ✓ shared partial | | Drag-to-reorder | ✗ | ✓ | ✗ | ✗ | ⚠ deferred | | Async / infinite loading | ✗ | ✓ | ✗ | ✗ | ⚠ deferred | | selectionBehavior (toggle/replace) | ⚠ implicit | ✓ | ✗ | ✓ | ⚠ deferred | | PageUp/Down nav | ✗ | ✓ | ✗ | ✗ | ⚠ deferred | Parts (5): Listbox (Root, replaces soma's Provider name), Item, ItemIndicator, Group, GroupLabel. Variant set: - variant: ControlVariant (`'surface' | 'outline' | 'ghost'`), default 'surface' - size: xs..xl (5-step canonical form-control scale) - color: ColorRole (primary/secondary/neutral/affirm/fulfill/risk/threat/loss) - block: stretch to container width Cross-component reuse: - `ItemIndicator` shares the menu-indicator visual (`a2709476`) — ✓ glyph identical to standalone Checkbox and Dropdown/Context Menu CheckboxItems. CSS-only difference: shown only inside `[data-listbox-item][data-selected]`. - Item row hover / highlight tokens mirror Combobox.Item / Command.Item — the form-control surface family stays coherent. Disambiguation note (in index.ts comment): - Listbox: atomic options, text rows, no inner interactive elements (ARIA forbids interactive descendants inside role="listbox") - GridList: rows with buttons / links / checkboxes inside (2D nav) - Select / Combobox: closed picker surface (Listbox-like dropdown) Gotcha: listbox.svelte and listbox-item.svelte rename `children` to `bodyContent` on destructure to avoid shadowing the inner `{#snippet children}` block (same recursion trap documented in `feedback_button_consumer_pattern.md` Rule 3). Demo: 6 tabs at canonical depth — Live wires all soma + eidos props, all 3 ControlVariant chips, 5 size chips, 8 ColorRole chips, single + multi mode toggle, RTL/horizontal toggle. Sidebar entry added under Forms (between Combobox and Calendar). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8ab8f9dae1	feat(eidos): port Command (⌘K palette) ... Closes #130. Eidos wrapper + 13 part wrappers + 2 new sub-parts + Dialog composition + recipe + canonical-depth demo. Soma owns scoring (`computeFuzzyScore`), keyboard nav (Arrow + vim Ctrl+N/P/J/K + typeahead + loop + grid columns + RTL), item visibility, and the imperative `CommandApi`. Eidos adds size + Item.Icon / Item.Shortcut slots + Dialog composition with optional shortcut binding. Reference parity: | Feature | cmdk | Mantine Spotlight | bits-ui Command | this port | |---|---|---|---|---| | Root provider w/ bind:value, bind:search | ✓ | ✓ | ✓ | ✓ | | Input, List, Viewport, Empty | ✓ | ✓ | ✓ | ✓ | | Group + GroupHeading + GroupItems | ✓ | ✓ | ✓ | ✓ | | Item value, keywords, disabled, onSelect | ✓ | ✓ | ✓ | ✓ | | LinkItem (anchor) | ✗ | ✗ | ✓ | ✓ | | Separator, Loading (progress 0-100) | ✓ | partial | ✓ | ✓ | | Custom filter / shouldFilter | ✓ | ✓ | ✓ | ✓ | | Loop, vim bindings, grid columns | ✓ | partial | ✓ | ✓ | | disablePointerSelection | ✓ | ✗ | ✓ | ✓ | | Modal Dialog composition | ✓ | ✓ (Root is modal) | ✓ | ✓ via eidos Dialog | | Built-in ⌘K shortcut binding | ✗ (BYO) | ✓ | ✗ (BYO) | ✓ optional | | Item.Icon / Item.Shortcut slots | BYO | leftSection/rightSection | BYO | ✓ NEW | Naming: `Command.Root` aliased as the default export (cmdk/bits-ui parity, eidos convention). Inner parts as named sub-properties: `Command.Input`, `Command.List`, `Command.Item`, `Command.Item.Icon`, `Command.Item.Shortcut`, `Command.Dialog`, … Variant set: only `size: 'sm' | 'md' | 'lg'` (drops xs/xl — palette UX needs comfortable hit targets, matches air baseline). Shortcut binding: cross-platform `mod` token (Cmd on macOS, Ctrl elsewhere). Parses `'mod+k'`, `'ctrl+shift+p'`, etc. Window keydown listener registered on mount, cleaned up on unmount. Pass `null`/ undefined to disable. Recipe: `command.css` paints palette container, input row, scrolling List/Viewport, item rows (with highlighted [data-selected] state), icon + shortcut slot layout, group heading, separator, empty state. Loading progress is a 2px bar under Input with `--_command-loading- progress` for the fill. Inside Command.Dialog the panel chrome comes from dialog.css. Demo: 6 tabs (Live/API/Morfo/Sema/Recipe/A11y) — Live wires every soma + eidos prop + Dialog mode with shortcut input. Two stages: inline palette + dialog opener with shortcut hint. Three code snippets (soma, eidos inline, eidos dialog). Gotcha note: command.svelte renames the children prop to `bodyContent` on destructure to avoid shadowing the inner `{#snippet children}` — same infinite-recursion trap noted in `feedback_button_consumer_pattern.md`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9def877dbd	feat(eidos): port Menubar (desktop File/Edit/View bar) ... #129. Eidos wrapper + types + recipe + canonical-depth demo. Soma owns active-menu state, cross-menu ArrowLeft/Right navigation, hover-switch when active, focus return on Escape, typeahead, RTL. Eidos paints the bar surface and trigger states; per-menu Content reuses the dropdown-menu recipe (Item / Sub / Checkbox / Radio chrome + the shared menu-indicator partial from `a2709476`) because soma already re-exports the DropdownMenu parts for those slots. Reference parity: | Feature | Radix | bits-ui | ark-ui | this port | |---|---|---|---|---| | Root provider w/ active-menu binding | ✓ | ✓ | ✗ (Menu only) | ✓ | | Menu / Trigger / Content | ✓ | ✓ | ✓ | ✓ | | Item / Group / GroupHeading / Separator | ✓ | ✓ | ✓ | ✓ | | CheckboxItem / CheckboxGroup / RadioGroup / RadioItem | ✓ | ✓ | ✓ | ✓ | | Sub / SubTrigger / SubContent | ✓ | ✓ | ✓ | ✓ | | Cross-menu ArrowLeft/Right (with loop) | ✓ | ✓ | n/a | ✓ | | Auto-open on hover when active | ✓ | ✓ | n/a | ✓ | | Typeahead | ✓ | ✓ | ✓ | ✓ | | Arrow part | ✓ | ✓ | ✓ | ⚠ dropped — menubar idiom anchors to bar edge | Parts shipped (15): Provider, Menu, Trigger, Portal, Content, Item, Group, GroupHeading, Separator, Arrow (re-exported), CheckboxItem, CheckboxGroup, RadioGroup, RadioItem, Sub, SubTrigger, SubContent. The inner 12 (Item onwards) are re-exports of the eidos DropdownMenu wrappers so the menu-indicator partial applies automatically — no recipe duplication. Variant set: only `size: 'sm' | 'md' | 'lg'` (xs would crowd triggers, xl unnecessary for a chrome bar). Size cascades from Menubar root to per-menu Content via a Svelte context (`menubar-context.ts`, `getMenubarSizeContext` / `setMenubarSizeContext`). Cross-layer: eidos Menubar reuses eidos DropdownMenu internals — the recipe doesn't redefine Item/Sub/Checkbox/Radio. Menubar.Content stamps `data-size` AND inherits `data-dropdown-menu-content` (soma's MenubarContent specializes DropdownMenuContent), so dropdown-menu.css paints the panel chrome and our menubar.css only declares the bar surface + trigger states. Workaround note: menubar-content.svelte casts rest props through `Record<string, unknown>` to bypass a TS "union too complex" depth limit triggered by soma's inline-augmented MenuContentProps + HTML attribute union. Runtime types are correct. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	0afcabee8b	feat(eidos): port LinkPreview (Radix HoverCard equivalent) ... #128. Eidos wrapper + types + recipe + canonical-depth demo. Trigger renders as `<a>` (navigational anchor); on hover/focus after `openDelay` (default 700ms) the Content panel reveals with SafePolygon bridging trigger and content so the pointer can travel without dismissing. Non-modal, no-op on touch (link follows directly). Reference parity: | Feature | Radix HoverCard | bits-ui LinkPreview | ark-ui HoverCard | this port | |---|---|---|---|---| | open with bind: | ✓ | ✓ | ✓ | ✓ | | openDelay (700ms) / closeDelay (300ms) | ✓ | ✓ | ✓ | ✓ | | disabled | ✗ | ✓ | ✓ | ✓ | | Trigger as `<a>` | ✓ | ✓ | ✗ (`<button>`) | ✓ | | Portal + Arrow | ✓ | ✓ | ✓ | ✓ | | Floating layer (side/align/offsets/collision) | ✓ | ✓ | ✓ | ✓ | | customAnchor | ✗ | ✓ | ✗ | ✓ | | ContentStatic | ✗ | ✓ | ✗ | ⚠ deferred | | lazyMount | ✗ | ✗ | ✓ | ⚠ deferred | Naming choice: `LinkPreview` (matches air + bits-ui), not `HoverCard`. Trigger semantic is navigational anchor — for a button-triggered hover-card use `<Popover>` with `openDelay` or pass `child` snippet to bypass the default `<a>`. Variant set: only `size: 'xs'..'xl'` (no ControlVariant — LinkPreview is a surface, not actionable). Defer color/intent per the canon rule that surfaces are uncolored. Parts shipped: Provider, Trigger, Portal, Content, Arrow. Recipe: `link-preview.css` with anchor underline (subtle, intensifies on hover/open), content panel chrome (border + surface bg + shadow), arrow fill matching panel bg, slide+fade entrance per `data-side`, reduced-motion skip. Demo: 6 tabs (Live/API/Morfo/Sema/Recipe/A11y) at canonical depth per DEMO_AUTHORING_GUIDE — Live wires every Provider+Content prop with the right chip set, eidos+soma snippets generated, all 6 ARIA contract rows + keyboard + pointer tables in A11y tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	0b55be5c36	refactor(combobox + search-field): ClearButton/Clear render <Button> ... Closes #120. The two icon-only clear affordances now render as eidos `<Button>` via soma's `child` snippet, retiring the per-recipe chrome (border, padding, focus ring, hover, dimensions) in favour of button.css. The X glyph is provided through Button's `icon` snippet slot; `iconOnly` collapses the body and keeps the label sr-only. Both narrow `variant` to ControlVariant (`'surface' | 'outline' | 'ghost'`) per DEMO_AUTHORING_GUIDE §12.7 — same 3-set as DropdownMenu.Trigger and AlertDialog.Cancel. Default `variant='ghost'` (subtle X that reveals chrome on hover) which is the canonical clear affordance. Defaults: - Combobox.ClearButton: ghost · xs · iconOnly · color=neutral - SearchField.ClearTrigger: ghost · sm · iconOnly · color=neutral Per-component CSS gutted to the empty-state visibility rule only — `[data-…][data-empty] [data-…-clear-…] { opacity: 0; pointer-events: none }` stays because hiding the X when there's nothing to clear is component-specific behavior, not Button chrome. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	32598d7cf3	fix(alert-dialog): narrow Action.variant to canonical SelectionVariant (3) ... Stops the chip-count drift introduced in \`c98510af\`. AlertDialog.Action was exposing all 6 ButtonVariant chips, breaking the 3-chip rhythm the rest of UIX follows. Per DEMO_AUTHORING_GUIDE §12.7 every chip-group must enumerate the full union the type declares — so the fix is to narrow the *type*, not truncate the chips. \`AlertDialogActionVariant = Extract<ButtonVariant, SelectionVariant>\` imports the canonical set from \`eidos/lib/types.ts\` (`solid | outline | ghost`), which is the right shape for a primary action button: - keeps 'solid' as the CTA default - 3-chip parity with Cancel (ControlVariant), DropdownMenu.Trigger (ControlVariant), and the rest of the form-control surface - no invented vocab — uses the existing canon set named for exactly this use case ("selection chips / toggles" semantically maps to "selection / action buttons") Demo array drops from 6 to 3 chips; API row updated to reflect the narrowing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	c6f063dc6a	refactor(alert-dialog): Action/Cancel render <Button>; intent flows via snippet ... #120 second pass. AlertDialog.Action and AlertDialog.Cancel now render eidos `<Button>` internally via soma's `child` snippet, retiring the per-recipe Toggle-token chrome and the CSS ancestor cascade (`[data-dialog-content][data-color='risk'] [data-alert-dialog-action]`). Intent propagation: soma's `AlertDialogActionProvider` exposes a new `dialogIntent` derived getter that reads `DialogProvider.opts.intent`. The Action component passes it to the `child` snippet alongside `props` (via `WithChildNoChildrenSnippetProps` so plain `children` stays a regular Snippet). The eidos Action wrapper forwards it to Button as `intent={intentOverride ?? dialogIntent}` — so `<AlertDialog intent="risk">` automatically paints a red Action without any cascade selector. Defaults: - Action: variant='solid', intent inherits from dialog - Cancel: variant='outline', intent='neutral', color='neutral' so it reads as gray-outlined regardless of the dialog's intent (canonical "this is the safe choice" cue) Cancel narrows variant to ControlVariant (3 chips: surface/outline/ghost) per DEMO_AUTHORING_GUIDE §12.7. Action keeps the full ButtonVariant because it's the primary call-to-action. alert-dialog.css gutted to a doc-only stub; all chrome now comes from button.css. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a2709476f4	style(menu-indicator): align with Checkbox / RadioGroup visual ... Menu CheckboxItem / RadioItem now mirror the standalone Checkbox / RadioGroup chrome: - off: outlined box / circle (transparent fill, neutral border) - on : filled solid accent + white ✓ glyph (checkbox) or white inner dot (radio) — same shape as `<SvgCheck>` and RadioGroup.Indicator The check glyph uses `mask-image` with the same `M5 12.5L10 17.5L19 7` path as `<SvgCheck>` so the menu item reads visually identical to a standalone `<Checkbox checked>`. Background-color carries the glyph colour via `--_menu-indicator-glyph` (`--color-content-on-solid`), matching how Checkbox sets `--_checkbox-palette-text` over the solid accent fill. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago