8 Commits (9e4187bc3c55354eb953ae74e9edca10e986b894)

Author	SHA1	Message	Date
dev	9ca8b4e30b	docs(claude/libro): document persistence + a11ySemantic + polymorphic close rollout ... LIBRO_VARIACIONES_Y_EXTENSIONES.md: - New section D.9 (persistence + holds-by-intent — book §6.1). - New section D.10 (a11ySemantic per event — book §9.1). - New section D.11 (polymorphic events — book §5.3) with the full rollout state across overlays + picker family. CLAUDE.md hand-offs: - 2026-05-27: initial sprint (persistence + a11ySemantic + polymorphic types). - 2026-05-27 #2: caller messages + persistence extension + Dialog refactor. - 2026-05-27 #3: Drawer + Popover polymorphic refactor. - 2026-05-27 #4: Picker family polymorphic refactor + test fixtures decoupling. Each hand-off records: scope, files touched, doctrinal decisions, and pending follow-ups. The whole rollout was verified on 680/680 tests across sema + morfo + soma + adom scopes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	826ca2bf46	docs(sema): add D.8 — channels: qué es canal y qué no ... Doctrina arquitectural sobre límites de los canales runtime: - Canales built-in del framework: sound + haptic (los únicos). - ARIA estructural: declarativo en morfo, NO canal. - ARIA dinámico (live regions): soma escribe directo, NO canal. - Visual (motion / color / presence): eidos CSS via data-event-*, NO canal. - Regla operativa: algo es canal sólo si recibe SemanticSignal, acepta modulación por intent.deltas, y tiene signature paramétrica análoga a sound/haptic. ARIA dinámico falla la modulación. - Channels extensibles: declaration merging del registry; opt-in por app (voice, a11y formal, etc.). Framework no envía ninguno. Cierra una tentación que surgió en D.7 — convertir ARIA en canal era confusión categorial. Esta sección fija los límites para que nadie reincida. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	2d562f3788	feat(sema): Lectura C steps 5-8 — 11 sema packs + doctrina samples ... Step 5 — 3 packs alta-frecuencia (silencio + tap leve): switch, toggle, toggle-group + tuning `form.toggle.silent: { gain: { op: 'add', value: -0.3 } }` Step 6 — 6 packs menús + árboles (emerge.soft / form.commit.subtle): menubar, navigation-menu, dropdown-menu, context-menu, tree-view, tree-grid Step 7 — card scope: KEEP `sema` + `family-default` (sin código). Step 8 — 2 packs (versión lean tras descartar 5 prematuros): tooltip (silent-by-default) collapsible (mirror accordion) + tuning `tooltip.silent: { gain: { op: 'add', value: -0.2 } }` Doctrina codificada en LIBRO_VARIACIONES_Y_EXTENSIONES.md: - D.5 — packs alta frecuencia (toggles) - D.6 — packs superficies menú / árbol - D.7 — sonido canónico vs samples SOUND_LIBRARY = recursos | SOUND_TUNINGS = canon | packs = composición samples NO sustituyen firma con intent.deltas sampleOverlay descartado permanentemente (sobreingeniería) family signal admite excepción para marcas culturales Cierra Lectura C steps 5-8 del audit-codex P1 #3. Total: 11 packs nuevos sobre 9 perfiles canónicos de tuning. 195/195 tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	00f0b740e6	refactor(sema/docs): apply author's evaluation — status classification + intentRequirement/intentGuidance split ... Two changes in one commit: 1. **Doctrina del autor sobre el documento de variaciones** The author evaluated LIBRO_VARIACIONES_Y_EXTENSIONES.md and gave per- entry verdicts. The doc is now rebranded, restructured, and classified: - Renamed: "Registro de desviaciones entre implementación y canon editorial". Disclaimer at top: not the book, internal registry only. - Formal status classification (BOOK_CANON / PROJECT_CANON / CANDIDATE / LOCAL_EXTENSION / DEPRECATED / ALIAS / IMPLEMENTATION_CONTRACT). - Per-entry verdicts assigned per author's evaluation. Author's doctrinal texts included verbatim where given. - A.6 split per verb (was a single bullet for apply/partial/block/ move/upload; now each has its own status: apply=BOOK_CANON, move=BOOK_CANON, upload/partial/block=CANDIDATE). - A.6/A.7 ordering fixed (commit.unselect now A.11 — terminal). - C.3 split into C.3.a (renames mecánicos) y C.3.b (correcciones doctrinales — command intent shift). - E (resumen ejecutivo) actualizado: clear/unselect movidos a resueltos (estaban contradiciéndose). Pendientes reales listados. - F + new section G ("Anti-mezclas") con disciplina sobre el doc. 2. **Family policy: split `intentPolicy` en `intentRequirement` + `intentGuidance`** (D.3 del doc). La policy actual `'allowed' | 'expected' | 'optional'` mezclaba dos ejes que el autor pidió separar: - `intentRequirement: 'required' | 'optional' | 'forbidden'` — compile-time type constraint. - `intentGuidance: 'expected' | 'contextual' | 'discouraged'` — guía doctrinal sin efecto en tipos. Policy nueva: | family | requirement | guidance | |----------|-------------|--------------| | contact | optional | discouraged | (Cap 22 §11) | commit | required | expected | | signal | required | expected | | handle | optional | contextual | | emerge | optional | contextual | | shift | optional | contextual | | sustain | optional | contextual | | delegate | optional | contextual | (Cap 29 §4) `IntentExpectedFamily` deprecated → `IntentRequiredFamily` (alias mantenido). `IntentPolicy` type también deprecated. Consumers actualizados: event.ts (isSemaEvent usa requirement), validation.ts (validateSemaEvent usa requirement), event.test.ts (tests usan ambos campos), dialog.ts (comment doc update). 3. **Bug menor encontrado en `SEMA_TRANSITIONAL_FAMILIES`**: faltaba `delegate`. Añadido. (Era inconsistente con SemaTransitionalFamily type que sí lo incluye.) Verification: - vitest src/uix/sema src/uix/morfo: 195/195 pass - morfo:vocabulary: 7 warns (todos words/*, separate dev track) - EXIT 0 Pendiente futuro (no en este commit): - Añadir flag `emission` a MorfoEvent type per D.2 (eventos declarados pero no emitidos) - Re-evaluar verbos CANDIDATE (acknowledge/confirm/upload/partial/ block) cuando aparezcan más casos de uso Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	bbfefdb63d	refactor(morfo): rename 12 events to {family}-{verb}-{variant} canonical shape (Capa 3 cluster otros) ... Closes the last cluster of name-shape drift in the non-words morfos. 11 are pure cosmetic renames (declared verb already canonical); 1 includes a doctrinal correction. Renames (verbo declarado canónico, solo el name): - carousel.shift-slide → shift-navigate-slide - feed.shift-focus-item → shift-navigate-focus-item - feed.commit-load-more → commit-submit-load-more - file-upload.commit-add → commit-set-add - file-upload.signal-reject → signal-warn-reject - form.signal-invalid → signal-warn-invalid - number-field.handle-scrub → handle-drag-scrub - range-calendar.commit-start → commit-select-start - range-calendar.commit-range → commit-select-range - tags-input.commit-add → commit-set-add - tags-input.signal-reject → signal-warn-reject Doctrinal correction: - command.commit-invoke (declared submit + fulfill) → commit-submit-invoke + submit + AFFIRM (not fulfill) Per book cap. 22 §8 ("Error típico: contact.press + fulfill — esto hace que el sistema diga 'ya terminó' cuando solo ha empezado. Contact inicia. Commit resuelve."), the user submitting a command in the palette does NOT mean the command has completed. Same precedent as Button: celebrate-before-time is wrong. Affirm acknowledges the submission; the command's actual completion (success/failure) fires downstream from whichever morfo owns it. Consumers updated: - sema/components/{file-upload,form,number-field,tags-input}.ts - soma/components/{file-upload,form,number-field,range-calendar,tags-input}/*.ts - sema/resolver.test.ts (event name + data-event selector) Verification: - morfo:vocabulary: warns 19 → 7 (-12), the 7 remaining are all words.* (separate dev track, excluded). EXIT 0. - vitest src/uix/sema src/uix/morfo: 195/195 pass Doc src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md C.3 marked RESUELTO with full list of renames + the command intent correction. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f3641347de	feat(sema/morfo): add commit.unselect to canon + apply to 6 morfos ... User doctrinal decision (2026-05-25): add `unselect` as canonical verb of the commit family. The pair `select` / `unselect` covers results applied on the selection state of an item — distinct from `toggle` (binary control flip) and `remove` (retirement from a collection). Quoting the author: "Seleccionar y deseleccionar son resultados aplicados sobre el estado de selección de un elemento. Eso es commit, porque el resultado queda aplicado. - No es remove: no estás eliminando el item ni sacándolo de una colección funcional; solo estás cambiando su estado de selección. - No es necesariamente toggle: toggle describe mejor el mecanismo binario o el control, pero no expresa tan bien el resultado semántico concreto." Changes: - src/uix/sema/verbs.ts: add `unselect` to SEMA_VERBS.commit after `select` (natural pair). Header comment documents the doctrinal distinction with toggle and remove. - 6 morfos updated: calendar, combobox, grid-list, listbox, select, tag-group. Each changes `commit-unselect` from `verb: 'remove' + intent: 'neutral'` to `verb: 'unselect' + intent: 'affirm'`. Names preserved (already canonical now). Intent `affirm` because "the action applied correctly" (sobrio, not celebratory). - src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md: C.2 marked RESUELTO with the full doctrinal reasoning verbatim. A.3 (remove vs delete) updated to reflect the three-way distinction now formalized (unselect/remove/delete). New A.7 entry for `unselect` itself with "para el libro" note (add to Cap 23 §5). Verification: - morfo:vocabulary: warns 25 → 19 (-6 unselect cluster), EXIT 0 - vitest src/uix/sema src/uix/morfo: 195/195 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	1582572e9b	refactor(morfo): commit-clear → commit-reset across 10 components (cluster clear resolved) ... User directive: clearing a field is `commit.reset` per book cap. 23 ("vuelve a estado inicial") — fits all 10 components in the cluster since each goes back to empty-initial-state, not discarding meaningful defaults. Components updated (morfo + soma trigger + sema cascade + test): - color-picker, date-field, date-picker, date-range-picker - file-upload, range-calendar, tag-group, tags-input - time-picker, time-range-picker range-calendar.commit-clear was declaring `verb: 'remove'` — corrected to `'reset'` along with the name change. All event names now: `commit-reset` (family commit, verb reset, intent neutral). No variant suffix needed; no ambiguity of multiple resets in any single component. words.commit-clear excluded — separate dev track. Doc updated: src/docs/LIBRO_VARIACIONES_Y_EXTENSIONES.md C.1 marked as RESUELTO with author's disposition. Verification: - morfo:vocabulary: warns 35 → 25 (-10), EXIT 0 - vitest src/uix/sema src/uix/morfo + tag-group tests: 199/199 pass Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	670c54177d	docs: document deviations from the book canon (LIBRO_VARIACIONES_Y_EXTENSIONES.md) ... Inventory of every place the UIX project canon diverges from, extends, or interprets «Diseñando lo que ocurre» beyond its literal lists. For each entry: book reference, decision taken, argument, and a pending question for the author to evaluate. Six categories: - A. Verbs added to canon beyond book's literal lists (handle.scroll, commit.acknowledge, commit.remove, commit.confirm, commit.set, commit.apply/partial/block/move/upload) - B. Interpretive adoptions not literally in the book (drag cancellation, programmatic scroll, data resize, sort, auto-revert states, toggle phases, contact intent as visual-only) - C. Open doctrinal questions (clear, unselect, ~19 individual events) - D. Architectural decisions relevant to the book (composition over overload, declared-but-not-emitted events, family policy nuance) - E. Executive summary - F. Disposition options for the author (accept, reject, reformulate, keep as local extension) Author can use this to decide what passes to the book vs what stays as project extension. Until disposition, this doc is source of truth for deviations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago