13 Commits (468a9d1134d697546f1b36231d6773d6324a5faa)

Author	SHA1	Message	Date
dev	b105421104	feat(soma)!: C+ especie 1 — grid-walk: el paseo 2D de los 4 calendarios es UN primitivo ... Primera especie del veredicto C+ (firmado b54bb3ad0: la ejecución de teclado converge en primitivos por especie). El censo midió ~90 % de máquina compartida hand-rolleada ×4; ahora: - soma/keyboard/grid-walk.ts: gridWalk<T>(event, from, opts) — puro y genérico sobre la UNIDAD del host (DateValue, {year,month}, number). Devuelve false en teclas ajenas (un Popover envolvente sigue viendo su Escape). Flechas 2D con dir lógica (RTL voltea X) · Home/End vía bounds() del host · PageUp/Down con evento (los calendarios leen shiftKey) · compare() decide el SENTIDO del cruce por ORDEN (jamás por tecla) · isOutsidePage/showPage = la máquina de bordes con hop · onLand ANTES del giro (orden embarcado) · salto de foco unificado (queueMicrotask + attr tipado + dom.focus). Enter/' ' NO entra: los 4 comprometen distinto — un commit no es un paseo. ~78 líneas de doctrina a propósito. - 4 providers = delegados finos (−58 en ejecutores; calendar −16, range-calendar −12, month-grid −14, year-grid −16). Los Shift+ de rango y Escape quedan en range-calendar (especie propia). - CERO tests re-firmados (ninguno pineaba máquina interna — los dos de teclado ya extraían conducta). +9 casos en grid-walk.test.ts, cerrando un hueco PREEXISTENTE: month-grid y year-grid no tenían NI UN fichero de test client. - Censo focus: la señal getDirectionalKeys+dom.focus la absorbió el primitivo — la red reconoce gridWalk (+6) sin debilitarse. Los 4 morfos actualizan su executor.custom a la verdad nueva: ejecutado por el primitivo 2D COMPARTIDO, no el RovingFocusGroup 1D. - De paso mueren los 4 selectores morfo-targeting a mano ([data-calendar-day] etc.) → attrs tipados de createAttrs (la ley del builder). AMBIGUOS retenidos con acta (no unificados en silencio): Home/End de month/year-grid = PÁGINA ENTERA (lo declarado y lo embarcado; el brief suponía fila) · los DOS calendarios difieren en la puerta del borde (min/maxViewValue y announceNavigation solo en calendar) — conservado en sus callbacks · Shift+PageUp/Down ±1 año sin declarar (clase modificador del censo keyboard) · skip de disabled: NINGUNO de los 4 lo hace. morfo+keyboard 285/285 · calendar/range-calendar client 19/19 · census 109/109 · check 71. Constructor Opus 5, sesión coordinando y verificando. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	1 month ago
dev	17c6adddcb	feat(morfo)!: P1 — split attrs[]/aria[] y vocabulario ARIA cerrado: cada cubo su territorio ... El cubo aria[] mentía un 13,5 %: 989 entradas medidas — 847 aria-*, 8 role, y 134 impostores (type ×130, tabindex ×2, for, contenteditable). - MorfoPart.attrs[]: cubo nuevo para atributos HTML genéricos, misma forma de entrada y mismo compilado (un solo builder para ambos cubos). - aria[] se CIERRA por tipo: MorfoAriaAttr = 'role' | unión del spec (53 nombres, DERIVADA del array ARIA_ATTR_VOCABULARY — nunca lista paralela, la lección MorfoElement). aria-grabbed/aria-dropeffect deprecados-en-1.2 con acta (verdad embarcada de drag-drop); braille*/description son 1.3 y entran anotados. Un typo muere en el tipo. - Esquema guarda el territorio en AMBAS direcciones: aria[] con no-aria LANZA sugiriendo attrs[]; attrs[] con aria-*/role o data-* LANZA. - Codemod: 134 entradas movidas en 62 morfos (133 bloques). Orden de emisión MEDIDO y conservado: data → attrs → aria (132/133 bloques declaraban el impostor como prefijo contiguo de aria[]); snapshot de los 921 parts × 168 morfos: 920/921 byte-idénticos — la única divergencia (breadcrumb.ellipsis, type tras un aria-label consumerWins) no cambia la bolsa renderizada. - Consumidores de part.aria censados: compile/resolver/schema actualizados; morfo-check pierde un filtro MUERTO (el cubo ya llega cerrado por tipo+schema); landmark-census y tests de la mitad aria sin cambio. - morfo.md documenta los dos cubos. 13 tests nuevos (8 schema territorio + 5 compile paridad). morfo 262/262 · soma entera 1314/1314 · check 71. Nota de árbol compartido: src/uix/morfo/source-census.test.ts (sin trackear) es el eje SourceMap de vicen-e1 y NO viaja aquí (add -u); su censo re-medirá sobre este árbol asentado, orden acordado por canal. Ejecutado por agente Opus 5, sesión coordinando y verificando (guardas de territorio probadas en vivo, suite re-corrida). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	1 month ago
dev	2c0fca4319	feat(morfo): 28 morfos declaran su política de foco — la especie, por escrito ... 9 trap (dialog, drawer, alert-dialog, context-menu, dropdown-menu, menu-dial, onion-menu, float-panel, popover) y 19 roving (toolbar, menubar, tabs, listbox, radio-group, stepper, tag-group, tags-input, toggle-group, carousel, drag-drop, tree-view, tree-grid, grid-list, chronos, calendar, range-calendar, month-grid, year-grid). Actas dentro de cada declaración; las que corrigen mentiras: - popover: trap FALSE — declaraba true desde hacía meses con cero lectores; la verdad embarcada manda. - radio-group: orientation 'both' por APG — su propio keyboard[] declaraba las 4 flechas; lo embarcado (2 flechas) era la deriva. El provider pasa both=true al ejecutor. - calendarios ×4 (calendar, range-calendar, month-grid, year-grid): grid + executor.custom firmado — roving-tabindex REAL medido en sus providers (focused ? 0 : -1), 2D que el primitivo 1D no expresa. - grids/árboles (tree-grid, grid-list, chronos, carousel, drag-drop, tree-view): custom firmado con su razón. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	1 month ago
dev	243122393d	refactor(soma)!: fase C2b — renderProps() muere; .props es la única bolsa ... Tras C2a las dos computaban lo mismo. Sin shim, por doctrina: los 262 call sites en 62 ficheros migran a `.props`, el método y su tipo desaparecen del runtime, y las ~200 menciones en comentarios (la plantilla «lets renderProps() emit…» de los morfos incluida) pasan a nombrar la bolsa de render, para no dejar deriva doc↔código en el propio código. Verificación: svelte-check con src/ a 0 (71 errores = exactamente el ledger de web/) · suites de soma tocadas en verde. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	1 month ago
dev	6f42eebfe8	feat(morfo,sema,eidos): todo evento dice de que familia es, y el cruce por fin se ve ... El framework llamaba a la misma cosa de dos maneras: `open` pelado en ocho componentes y `emerge-open` en tres. No era estetica — un preset de movimiento engancha el nombre con `^=`, asi que el dialecto pelado no casaba con ninguna firma y simplemente no animaba, sin romper una sola prueba. Los 40 nombres sin prefijo pasan a `{familia}-{verbo}[-{matiz}]`: 256 eventos, 256 con prefijo, 0 ambiguos. El plan decia 36 y decia `handle-drag-start`; eran 40, y el canon (c25) dice que esos verbos son `pick` y `drop` — `handle-pick` y `handle-drop` ya existian en 10 y 4 componentes. `validateMorfo` cierra la puerta: un `events[].name` que no empiece por su familia ahora lanza. Visto fallar antes con un nombre pelado inyectado. Lo que el renombrado destapo, y va aqui tambien: - La receta del splitter enganchaba `commit-resize`, muerto desde `bd2e40366`. No casaba desde mayo y nadie chillo. Reescrita por FAMILIA, como slider y knob, y `eidos-lint` valida ahora el VALOR de `data-event*` contra el catalogo de morfos — el guard que lo habria cazado en su dia. - La familia `shift` era muda en el canal visual, contra su propia doctrina (c27: el cruce debe percibirse; c34 tipifica el «shift invisible»). Su mapa ya describia la firma que le faltaba y su sonido por defecto es `slide`. Ahora tiene firma direccional: sexto atributo del sello (`data-event-direction`, `forward`|`backward`, por emision) y deslizamiento de 320ms RTL-safe por `:dir()`. Medido: LTR -30px/+30px, RTL los invierte. - El sello de `shift-navigate` pasa del BOTON al `grid` en los cuatro calendarios. Medido: el boton recibia `contact-activate` y 8,5 ms despues —media trama— el `shift-navigate` pisaba la misma ranura y el `press-squeeze` moria sin pintar un fotograma. Una superficie, una ranura (A-36). - 101 contradicciones docs<->morfo adjudicadas con evidencia (git log, docs de decision, el componente vivo). Las docs desfasadas, corregidas; los nueve DEFECTOS de codigo obsoleto quedan abiertos y sin tocar. - `SoundDirection` -> `SoundContour`: era un contorno de tono, no un sentido, y habia tres cosas distintas deletreadas «direction». check en su linea base con 0 errores nuevos por diferencia de conjuntos · docs:check 0/0 · eidos-lint invalid 0 · el censo y las escenas de navegador medidas con raton real y rAF vivo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2 months ago
dev	fc84305c22	feat(direction): el mecanismo pertenece al morfo — la declaracion exige el cable ... El campo obligatorio `dir: SomaRuntimeDir | null` de 4.1 conservaba el gate a costa de ~116 lineas de ceremonia: 67 `dir: null` en fuente + 47 en tests obligaban a ~75 componentes SIN direccion a pronunciarse sobre un eje que no les concierne, y `parts` era un `readonly string[]` sin validar — un typo estampaba nada, en silencio (fail-open). El usuario lo dijo antes que la auditoria: "los dir no deben ser obligados de pasar". Ahora lo declara el MORFO, que es donde viven los contratos: direction: {} // 46 morfos — estampa en 'provider' direction: { parts: ['trigger'] } // dropdown-menu (su raiz no renderiza) direction: { parts: ['content'] } // drawer · float-panel (pintan en portal) direction: { parts: [...,'input'] } // css-field · number-field (dos caras) y el TIPO se computa de la declaracion, con el generico que ya existia inerte en soma.runtime<M>: morfo declara direction => dir: Active<Direction|undefined> REQUERIDO no declara => dir?: never PROHIBIDO Olvidar el cable no compila; cablear un eje a un componente sin direccion tampoco. Y compileMorfo valida direction.parts contra el arbol declarado — fail-CLOSED: el typo que antes estampaba nada ahora revienta al registrar. El colapso: 49 getters `{ get: () => this.opts.dir.current }` -> `dir: this.opts.dir`; los 67+47 `dir: null` MUEREN. El estampado gana su sitio en el tipo de la superficie (`SomaRuntimePart.props` incluye `dir?: Direction`), asi que los casts `(props as Record...).dir` de los tests sobran. El gate cazo en el acto, y las dos presas eran reales: - `command`: 4.1 le dejo `dir: null` en el runtime y el estampado manual inline en el assert (la linea no estaba sola y el barrido no la vio) — un componente CON direccion que habia quedado fuera del mecanismo. - 5 runtimes SECUNDARIOS del mismo morfo (accordion item, nav-tree item, emoji-picker cell, context-menu root-runtime, feed sentinel): mismo morfo, misma exigencia — reciben la afirmacion del dueno (el estampado solo aterriza en direction.parts, que esos runtimes no registran). Guards nuevos: - compile.test: normalizacion a ['provider'], partes explicitas, y el fail-closed del typo (4 casos). - direction-census.test: prop publica `dir?: Direction` <=> morfo.direction, en ambos sentidos, con las excepciones FIRMADAS y sus razones (field-langs: LangSpec; waveform: delega en el Slider; popover/tooltip/link-preview: overlays puros cuya pintura estampa la capa flotante en el wrapper portalizado — declararles direction seria el atributo inutil contra el que 4.1 avisaba). El propio censo cazo a esos tres: la excepcion quedo escrita el mismo dia que el guard. Verificado en Chrome con la fuente nueva (el morfo): dropdown-menu estampa en el TRIGGER, css-field en raiz E input, drawer con pagina rtl por prefs deja el content SIN atributo y computa rtl por herencia — el modelo del flip intacto. check 77 = linea base · morfo+soma+active-uix 1401/1402 (el 1 es soma-attr-audit, flaky bajo carga, pasa aislado) · rtl:check 1 (palabras) · docs:check 0/566. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2 months ago
dev	53b6f629f2	feat(audit): component re-audit + fixes P0–P5 (P4 complete, P5 in progress) ... Re-audit of the whole component catalog at pilot depth (91 fichas + the checkpoint verdicts in docs/audit/components/) and the executed fix packages. - P0–P3: doctrine (sema participation, CANON §3 intent, component-guide §5 + API naming, §32 outline), guards (morfo-vocabulary-check S10/S11d, component-audit A-3.1/A-1.4/S9, eidos-lint classHooks), morfo contracts (role=application removed ×4, aria-selected off the Day, drp translationRef, field data-state prune, pin-input commit-set, media-player renames), 13 new sema packs + 12 morfos family-default → pack. - P4 (N1–N10) COMPLETE: selectionMode (select/combobox/toggle-group/calendar); onValueCommit terminal-callback norm (pin-input/search/password/textarea + date/time/color-field add); typed validation reason + onInvalid (tags-input, css-field); index/onIndexChange (carousel); deselectable; openDelay/ groupSkipDelay; allowCustomValue; defaultValue prune. - P5 (in progress): S1 class-hooks codemod (22 hooks → data-attrs across cropper/button/image-picker/toggle/image-adjustments); S5 outline remnant in field.css; depth pass (data-depth=overlay on tooltip/toast/float-panel); touch-rows (--touch-target token, decoupled ::before hit-slop, area-not-visual, 44 AAA). S6 (Field composition) + S8 (calendar-surface) pending. Verification: errors-outside-(alpha|words|palabras|chronos) == 59 (baseline); morfo-vocabulary-check exit 0; eidos-lint class-hooks/invalid 0 on touched components; per-component vitest suites green. Handoff + remaining plan: docs/process/continue-audit-fixes-2026-07.md Excluded (broken by the N1 rename, left broken per user decision, not staged): words/**, palabras/**, chronos, web/routes/alpha/**. Reconciliation pending: the touch-rows ::before for checkbox/switch reverses changelog §37's earlier pseudo-element rejection (WCAG-overlap) that had routed markers to a labeled-row/Field task — flagged for the user in the handoff. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	212624e0b2	fix(uix): audit Phase 3 — SYS-1 scope-drift, declare 'eidos' where a recipe exists ... Decision (the one definitional call SYS-1 required): morfo `scope` enumerates the layers that IMPLEMENT the component (per the glossary), so a component with an `eidos/components/{c}/` recipe + wrapper MUST list `'eidos'`. This matches the 62 components that already declared it correctly (dropdown-menu, accordion, tabs, checkbox, radio-group, splitter, …) and makes "which components have eidos" answerable from the morfo. Chosen over the implicit-eidos alternative for explicitness. Added `'eidos'` to the morfo-level `scope` of every drifted component — the 62 with a real eidos recipe (.svelte/.css, not a README-only dir) whose scope omitted it. After this, all 124 audited morfos declare scope consistently; scope-drift = 0. `scope` is purely documentary (the only readers are the schema validator — `layerSchema` already accepts `'eidos'` — and the 2-of-3 doctrine; nothing keys behavior off it), so this is a behavior-safe documentation alignment: every diff is exactly one `scope:` line, `npm run check` adds zero errors. words/palabras/chronos excluded. calendar included (its morfo is clean; the view-switch refactor lives in soma/eidos, untouched here). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	3 months ago
dev	f822d6e4dd	fix(eidos): DatePicker/Calendar — flush field triggers + drop listbox `item` chrome from grid cells ... Several distinct regressions/latent bugs surfaced via the DatePicker, all the same root: parts wrongly typed as the interactive `trigger`/`item` archetype pulling button/listbox chrome they should not have. - Field overlay triggers (date/time/color picker, date-range) are NOT buttons: new `field-trigger` archetype; the picker trigger soma overrides the popover's generic `trigger` archetype with it. popover.css no longer applies the generic popover-button envelope to `[data-field-control-trigger]` (composing IconButton flipped CSS load order, so the button border/bg bled into the flush field icon). - The field input drops its padding on the trigger side (logical → LTR + RTL): `[data-archetype='input']:has([data-field-control-trigger]) { padding-inline-end: 0 }` — the trigger sits flush instead of behind the full text padding. - Calendar/range/month/year-grid Cell + GridRow + Day declared `archetype: 'item'`, which shipped the listbox-row chrome: 6px cell padding (tall rows), a full-week hover band, and `[data-archetype='item'][data-selected]` (higher specificity) OVERRODE the calendar's accent fill so the selected day showed the menu tint instead of solid accent. These are display gridcells, not menu items — archetype removed; the Day keeps its bespoke `[data-calendar-day]` styling. Verified in browser: DatePicker now matches the standalone Calendar (32px rows, solid-accent selected day, no week-band hover, flush calendar-icon trigger). morfo 62/62. Excludes words/palabras/chronos. 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	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	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	f7831563a1	feat(month-grid, year-grid): standalone primitives parallel to date-picker views ... DatePicker.MonthView / YearView require a DatePickerProvider context and can't be used standalone. This commit introduces MonthGrid and YearGrid as independent primitives that accept value / placeholder / minValue / maxValue as props and work anywhere. morfo - New morfo/components/month-grid.ts and year-grid.ts. - scope: ['soma','sema'], apg: grid pattern. - 7 parts each: Provider (role=application) / Header / Heading / PrevButton / NextButton / Grid (role=grid) / Cell (role=gridcell). - Events: commit-set (cell click) + nav-step (prev/next). - Cell data-attrs: data-value, data-selected, data-current, data-disabled, data-focused. - Keyboard map covers arrows / Home / End / PageUp/Down / Enter / Space. soma - New soma/components/{month-grid,year-grid}/ with provider class + langs + types + exports + 7 thin svelte wrappers each. - MonthGridProvider: 12-cell grid keyed to placeholder.year; localized month names via Intl.DateTimeFormat with configurable monthFormat ('long'|'short'|'narrow'). Prev/Next step ±1 year. - YearGridProvider: decadeSize-cell grid (default 12); page anchored at placeholder.year - (placeholder.year % decadeSize). Prev/Next step ± decadeSize. - Both expose Cell sub-provider with snippetProps {selected, disabled, current, value, label} + roving tabindex + RTL-aware keyboard nav. eidos - New eidos/components/{month-grid,year-grid}/ — namespace-style index with size / variant / color visual props + dedicated CSS reusing the --calendar-* token family. - Each grid renders Header (Prev/Heading/Next) + 3-col Grid. demo - New /uix/components/month-grid and /uix/components/year-grid demo pages with the standard live/api/morfo/sema/recipe/a11y tabs, interactive controls for every public prop, soma+eidos snippets that reactively rebuild from controls, and sema event play buttons. Verified: svelte-check --threshold error -> 0 errors / 0 warnings / 4572 files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago