204 Commits (19ce90b04061000067efe5d337b96b93b02541b6)

Author	SHA1	Message	Date
dev	19ce90b040	refactor(sema,eidos): drop 2 orphan @deprecated aliases + translate Spanish comments ... Removed orphan deprecated type aliases with no real consumers: sema `IntentPolicy` (legacy single-axis policy, superseded by intentRequirement + intentGuidance) and its re-export; eidos `RecipeTokenObject` (→ RecipeTokenDeclaration) and the comment that named it. Left `IntentExpectedFamily` and `SemaEventLabel` — both are still consumed by public morfo types / sema functions, so removing them is an API rename, not dead-code cleanup (documented in SYSTEM-AUDIT). Translated 3 non-quote Spanish comments to English (sema/chans/types, sema/projection/index, morfo/year-grid) per the English-comments rule. Book quotes stay in Spanish (they're the canonical source). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	5c18a892a0	docs(soma,morfo): fix dead $lib/util aliases + stale morfo count ... 9 soma component READMEs imported from the removed $lib/util/dias and $lib/util/colors aliases → $libs/days / $libs/color (matches what the code actually imports). morfo/README.md said "All 66 morfos" (real count ~116) → reworded to "Every morfo in the codebase" to drop the brittle number. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	e0579f7e24	feat(eidos): add QrCode — themeable QR with own zero-dep encoder ... Own QR encoder in $libs/qr (ISO/IEC 18004: segment analysis → Reed-Solomon over GF(256) → matrix layout → 8-mask penalty selection), no npm dependency. Eidos <QrCode> renders the module matrix as one SVG path with square/rounded/dots cell shapes; function patterns stay square (via the encoder's `reserved` mask) so every shape scans. Optional logo clears the centre + auto-boosts ECC to H. <QrCode.DownloadTrigger> exports PNG/SVG, baking resolved colours into the clone first (a serialized SVG loses the document's CSS custom properties). Fixed-tone default colours for scannability; themeable via color/background. morfo qr-code (scope: eidos; parts Provider/Pattern/Overlay/ DownloadTrigger) + 'path' added to MorfoElement; recipe with 11 --qr-code-* tokens; canonical demo + nav entry. 11 encoder unit tests; verified end-to-end via jsQR round-trip + browser. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	f59396b51a	feat(uix): RadioCards — card-style single-select reusing RadioGroup ... New eidos component built ON TOP of RadioGroup with zero duplicated behaviour. RadioCards reuses RadioGroup's soma wholesale (selection, roving focus, role=radio, native <form> via HiddenInput) and adds only the card chrome: icon · title · description + an always-present corner radio. Vertical, horizontal and grid layouts. - morfo: scope:['eidos'], thin contract for presentation parts only (Provider marker, Item-card, Indicator, Icon, Content, Title, Description). The interactive contract + commit-select stay in radio-group, reused via its soma. No new soma, no new sema. - eidos: `radio-cards` recipe (card chrome) + wrappers + radio-cards.css. radio-group.css is NOT loaded here, only its foundation tokens — the card owns its visual, reusing --_radio-group-palette-* (inlined, since a :root token referencing the palette is invalid-at-computed-value). - demo: canonical structure (always-on stage + trace, tabs, chip/switch controls, Untitled-UI example patterns) + nav entry + README. check 0 · eidos-lint 0 invalid. Browser-verified: select (click + keyboard roving), disabled, the three layouts, controls drive the preview. Follow-up: icon/circle sizes are still px (mirroring radio-group's own size tokens) — making the control-size scale density-aware is a separate, family-wide change deferred per request. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	7bf5d047c3	refactor(soma): de-dup attrs in 12 providers via renderProps (batch 3) ... Source role/aria/data from the morfo via renderProps() across the collection/menu families, removing the attrs the providers re-declared ("morfo declares, soma executes"). Audit total 369 → 213. Migrated: select, listbox, carousel, tree-view, year-grid, grid-list, tree-grid, table, file-upload, editable, combobox, command. tree-view/table keep their per-node aria hardcoded on purpose: each tree node / table cell computes its own aria-level/selected/rowindex/colindex/ sort, which a single renderProps can't resolve. The residual hits the guard pins are all legit value overrides — computed aria-labels (carousel "slide N", editable/file-upload triggers), per-instance dynamic values, and computed refs (command aria-activedescendant/controls). listbox/grid-list tests: aria booleans the morfo declares via stateRef now resolve through renderProps as "true"/"false" strings (aria-boolean mode) instead of the providers' hardcoded booleans — assert strings. words excluded from this rollout per request (active dev track). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	e1b43cfb53	refactor(soma): de-dup attrs in 11 providers via renderProps (batch 2) ... Source role/aria/data from the morfo via renderProps() across the date/time/calendar/picker families, removing the attrs the providers re-declared ("morfo declares, soma executes"). Audit total 468 → 369. Migrated: field, date-field, time-field, color-picker, date-picker, date-range-picker, time-picker, time-range-picker, calendar, month-grid, range-calendar. date-field/time-field keep the `segment` part hardcoded on purpose: it is multi-archetype (editable segments are spinbuttons, literal separators must NOT be) so a uniform renderProps would inject role into the literals. The residual hits the guard now pins are all legit value overrides: composite aria-labelledby/describedby (input), the deferred segment part, and computed aria-labels (color-picker/calendar include the value/month). field test: required-indicator applies aria-hidden via syncAttrs, so the attr lives on the DOM (not the props object) — assert it via getAttribute. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	96179ce392	refactor(soma): de-dup attrs in 16 providers via renderProps (batch 1) ... Workflow-driven rollout of the morfo↔soma attr de-duplication. 16 providers (textarea, pagination, pin-input, slider, tag-group, scroll-area, form, search-field, drag-drop, stepper, tags-input, color-field, password-field, link-preview, menubar, navigation-menu) now source role/aria/data from the morfo via renderProps() instead of re-declaring them. 3 morfos gained `ariaBoolean` on propRef-valued aria booleans (color-field, form, password-field). Audit: 559 → 468 hits (−91). Provider tests updated to the renderProps shape: ARIA booleans assert the string "true"/"false" (the correct ARIA shape, was a JS boolean), and the few DOM-read assertions for parts that moved off `syncAttrs` now read the props object (pagination). Parts still on `syncAttrs:true` keep their imperative DOM application + tests. Each component's residue (legit value overrides the morfo can't express) is pinned in the audit guard. Verified centrally: 112 tests green, check clean, pagination spot-checked in the browser (type/role/aria-label/data render correctly via props-spread). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	c44a259916	refactor(soma): de-dup spin-field triggers + scrubbers via renderProps ... Finishes the spin-field family. The 4 triggers + 2 scrubbers (number-field + css-field) now spread renderProps() and add only soma-specific extras. - Scrubbers: role + aria-hidden + data-spin-field-scrubber now morfo-sourced; soma keeps data-scrubbing/disabled, cursor style, pointer handlers. - Triggers: type + aria-label + data-spin-field + aria-disabled now morfo- sourced. The trigger morfos' aria-disabled moves from literal-'true'+condition to propRef('disabled') + ariaBoolean (the de-facto always-emit shape); each trigger registers its own `disabled` source (includes atMax/atMin) so renderProps resolves it. aria-label resolves from the morfo's commonRef('buttons.increment/decrement') — the SAME idlangref the provider used, so the string is unchanged ("Aumentar"/"Disminuir" in es). - Dropped the now-orphaned NUMBER_FIELD_LANGS + boolToStr imports. Verified in browser for all parts (type/aria-label/aria-disabled/role/aria-hidden identical) + soma/morfo tests 95/95 (2 pre-existing palabras contract failures only). The entire spin-field family is now morfo-sourced — zero re-declared attrs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	75e50becf7	refactor(soma): de-dup CssField Input via renderProps (spin-field family) ... Mirrors the NumberField Input reference. CssField morfo's aria-required/disabled/ readonly/invalid gain `ariaBoolean`; the Input provider drops the hardcoded role + data-spin-field-input + those four aria booleans — all now from renderProps(). Soma keeps the CSS-value-specific bits it genuinely owns: the parsed aria-valuenow, soma-only aria-valuemin/max, aria-valuetext, native form attrs, handlers. Verified in browser (role/aria/data from morfo, parsed aria-valuenow="16") + soma/morfo tests 71/71. Both spin-field inputs are now fully morfo-sourced; the triggers/scrubber + the other families remain on the backlog. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	019413501b	feat(morfo): ariaBoolean entry flag — full de-dup of NumberField Input aria ... `MorfoAriaEntry.ariaBoolean?: boolean` makes a propRef-valued ARIA attr compile to aria-boolean mode (renders the "true"/"false" string), the same shape a stateRef already gets. Without it, `aria-required` ← `required` prop compiled to raw mode → renderProps() emitted a boolean (DOM-identical, but a different props shape, and it forced the provider to keep stringifying). - types/schema/compile wired for the flag. - NumberField morfo: aria-required/disabled/readonly/invalid gain ariaBoolean. - NumberField Input provider: dropped the 4 boolToStr overrides — role + every aria + data-spin-field-input now come from renderProps(); soma keeps only the formatted aria-valuetext, aria-describedby, native form attrs and handlers. The Input is now fully morfo-sourced (zero re-declared attrs). Verified in browser (aria-required="false" string, role/valuenow from morfo) + provider tests 69/69. This is the reusable mechanism for de-duping aria booleans across the rollout. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	59a851850c	feat(soma): morfo-sourced part props — renderProps() + prop-defined (pilot) ... Foundation for removing the morfo↔soma attribute duplication: providers that compose attrs in their `props` getter were re-declaring role/aria/data that the morfo already declares (a second source that drifts — the spin-field bug). - runtime: new `SomaRuntimePart.renderProps()` — static identity + every morfo-declared static/dynamic attr, resolved against THIS part's registered sources. A part's getter spreads it and adds ONLY soma-specific extras (handlers, formatted values, native attrs), instead of hardcoding role/aria. - morfo: new `prop-defined` condition (`emitted iff prop !== undefined`) so an optional numeric aria (aria-valuemin at min=0) emits correctly — `prop-truthy` wrongly dropped 0. Wired through types, resolver, schema, compile dep-collect. - NumberField Input migrated as the reference: registers value/min/max as part sources, spreads `renderProps()`, keeps only soma extras. Removes the hardcoded role + aria-valuenow/min/max + data-spin-field-input duplication. ARIA booleans (aria-required/disabled/…) stay soma overrides for now — a propRef-valued aria compiles to raw mode, so soma still stringifies them; a future `v.ariaBool()` helper would let those resolve from the morfo too. - COMPONENT_GUIDE: "Part props: read the morfo, don't re-declare it" doctrine. Verified bit-for-bit in browser (role/aria/data identical incl. min=0 → aria-valuemin="0") + provider tests 7/7. The survey found ~⅔ of components carry this duplication (form controls 70%); this lands the pattern + the NumberField Input reference. Family rollout is the documented backlog. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	3c059ff087	refactor(eidos): share number-field + css-field visual via spin-field ... NumberField and CssField are the same visual (a bordered field + input + increment/decrement triggers + scrubber, split/stacked layouts, sizes/ variants/colors, themeable glyphs); only their value model differs. They were two cloned recipes + CSS that drifted — a refinement to one (square flush buttons, divider, contrast) didn't reach the other. Unify into ONE shared source (the toggle-group structural-identity pattern): - New eidos/components/spin-field: recipe key `spin-field` (`--spin-field-*`) + spin-field.css with all the stepper-field rules, selecting `[data-spin- field*]`. Loaded via the foundation @import in index.css. - number-field + css-field morfos declare structural identity (`data-spin- field*` presence attrs on each part). The Provider emits them via syncAttrs; the sub-parts emit them in their soma `props` getter (number-field's soma hardcodes sub-part attrs rather than syncing the morfo). - Removed the `number-field` / `css-field` recipe keys; their CSS files are now stubs. A theme tints one component by scoping `[data-number-field] { --spin-field-… }`. - css-field thereby adopts number-field's refined steppers (square, flush, divider) — the drift fix the user asked for, now structural (no clone). Verified bit-for-bit in browser: number-field identical to baseline (split flush, stacked symmetric xs..xl, RTL, glyph token/children override); css-field now square/flush/divider. eidos-lint invalid 0; recipe contract passes (no orphans, loads-once); check + morfo:check clean for these. Docs: THEMING sections 33 (glyph tokens now `--spin-field-*`) + 34 (the shared layer); number-field / css-field READMEs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	ded673ad0f	fix(eidos): unify input focus into a parameterised two-ring model ... Each input drew its focus ring differently — the foundation [data-archetype] :focus-visible ring landing on the <input>, ad-hoc per-component input rings (css-field/number-field), the textarea's own color-mix — so editing showed a DOUBLE frame (inner + outer), inconsistent across components. Unify into one theme-parameterised two-ring model: - New --focus-ring-inner-width (0 by default), folded into --focus-ring and every field *-focus-shadow: inner inset ring + outer ring. 0 = single outer frame; raise it in a theme to show the inner line everywhere at once. - Foundation [data-archetype]:focus-visible now excludes form-internal elements (:not(input):not(textarea):not(select):not([data-archetype='segment'])) — their focus is shown by the wrapping control. - Removed the ad-hoc input rings (css-field/number-field); textarea uses var(--focus-ring). - Cleaned the now-dead per-data-color _accent-* cascade in css-field/number-field (recorded as backlog in THEMING.md §32). Verified with real keyboard on field/css-field/number-field/date-field/textarea: single outer frame. Also includes the earlier textarea `resize` fix (morfo data-resize values + soma stops inlining resize + eidos materialises it). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	7da7285d94	feat(uix): cropper, image-picker, image-adjustments + reusable zoom-pan layer ... Three new components across all 4 layers (morfo/soma/sema/eidos) + demos + langs + READMEs: - ImageAdjustments — reusable image-filter sliders subcomponent. - ImagePicker — composes file-upload + image + image-adjustments (fill modes, rotation). - Cropper — Ark image-cropper anatomy: normalized 0-1 crop rect, rect + round shapes, 8 resize handles, fixedSize move-only (avatar), canvas Blob output (5-arg drawImage for SVG safety), wheel/pan zoom, two-zone gesture (selection moves the area, the background pans to set focus; img draggable=false guards native DnD per zag). New reusable soma/layers/zoom-pan: cursor-centered zoom, clamped pan, transform + viewport-frac-to-content-frac mapping. Image-viewer / diagram-pan / map can reuse it. sema: add 'zoom' verb to the handle family (direct manipulation, documented extension). slider: track visible at zero (gray, not white), thumb lifts on drag. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	b3ef470646	feat(uix): FloatPanel — draggable/resizable floating panel ... New general-purpose overlay component across all 4 layers (morfo/soma/sema/eidos) plus a shared stacking layer and i18n catalog. - Drag (2D free, anchored→free) + resize with device-pixel-snapped, GPU-composited 1:1 movement; elevation lifts on pointerdown for the pickup metaphor. - Stages: minimize / maximize / restore (StageTrigger, computed maximized geometry so restore needs no saved-rect bookkeeping). - Composable header buttons: Controls + Action (custom) + Close + StageTrigger. - Keyboard a11y (the industry gap): grab-mode move/resize on the focusable header and a se-corner ResizeGrip (pointer + keyboard), with debounced live-region announcements, bounds/min-max cues, aria-roledescription/keyshortcuts. - Stacking registry (bring-to-front/topmost), Presence motion preset (scale-fade), es/en langs catalog. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	7ff1738a12	feat(uix): add CssField — validated CSS-value spinbutton + sium CSS helpers ... New 4-layer UIX component for CSS dimension values (px/rem/%/vh/…) modeled on number-field: allowedUnits whitelist, optional increment/decrement triggers, pointer scrubber, keyboard stepping, wheel, Field integration. Validation is ambivalent — built-in pure sium functions by default, or delegate to a sium schema via the validate prop (untilFix feedback on invalid units). sium: parseCssValue/formatCssValue/isCssValue/cssValue + CSS unit vocabulary in arts/sium/types/css.ts; css_value issue code + es/en messages; tests. morfo/soma/sema/eidos: css-field across all layers; recipe tokens + interactive demo + sidebar link + READMEs. Verified: check 0 errors; sium 395, soma css-field 9, morfo+sema 214 tests; morfo:check + eidos-lint clean; browser render/behavior/sema-trace confirmed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	cd8343849d	fix(morfo): checkbox commit events sequence pre -> post (kills 244ms check lag) ... The REAL cause of the slow checkbox (not the stroke duration). The checkbox provider flips its checked state inside the trigger HANDLER, and the morfo declared the commit events with sequence: 'pre' — so the runtime ran `await runEmit()` BEFORE the handler. emit() awaits the visual-channel hold (~240ms), so the functional state change (and thus data-state) waited the full perceptual hold before flipping. Measured: click -> data-state='checked' took 244ms. Fix: commit-toggle-check / commit-toggle-uncheck -> sequence: 'post' (handler runs FIRST, state flips immediately, the celebratory pulse emits after). This is the doctrine for control commits (runtime.svelte.ts §577: "toggle's commit-toggle... the pulse arrives AFTER the state has flipped"). Toggle + Switch were already 'post'; checkbox was the outlier. Measured after: 244ms -> 46ms. Verified the siblings are NOT affected: radio-group (47ms) and tabs (31ms) are also 'pre' but flip state in the call-site (not the handler), so no lag — left unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	ba74b6b416	feat(scroll-frames): adapt to framework + demo; add genie-class motion presets ... ScrollFrames (eidos) rebuilt as a first-class component -- it was draft WIP using bare native APIs. - No native globals: window scroll/resize -> dom.listen + dom.observeResize; requestAnimationFrame -> dom.raf (disposer); window.innerHeight / devicePixelRatio -> dom.getWindow(node); new Image() -> dom.getDocument().createElement('img'). - lang="ts" + typed props (types.ts) + index.ts + data-attrs + recipe CSS (no scoped <style>), registered in index.css. - New `root` prop: drive progress from a scroll container instead of the window (makes it embeddable + demoable). - Morfo (morfo/components/scroll-frames.ts): scope ['eidos'], 4 parts, 0 events. - Demo (uix/components/scroll-frames): locked 6-tab template, self-contained generated frames (canvas -> data URL), scrollable stage via `root`. + README. - Fixes the 12 errors the earlier draft pushed (branch back to the 1 pre-existing grafito error). Motion demo (temas/animations): "genie y cia" section -- 4 expressive JS presets played via eidos.motion.enter: genie (waapi warp), flip-3d (rotateY), swing (pendulum), elastic (overshoot spring). Verify: npm run check -> 1 pre-existing error (grafito), 0 new; recipe-css + component-api contracts clean (3 pre-existing words failures); morfo:check scroll-frames PASS (1/108 fail = pre-existing words). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	0d66e5a4e7	fix: address architectural audit findings + sync ecosystem docs ... Audit: src/audit-opus-4-6-26.md. All non-words findings remediated. Code: - E1: navigation-menu indicator data-state visible -> open (render bug; the active underline was permanently invisible). Clears the only invalid lint selector. - SO1 + E2: raw `new ResizeObserver` -> ActiveDom.observeResize in carousel-provider and the canvas-text useContainerWidth hook (+ s-text / s-text-virtual-list pass eidos.dom). iframe/popup-safe, lifecycle-tracked. - A1: defineUixServices now registers `motion`, so attach-mode app.motion is real and the active-uix fallback becomes the true edge case (test guard updated). - A2/A4: contracts.ts pins `motion` + `announce` in ActiveUixServiceContract + publicSurface; dispose() comment corrected. - SO2: carousel drops the hardcoded `transform 300ms ease-out` (the recipe already handles it via [data-dragging]); also fixed the recipe's undefined `--duration-base` token -> `--duration-slow` (it was masked by the inline). - S1: HapticChannel reduced-motion via an injected ActiveDom port (mirrors SoundChannelDom) instead of global matchMedia. - T1: 10 sites repointed `$libs/dom` -> `$adom` (sema x5 + its tests x3, active-uix value import, arts/prefs). - M2 / S2 / S3: dead code removed (button `states:['idle','loading']`, SemaRuntimeChannelId, SEMA_VALENCED_FAMILY_LIST). Docs: - Motion-as-service reflected across the ecosystem: CLAUDE.md (aliases + arch + service note), arts/README, active_architecture, soma SOMA_ARCHITECTURE, eidos README, eidos-motion.md. - X1: CLAUDE.md "5 canonical channels" (false) -> the single canonical narrative (8 book channels; Sema runs 2 + visual meta-channel, Eidos materializes 5). - X2/X3/X4: sema/README (8 families + intentRequirement/intentGuidance split), types.ts JSDoc (SEMA_INTENT_POLICY -> SEMA_FAMILY_POLICY), engine.ts cascade 6->5, alias table ($frontend out, $lang->$langs, +$clipboard). - E4: codex_audit.md HISTORICO banner. Deferred: SU2 (test-only layering, not a build violation); Words M1/T5/E3 (WIP). Verify: npm run check -> 1 pre-existing error (grafito), 0 new; sema 152/152, contracts 31/32 (1 pre-existing words), carousel 4/4, motion 22/22. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	49802e9257	fix(words): close 4 cross-layer audit findings (morfo/soma/eidos) ... Full audit of the Words component (3 parallel explore agents + deterministic gates) surfaced 4 carried-over defects, all verified and fixed: - R2 (soma) engine/operations/visual.ts:147 — the `node as Record` cast in updateBlockAtPath failed because WordsNode includes WordsDocument (no index signature). Use the double cast `as unknown as Record`, consistent with the sibling op at line 118. Clears the only Words type error in `npm run check`. - R1 (morfo) components/words.ts — the `data-words-node` enum was conflated with `data-words-block`: it listed block TYPES (paragraph/heading/quote/ code/image) that nothing emits on that attr, and OMITTED the real structural kinds the engine writes (`block`/`inline`). Aligned to the engine's WordsDomNodeKind. eidos-lint invalid selectors 2 → 0; verified in the browser that top-level blocks carry node='block' and the active-block outline still paints. - R3 (eidos) langs-inspector.ts — `LABEL_COLUMN_BLOCKS` had no bundle entry, so the column "Blocks" panel title fell back to English in ES. Added label.column-blocks + label.add-block. Verified: panel now reads "Bloques". - D3 (morfo) components/words.ts — declared `expression: 'family-default'` to make the no-sema-pack choice explicit; `morfo:vocabulary` no longer warns about the missing pack/expression. Gates: npm run check 1 error (pre-existing, web/routes/temas/grafito — not Words) · words soma+morfo 514/514 · eidos-lint words invalid 0 · prettier clean · morfo:vocabulary exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	10ed029b91	refactor(words)!: remove V1 engine — V2 is now the sole engine ... Deletes the V1 rich-text engine and the extensions/ tree. The public document model flips from WordsDocument to WordsDocumentV2 (D1: V2 puro, sin legacy — no backward-compat importer, V1-persisted docs no longer load). Per D2, table striped/compact/cell-tone are dropped entirely (props, commands, morfo attrs). - Delete engine/{document,operations,commands,history,input,render, find-replace,serialize-{html,json,markdown,text},dom-selection,index} and the whole extensions/ tree (registry + image + table). - Complete the V2 ops under operations-v2/: port commands, history, input, find-replace, render-dom, serialize-text, extra-ops, insert-block-types, markdown shortcuts, factories, dom-selection; land R4A.2-R4A.8 (text/delete/marks-ops/paragraph-ops/delete-ops/ block-format/list-ops/link-ops/table-ops/selection-walkers). - Rewire provider, exports, types, morfo/words.ts, eidos word components, soma words.svelte, the content-test harness, and the /uix/components/words demo to V2. - Import accepts JSON (JSON.parse + validateWordsDocument gate) and plain text only; HTML and Markdown remain export-only (lossy, no faithful inverse parser). Verify: npm run check 0 errors; words scope 455/456 (lone failure is the sema-parity 5s timeout flake under parallel load — 6/6 isolated); morfo:vocabulary exit 0; browser smoke of /uix/components/words green (sample renders, text + JSON import round-trip, invalid JSON rejected without mutating the doc). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	4 months ago
dev	c4be6dbe1b	fix(words): silence body event spam + slim top toolbar + reposition handle/inserter ... Four user-requested fixes to the Words editor surface — the body should not emit perceptual cues during editing, the top toolbar must not duplicate the drawer, and the gutter widgets need clearer anchor points. EV-A (events spam): - Move `contact-focus` event target from `content` to `provider` in the morfo + sema cascade selector. Focus is a Words-component-level signal; firing it from the content body conflates "user entered the editor" with "user is editing the body". The wasFocused guard in soma already throttles to one emit per real focus transition. - Expand `isInsideWordsTool` selector list to cover the four companion overlays added after the original list was written: `data-words-drawer`, `data-words-block-handle`, `data-words-block-handle-menu`, `data-words-block-inserter`, `data-words-image-float-bar`. Before this fix every click on a companion overlay fired commit-save-content + contact-focus on the blur/refocus cycle (two perceptual cues per tool interaction). EV-B (toolbar trim): - Demo's full / formatting / minimal presets + custom config now host only GLOBAL actions: history (undo/redo), insert (creates new blocks), link (selection-bound flow), tools (find/replace + clear), find-replace in its own group. text-menu / block-menu / align-menu / list-menu / table-menu moved out because the drawer already owns contextual formatting per the HIER-2 split. EV-C (block-handle drag UX): - Drop the `setDragImage(hoverBlockEl)` call. The browser now uses its default snapshot (the grip button itself) as the drag ghost — the ghost travels with the cursor while the bar in the gutter stays fixed as a visual anchor. New `data-dragging` attr + `[data-words-block-handle][data-dragging]` CSS rule fades the static anchor to 0.35 opacity so it reads as "drag origin" while the ghost is the moving part. EV-D (inserter at block bottom): - Seam positions are now pinned to the BOTTOM EDGE of the preceding block (`a.bottom`) instead of the midpoint of the gap between two blocks. The "+" reads as "insert AFTER this block" anchored to that block's lower edge, per spec — el botón de añadir bloque debe aparecer en el límite inferior del área en relación al bloque. - Tighten the "cursor inside block band" check to a half-open interval `[top, bottom)` so the exact bottom-edge pixel belongs to the seam below (otherwise the seam at `y === bottom` is shadowed by the block and the inserter never snaps). Verification: dev server, /uix/components/words, DOM probe confirms handle centered in the rail column (left=48 inside the 32-wide rail starting at ~46), inserter snaps to block 1's bottom (`top=569.94px` when block 1 bottom = 570px). 366/366 tests pass in morfo + sema + soma/components/words. `npm run check` still 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d2f184da44	refactor(toggle-group): item is structurally a Toggle (zero derivation duplication) ... Closes the deuda left explicit in hand-off 2026-05-27 #5: the inlined derivation expressions in toggle-group.css duplicated Toggle's recipe because [data-toggle-group-item] wasn't a descendant of [data-toggle]. Resolution is structural, not a drift test: - morfo: each item declares { attr: 'data-toggle', value: v.literal(''), severity: 'required' }. Captures structural identity — an item IS a toggle in every observable sense (same press, same variant/color/size, same on/off machine). - eidos: new context.ts propagates the root's variant + size via reactive getters; the item wrapper writes them as data-attrs on its button. Combined with data-toggle, the item is DOM-equivalent to a standalone <Toggle>. - eidos css: ~150 lines deleted (base derived tokens, variant cascades, size cascade, focus/disabled/icon-only duplicates). Toggle's recipe now paints the item end-to-end. CSS keeps only the grouping concerns: flex, orientation, attached, block, focus z-index, group disabled. - composition (TSC v2.2) stays — palette overrides land on the item under [data-toggle-group][data-color='X'] [data-toggle-group-item], which Toggle's --toggle-palette-* chain reads at item scope. Verification: - DOM probe (12 combinations: 4 colors × 3 variants × 2 states) on /uix/components/toggle-group. Computed values match bit-a-bit with baseline pre-refactor (e.g. affirm/solid on = rgb(18,165,148), risk/outline on = srgb(0.2,0.118,0.043), threat/ghost on = rgb(25,17,17)). - vitest src/uix/{morfo,eidos}: 163/163 pass. - vitest src/uix/soma/components/toggle-group: 4/4 pass. - npm run check: 12 errors (all pre-existing in active Words sprint; zero added by this migration). Drive-by: the same npm-check pass surfaced 4 stale 'orientation' refs in words-toolbar.svelte + words-toolbar-group.svelte from this session's earlier toolbar refactor (orientation was removed from types but not from these soma components). Removed; brings check from 16 → 12 errors. CLAUDE.md hand-off 2026-05-28 documents the new doctrine: when a wrapper visually reuses another, declare structural identity in the wrapper's morfo. Don't duplicate the cascade, don't extend TSC for one case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d767d88c03	fix(codex-audit): close P0 + tokenize drift introduced by Words sprint ... Three categories of audit drift introduced during the recent Words sprints (drawer redesign, image float bar, color marks, insert panel, gutter rail), all caught by the existing contract tests now that the work has landed: 1. **Undeclared morfo attr** (P0 contracts test): `data-words-block-selected` is stamped by the engine's render on the atomic-selected block (today only image) but wasn't in the morfo's data-attr list. Adds it as optional on the same parts array that already declares `data-words-image-*`. 2. **Missing i18n key** (translations:check): The drawer part references `components.words.drawer` for its aria-label, but the langs catalog was never updated when DRAWER-CANON landed. Add `drawer` to `src/uix/langs/components/words.ts` (es + en). 3. **Recipe CSS contract drift** (eidos recipe-css-contract test): - 3 undeclared CSS vars used in the drawer-Editable styles: `--words-toolbar-color` → `--words-command-color` `--words-command-hover-bg` → `--words-command-bg-hover` `--words-command-active-color` → `--words-command-color-hover` (Right names per `lib/recipes/base.ts > words`.) - 15 raw font-size literals (0.65rem / 0.7rem / 0.75rem / 0.8rem / 0.9rem) replaced with the existing words font-size tokens: 0.65/0.7rem → `var(--words-status-font-size)` 0.75/0.8rem → `var(--words-font-size-sm)` 0.9rem → `var(--words-font-size-md)` Result: - `contracts.test.ts`: 31→32 pass (the data-attr violation is gone). - `translations:check`: 219 refs / 76 catalogs / 0 errors / 0 warnings. - `recipe-css-contract.test.ts`: 17→19 pass. - Full `vitest run src/uix`: **867/867** pass (was 865/2-fail before). - `npm run check` clean (only 6 pre-existing errors unrelated). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	71c24dca9b	refactor(words): drop vertical toolbar orientation ... The companion drawer + new floating overlays (image bar, block handle, block inserter) assume a horizontal toolbar above the content. The vertical layout was a CSS-grid two-column repositioning that fights that geometry and was the cause of the new design breaking when the user switched to vertical. `horizontal` is the only orientation now. Cuts: Morfo (`morfo/components/words.ts`) - Toolbar + ToolbarGroup parts: `data-orientation` becomes a literal `'horizontal'` (no longer reads from `propRef('orientation')`). - Same for the toolbar's `aria-orientation`. Soma (`soma/components/words/types.ts`, `exports.ts`, provider) - Removed `WordsToolbarOrientation` type entirely. - Removed `orientation?` from WordsToolbarProps and WordsToolbarGroupProps. - Provider opts no longer read or pass through `orientation`. Eidos (`eidos/components/words/{types,words.svelte,words-toolbar.svelte,words.css}`) - `WordsProps.toolbarOrientation` removed. - `<Words.Toolbar>` / `<Words.ToolbarGroup>` no longer accept or forward `orientation`. - Six chunks of CSS that targeted `[data-orientation='vertical']` deleted (toolbar layout, content grid placement, status, find-replace, link-editor, placeholder). Demo (`web/routes/uix/components/words/+page.svelte`) - `orientations` const, `orientation` state, the chip-control UI, the `toolbarOrientation={orientation}` prop, and the corresponding line in the generated code snippet all removed. - Recipe-selector entry for `[data-orientation]` deleted. - A11y row text simplified. Verified: `npm run check` clean (only pre-existing 6 errors unrelated); soma words tests 152/152 pass. Eidos vertical CSS is gone end-to-end. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	e25ac301b5	feat(words): drawer hierarchical mode stack — Format → Cell → Row → Table (HIER 1-3) ... The drawer now renders the FULL hierarchy of scopes that apply at the caret, instead of only the most-specific one. Inside a table cell with text selected the user sees four panels stacked: Format ← active selection's inline marks/links Cell ← tone, vertical align, cell text-align Row ← +/- row, row header toggle Table ← striped, compact, +/- column, col header Each panel is independently collapsible. Default: the leaf (most specific) is open, the rest are collapsed but accessible via the chevron next to their header. User-explicit toggles persist across context changes. HIER-1 — soma: - WordsDrawerMode union expanded: split 'table' → 'cell' | 'row' | 'table'; split 'list' → 'list-item' | 'list'; added 'block' for the paragraph/heading/quote text-align scope. - WordsDrawerProvider gains `modes: readonly DrawerMode[]` derived that walks the caret context outward (most-specific first). The legacy `mode` field is kept as the top of the stack for consumers that just want the leaf. - snippetProps surfaces both `modes` (stack) and `mode` (leaf). - Morfo `data-words-drawer-mode` values updated to the new union. HIER-2 — eidos panel split: - Table panel decomposed into three: cell-scope (tone + vertical + text-align), row-scope (+/- row, row header), table-scope (+/- col, col header, striped, compact). - List panel decomposed into list-item-scope (indent/outdent) + list-scope (kind). - New 'block' panel hosts text-align when caret is in a heading / paragraph / quote outside a table cell. - Each panel is a `<section data-words-drawer-panel data-depth=N>` with its own toggleable header + body snippet. HIER-3 — per-panel collapse: - SvelteMap stores user-explicit open/closed overrides per mode. isPanelOpen() falls back to "open if leaf, else collapsed" when no override exists. - Drawer header now shows leaf title in bold + breadcrumb of deeper panels in muted text (Format · Cell · Row · Table). - Visual depth cue: border-inline-start of each panel renders at decreasing strength as depth grows (leaf solid, deeper at 60% / 30% accent border). Visual verification: selected text inside a sample table cell shows 4 panels stacked (Format open, Cell/Row/Table collapsed), header breadcrumb "FORMAT · Cell · Row · Table". Click on any collapsed header expands it. 214/214 tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	9a5f3c2359	refactor(words): drawer canon — morfo part + soma provider + eidos consumes via provider (DRAWER-CANON) ... Closes the architectural gap from the DRAWER spike: the companion drawer now follows the same morfo/soma/eidos pattern as every other Words part (Toolbar/BubbleMenu/SlashMenu/LinkEditor/Status/etc.). DRAWER-CANON-1 — morfo + soma: - wordsMorfo gains a 'Drawer' part (kebab 'drawer', archetype 'group', defaultElement 'aside', role 'complementary'). Declares data-words- drawer-mode (default/format/image/table/code/list), data-open, data-disabled, aria-label. New event 'commit-toggle-drawer' fires on collapse/expand for sema/telemetry hooks. - New WordsDrawerProvider in words-provider.svelte: owns `open` bindable state, derives `mode` from parent provider's currentBlock + selection (same logic as the spike, now in soma where it belongs), exposes snippetProps {mode, open, disabled, snippet, toggle, setOpen}. `toggle()` and `setOpen()` emit the event. - WordsDrawerProps + WordsDrawerSnippetProps + WordsDrawerMode types added to types.ts and re-exported via exports.ts. - soma/components/words/components/words-drawer.svelte (the soma component) mounts the provider and forwards merged props to either the `child` snippet or the default <aside> render. DRAWER-CANON-2 — eidos refactor: - eidos words-drawer.svelte rewritten as a consumer of <Words.Drawer>. The shell (aside + header + collapse button) and the per-mode body now live inside the children snippet that receives the soma's drawer snippet props. Mode derivation removed from eidos (it's now in soma). Local open $state removed (now bindable via the soma component). - Demo +page.svelte: `<Words.Drawer snippet={snippetProps} />` collapses to plain `<Words.Drawer />` — the soma provider hands the parent snippet down internally. DRAWER-CANON-3 — verify: - 214/214 tests pass in soma+morfo scope (no regressions). - npx tsc --noEmit clean for words area. - Visual verification: drawer still renders with DOCUMENT/OUTLINE/ STATS/SUGGESTIONS in default mode; context-switching to table / code / list / format still works; aside element now carries role='complementary', aria-label from morfo translationRef, data-words-drawer-mode reflecting current panel. The eidos drawer now passes the same canon checks as every other Words part: morfo declares its contract, soma owns the state, eidos only paints. The schema validator can verify the drawer's attrs, the eidos lint can check selector usage, sema can react to the toggle event. Demo header chips reflect the new contract: PARTS 19→20, EVENTS 11→12. 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	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	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	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	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	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	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	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	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