366 Commits (15dbf0f8fdaa395c4422793551af8be54b221bc5)

Author	SHA1	Message	Date
dev	ef95b1a82a	feat(words): slash command /image + paste/drop with onUploadImage (F3.7, F3.8) ... F3.7 — slash command /image: - DEFAULT_SLASH_COMMANDS gains an 'image' entry: triggers a window prompt for the URL (and optional alt text), then dispatches insertImage. The native prompt is MVP — consumers wanting a custom dialog can hide the slash entry via slashCommands override and call applyWordsCommand({ type: 'insertImage', src }) from their own UI. - WordsSlashCommandId union + WordsCommandName union extended with 'image' / 'insert-image' respectively. - slashCommandToWordsCommand returns undefined for 'image' so the prompt path in commitSlashCommand owns it. F3.8 — paste/drop with onUploadImage callback: - New WordsProps.onUploadImage prop: (file: File) => Promise<{url, alt?}>. Consumer-injected upload pipeline (S3, R2, own backend, etc.). - onpaste detects image files in clipboardData.files. If present + the callback is wired, intercepts the paste (drops text/html processing) and inserts each image with a blob: URL + status='pending'. - New ondragover + ondrop handlers gate on dataTransferHasImageFiles and the callback being set; trigger insertImageFiles on drop. - insertImageFiles inserts pending placeholders, awaits the upload promise for each, then either swaps src for the final URL (success) or flips status='error' (rejection). Matches blocks by blob URL (unique) so concurrent uploads + concurrent edits stay coherent. - replaceImageBlock / markImageBlockError use mapImageBlocksBySrc to rewrite the document via replaceDocument command. No new command type needed. - Helpers added: collectImageFiles, dataTransferHasImageFiles, mapImageBlocksBySrc — all pure functions at module scope. Test fixture: wordsOpts gains the onUploadImage state slot so the 16 existing provider tests typecheck without behavior change. 152/152 tests pass in the full words soma scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	86b47cef25	fix(words): normalize handles image blocks + 3 image tests (F3.11 partial) ... normalizeBlock had no case for type='image' — image blocks coming from parseWordsMarkdown / parseWordsHtml were silently dropped at the default branch. Now: - normalize.ts case 'image': validates src (non-empty + sanitizeWordsUrl), passes through alt / caption / width (numeric) / height (numeric) / align (validated via isWordsImageAlign) / status ('pending' | 'error'). - normalize.ts imports createImage + isWordsImageAlign from the extension. Image-extension cast widened with `as unknown as ErasedFactory` because WordsImageBlock (no `children` field) doesn't satisfy the contract's node shape strictly; the double-cast is the same pattern table-extension already uses for typed factories. 3 new engine tests cover the F3 happy path: - parses a block-level markdown image ( on its own line yields a type:'image' block) - round-trips an image through markdown (serialize → parse → matches) - round-trips an image through HTML (figure>img+figcaption → ImageBlock → serialize back) 85/85 engine tests pass (was 82; +3 image tests). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	2a51adc00f	feat(words): insertImage operation + command + CSS + extension stub (F3.6, F3.9, F3.10) ... F3.6 — insertImage reducer + command: - engine/operations.ts: insertImage(state, options) — atomic insert (URL required, optional alt/caption/width/height/align/status). Replaces an empty paragraph cursor lands on, otherwise inserts after. Caret lands on the new paragraph following the image (image is atomic — no caret inside the figure). - engine/commands.ts: 'insertImage' case added to WordsCommand union + applyWordsCommand switch. Public command surface: provider can call applyWordsCommand(state, { type: 'insertImage', src, alt?, ... }). F3.9 — eidos CSS for image block: - figure[data-words-block='image']: centered flex column with border, bg, padding, gap. - img: max-inline-size 100%, auto height, user-select none. - figcaption: italic, centered, status-color, smaller font. - data-words-image-align='left'/'right': flex alignment + auto margins. - data-words-image-status='pending': opacity + grayscale + "Uploading…" ::after pseudo-text. - data-words-image-status='error': threat border + "Upload failed" ::after pseudo-text. - :focus / :focus-within: 2px accent outline so the atomic block has a visible selection state. F3.10 — imageExtension stub: - extensions/image/image-extension.ts: WordsExtension shape with name='image', nodeTypes=['image'], factories.image=createImage, commandNames.insertImage='insertImage'. Hooks intentionally absent (engine still hardcodes branches today; stub publishes the public shape parallel to tableExtension). - extensions/index.ts exports imageExtension alongside tableExtension. Morfo: - data-block + data-words-node value sets include 'image'. - New optional attrs declared: data-words-image-align (left/center/ right), data-words-image-status (pending/error). Now the eidos CSS selectors validate against the morfo contract. 211/211 tests pass in words soma + morfo scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	08bef77f4b	feat(words): image extension foundation — types, render, HTML+Markdown serializers (F3.1-F3.5) ... Adds image as a first-class block node to the words engine. Phase F3 of the words rich-text editor. Ships the bottom half of the stack so images can be authored in source (markdown / HTML / value JSON) and roundtripped, but UX surfaces (toolbar action, slash command, paste/ drop) land in subsequent commits. F3.1 — extensions/image/{types,factories,index}.ts: - WordsImageBlock = { type: 'image', src, alt?, caption?, width?, height?, align?, status? } - createImage(src, options) factory canonicalising defaults (align='center' stripped, etc.) - WordsImageStatus = 'pending' | 'error' for upload lifecycle - WORDS_IMAGE_ALIGNS + isWordsImageAlign predicate F3.2 — engine/document.ts: - WordsBlockType + WordsBlock union extended with 'image' - Image types re-exported (backward-compat with the table-types pattern) - getBlockText: image → alt text (captions excluded; image stays a single atom in plain-text contexts) F3.3 — engine/render.ts: - Image branch renders <figure data-words-block=image contenteditable=false> <img src alt width? height? loading=lazy draggable=false> <figcaption>caption</figcaption? - WordsRenderTag union gains 'figure' | 'img' | 'figcaption' - data-words-image-align / data-words-image-status surface state - renderBlockPlainText: image → alt F3.4 — engine/serialize-html.ts: - Out: <figure data-words-image-align?><img alt src width? height?><figcaption?></figure> - In: 'figure' added to BLOCK_TAGS; <figure><img> elements parsed back to ImageBlock (with caption from <figcaption>); bare <img> parses to a block too - htmlElementText helper added for caption text extraction F3.5 — engine/serialize-markdown.ts: - Out:  — escapes ], ( and ) in src, " in caption - In: standalone line matching ^$ promotes to a block image. Inline images mid-paragraph become text + no image (lossy by design — keep the model tight; inline image is a separate node type if added later) Engine ripple — exhaustive switches updated: - normalize.getInlineBlockText - path.collectContainerChildren (image marked as terminal) - selection.collectBlockText (image returns empty — opaque atom) - operations: - setBlock skips image (image is not convertible to inline-text blocks) - setTextAlign skips image (no text align on image) - deleteRange refuses if range crosses an image (atomic) - insertParagraph on image inserts a fresh paragraph after it and moves the caret - blockTextAlign() returns undefined for image - words-provider.currentTextAlign returns 'left' on image 149/149 tests pass in the full words soma scope. `npx tsc --noEmit` clean for the touched area. Engine consumers compile unchanged. Next: F3.6 insertImage operation + toolbar/slash command, F3.7 slash menu /image entry, F3.8 paste/drop with onUploadImage callback, F3.9 eidos CSS, F3.10 imageExtension stub, F3.11 demo + verify. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	1043f1de4a	refactor(words): extract 8 pure table helpers to extensions/table/utils.ts (F2.3h.1) ... Moves the table-pure helpers (no engine selection/normalize/marks dependencies) from `engine/operations.ts` to `extensions/table/utils.ts`: - createTableGrid (2×2 default, clamped 1..12 × 1..8) - tableCellPathFromContainer (3-tuple path resolver) - tableOptions / tableCellOptions (option-bag readers) - tableColumnCount (max-cells-across-rows, min 1) - createEmptyTableRow (N-cell row factory) - insertTableCellInRow / deleteTableCellFromRow (cell ops over a row) - WordsTableCellPath type alias The 6 *mixed* helpers (currentTableCellPath, selectTableCell, setTableCellTextAlign, updateCurrentTableCell, updateCurrentTable, preserveTableFormattingSelection) still live in operations.ts — they read private engine state and can only move once F2.3i full lands a visitor pattern that injects those engine APIs as parameters. clampInteger stays duplicated locally in utils.ts (9 LoC, generic numeric helper) instead of being exported from the engine, to keep the extension's surface tight. If a third caller emerges, promote to a shared location. 149/149 tests pass in the full words soma scope. TS check clean in extensions+engine area. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	bde6728590	refactor(words): table extension stub — name + nodeTypes + factories + commandNames (F2.3i) ... Publishes `tableExtension: WordsExtension` in `extensions/table/table-extension.ts` with the three static facets we can ship without touching the engine: - `nodeTypes`: ['table', 'table-row', 'table-cell'] - `factories`: typed constructors for the three node types - `commandNames`: the 12 public table commands (insertTable, deleteTableRow, toggleTableHeaderRow, setTableCellTone, …) mapped to internal operation types (1:1 today). The dynamic hooks (`render`, `normalize`, `serialize`, `path`, `keyboard`, `commands`, `events`) are intentionally absent — F2.3f-h port each one incrementally. The engine does NOT yet consume the registry; the stub publishes the shape the engine will respect once F2.3i full lands. 6 smoke tests verify the public shape (nodeTypes, factories produce valid nodes, registry registers cleanly + finds by every nodeType, all 12 command names exposed, hooks intentionally absent, default 1×1 table). 102/102 in extensions + engine scope, 149/149 in full words soma scope. CONTINUE.md updated to reflect F2.3i-stub done + next-session order (F2.3h first, then F2.3f/g — F2.3i full wire-up follows F2.3h). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d839273536	refactor(words): extract table render to extensions/table (F2.3e) ... Fifth atomic checkpoint of F2.3. Moves the table-specific DOM render helpers from engine/render.ts to extensions/table/render.ts. Moved: - renderTable(block, path, helpers) — replaces the table branch in renderWordsBlock + internal renderWordsTableRow + renderWordsTableCell - renderTablePlainText(block, helpers) — replaces the table branch in renderBlockPlainText The extension defines structural render-element types (TableRenderElement, TableRenderText, TableRenderNode) assignment- compatible with the engine's WordsRenderElement/Node. The engine passes its constants (WORDS_PATH_ATTR, WORDS_NODE_ATTR) + helpers (encodePath, renderInlines, getInlineText) via a TableRenderHelpers object, keeping the extension independent of engine/dom.ts. The engine's renderWordsBlock dispatcher branch for `block.type === 'table'` now delegates to `renderTable(block, path, { ... })` in a single call. ~50 LoC of helper functions removed from the engine. Extension barrel updated to expose: - renderTable / renderTablePlainText - TableRenderElement / TableRenderNode / TableRenderText / TableRenderHelpers / RenderPath types Verification: - 143/143 tests pass in src/uix/soma/components/words - 0 new TypeScript errors F2.3 progress: a + b + c + d + e done. Remaining: f (path), g (normalize), h (operations — largest at ~400-500 LoC), i (registry wire-up), j (verify). Operations remains the heaviest piece — likely its own dedicated session. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	5797e69b88	refactor(words): extract table HTML serializer (F2.3c) ... Fourth atomic checkpoint of F2.3. Moves the HTML pipe-table serialize + parse helpers from engine/serialize-html.ts to extensions/table/serialize-html.ts. Moved (write side): - serializeTableHtml(block, serializeInlines, escapeHtmlAttr) - serializeTableCellHtml (internal) - tableAttrsHtml (internal) - tableCellAttrsHtml (internal) Moved (parse side): - parseTableHtml(node, parseInlines, textAlignFromStyle) - collectTableRows (internal) - htmlRowToWords (internal) - htmlCellToWords (internal) - tableCellVerticalAlignFromNode (internal) - tableCellToneFromNode (internal) Mirrors the F2.3d pattern: extension consumes engine inline serializer + HTML attribute escaper as callback parameters to avoid circular dependencies. The extension defines its own minimal `WordsTableHtmlElement` / `WordsTableHtmlChild` types structurally compatible with the engine's internal HtmlElementNode/HtmlNode — engine passes its own parsed nodes via a safe `as unknown as` cast at the call site (commented). engine/serialize-html.ts now contains only the dispatch call to the extension's serializeTableHtml / parseTableHtml. ~150 LoC of helper code removed from the engine; same LoC + clearer separation in extension. Extension barrel updated to expose: - serializeTableHtml / parseTableHtml - WordsTableHtmlElement / WordsTableHtmlChild types Verification: - 143/143 tests pass in src/uix/soma/components/words - 0 new TypeScript errors F2.3 progress: a + b + c + d done. Remaining: e (render), f (path), g (normalize), h (operations — largest), i (registry wire-up), j (verify). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d6f0af4846	refactor(words): extract table markdown serializer (F2.3d) ... Third atomic checkpoint of F2.3. Moves the markdown pipe-table serialize + parse helpers from engine/serialize-markdown.ts to extensions/table/serialize-markdown.ts: Moved: - serializeTableMarkdown(block, renderInline) - tableMarkdownRow (internal) - escapeMarkdownTableCell (internal) - collectTable(lines, startIndex) - parseTableLine (internal) - isTableSeparator (internal) - NEW: buildTableFromMarkdownRows(rows, parseInline) — convenience for the engine to convert collectTable's raw output into a WordsTableBlock, keeping the extension free from the engine's inline parser implementation. The extension takes inline serialize/parse functions as callback parameters (`renderInline`, `parseInline`) instead of importing the engine's inline serializers. Avoids circular dependency — the extension imports engine for shared types (WordsInline, WordsTableRow) and factories only, never for runtime function dependencies. engine/serialize-markdown.ts now imports the 3 extension functions and calls them from `serializeBlockMarkdown` (write side) and `parseWordsMarkdown` (parse side). Internal `collectTable`, `parseTableLine`, `isTableSeparator` removed. Extension barrel updated to expose the new functions: - serializeTableMarkdown - parseTableMarkdownRows (collectTable re-exported under clearer name) - buildTableFromMarkdownRows Verification: - 143/143 tests pass in src/uix/soma/components/words - 0 new TypeScript errors F2.3 progress: a + b + d done. Pending: c (serialize-html), e (render), f (path), g (normalize), h (operations — largest), i (registry wire-up), j (verify). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	a0afa44da4	refactor(words): extract table factories to extensions/table (F2.3b) ... Second atomic checkpoint of F2.3. Moves table factory functions (createTable, createTableRow, createTableCell), predicate functions (isWordsTableCellVerticalAlign, isWordsTableCellTone), and value-set constants (WORDS_TABLE_CELL_VERTICAL_ALIGNS, WORDS_TABLE_CELL_TONES) from engine/document.ts to extensions/table/factories.ts. engine/document.ts now re-exports the moved symbols so existing imports keep working unchanged. The factories module imports its back-references (createText, WordsInline) from engine/document — the extension may depend on the engine core but the engine core only depends on the extension via re-export indirection (no functional dependency). extensions/table/index.ts barrel updated to expose types (F2.3a) + factories (F2.3b) as the table extension's public surface. Document header notes which pieces have been migrated and which are still pending (serializers, render, path, normalize, operations, registry wire-up). Verification: - 143/143 tests pass in src/uix/soma/components/words - 0 new TypeScript errors - No engine behaviour change (symbol relocation only) F2.3 progress: a + b done. Pending: c (serialize-html), d (serialize-markdown), e (render), f (path), g (normalize), h (operations — largest), i (registry wire-up), j (verify). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	088d31ec5d	refactor(words): extract table types to extensions/table/types.ts (F2.3a) ... First atomic checkpoint of F2.3 (table migration to extension). Moves the type declarations only — interfaces and unions for the table node tree (WordsTableBlock, WordsTableRow, WordsTableCell, WordsTableOptions, WordsTableCellOptions, WordsTableCellVerticalAlign, WordsTableCellTone) go from engine/document.ts to extensions/table/types.ts. engine/document.ts re-exports the moved types via `export type { ... } from '../extensions/table/types'` so every existing consumer keeps compiling without changes. Internal usages within document.ts use a separate `import type` to keep the types in local scope for factory function signatures. The rest of F2.3 (factories + serializers + render + normalize + path + operations + registry wire-up) requires deeper dependency analysis across the engine's ~990 LoC of table code spread over 10 files. That work is deferred to a dedicated session to avoid mid-refactor breakage. Verification: - 143/143 tests pass in src/uix/soma/components/words - 0 new TypeScript errors - No engine behaviour change (types-only move) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
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	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	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	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	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	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	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	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	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	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	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	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	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	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	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