8 Commits (37fe04693aaf4dcf2937cc2dd1672db15b3e7152)

Author	SHA1	Message	Date
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	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	a74f26728c	fix(sema/verbs): validateEventName longest-prefix-match for multi-word verbs ... The canon includes two multi-word shift verbs: `enter-mode` and `exit-mode`. `validateEventName` was splitting at the first dash and checking the canon for `enter` / `exit` alone — those aren't canon, so legitimately canonical events like `shift-enter-mode` were being flagged as drift. Fixed by matching the longest canonical verb prefix against the tail (family-verb shape) or against the name (bare verb shape). Handles trailing variants too — `shift-enter-mode-edit` recognises `enter-mode` as the verb and `edit` as the variant. Verification: - 1 new test covering multi-word verb shapes; 19/19 pass - `npm run morfo:vocabulary`: 58 → 57 warns (editable.shift-enter-mode no longer falsely flagged), EXIT 0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	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	e6e438b62a	Tighten uix audit contracts	5 months ago
dev	d4dfdaffa9	sema/morfo/eidos: align with GUIA_IMPLEMENTACION_SEMAUIX (canonical guide) ... The new doctrinal guide at src/docs/GUIA_IMPLEMENTACION_SEMAUIX.md supersedes src/docs/sema-implementation-guide.md and locks the canonical vocabulary, event shape and color tokens. This commit aligns the codebase to that canon in three concrete moves. Phase 1 — sema/verbs.ts vocabulary: - Restructured from flat array to family-keyed Record per the guide. - Moved select / toggle / acknowledge → commit (these fix state, not contact). Removed edit from handle (it's shift.enter-mode now). - Added new verbs per the canon: contact (tap, focus, trigger, release), commit (complete, restore, expire, set, remove, reorder), signal (remind), handle (rotate, scroll, reorder), shift (route, step, return, context), sustain (start, loading, waiting, syncing, processing, streaming, pending, retrying, end). - validateEventName now recognises both naming shapes: {verb}-{variant} (head=verb) and {family}-{verb} (head=family). - New helper familyForVerb. Tests rewritten — 16/16 green. Phase 2 — morfo event shape: - target moved from event-level into event.semantic. Adds optional semantic.verb (advisory, validated against SEMA_VERBS[family]) and optional semantic.sequence ('pre' | 'coincident' | 'post'). - compile.ts and schema.ts updated. The 22 events across toggle, toast, popover, drawer, dialog refactored to the new shape with explicit verb + sequence. - Polymorphic capability (allowedFamilies + defaultSemantic) and a11ySemantic deferred — no current consumer needs them; will land when the first concrete usage appears. Phase 5 — color tokens (doctrinal 8): - themes/base/light.css and dark.css rewritten to expose primary, secondary, neutral, affirm, fulfill, risk, threat, loss. Renames success→fulfill, warning→risk, danger→threat (same hex). New primitives for secondary (slate-blue), affirm (teal-mint, low activation), loss (deep violet-grave, posterior). info palette deleted entirely — per guide, "info no es intent, es signal.announce + neutral". - _static.css legacy compatibility aliases (--color-bg, --color-success, --color-error, --color-accent, ...) deleted. Clean cut, no transition. Consumers reference doctrinal palettes directly. - 29 consumers (token files + recipes) migrated: - All --*-color-info-* declarations dropped. - Component palettes extended with secondary / affirm / loss. - switch + checkbox recipes updated to use [data-color='affirm'| 'risk'|'threat'|'secondary'] (was 'success'|'warning'|'danger'| 'info'). - toast tokens + recipe renamed to affirm/fulfill/risk/threat/loss (was success/error/warning/info). - meter, progress, mark, badge, button tokens renamed. - Contracts (contracts/contract.css + contracts/components/*) updated. - focus-ring-color-error in themes now points to --color-risk-border (validation errors are signal.warn + risk per doctrina, not threat). Phase 4 (partial): - src/docs/sema-implementation-guide.md deleted (superseded by the canonical guide). Tests: 217/217 green across uix. npm run check holds at the 39-error baseline (all pre-existing in unrelated test files; none introduced). Pending in follow-up commits: - Update active_architecture.md, sema/README.md, morfo/README.md, CLAUDE.md to reflect the canon. - Switch component migration to the eidos wrapper pattern. - Persistence field (untilAction / untilFix / stateBound) and holds-by-intent — defer until the first signal.warn / signal.alert consumer appears. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a6e2c1e443	sema: align vocabulary with libro_semantica (signal, shift, loss) ... Updates the canonical semantic vocabulary to match the latest formulation in src/docs/libro_semantica_completo.txt: Families (7, was 6): contact, commit, signal, handle, emerge, shift, sustain - `alert` → `signal` (rename: same perceptual function — attention / salience — but the book's name reflects the broader scope including notify, warn, emphasize, announce). - `shift` (NEW, transitional): frame change. Modal mount, navigation, mode change. Differs from emerge in that it reorganizes planes (heavier backdrop, deeper shadow) — "cruce de umbral" not just "aparición". Per book rule, the frame doesn't carry intent on its own; evaluation belongs to a companion `signal` event. Intents (6, was 5): neutral, affirm, fulfill, risk, threat, loss - `loss` (NEW): consummated negative consequence (negative valence, low activation, posterior). Differs from `threat` (anterior, high activation, convokes action): loss registers, doesn't convoke. Per book §11.5 "la amenaza no es la pérdida". sema-map.ts perceptual values: - `signal` family entry: kept the prior `alert` numbers verbatim (semantics is the same — attention/salience) under the new name. - `shift` family entry: motion 260ms ease-in-out 0.98→1, sound pitch 500 ascending gain 0.18 (deliberately quieter than emerge's 0.20 to not compete with companion signal), presence with stronger backdrop (0.5) + shadow (blur 32 y 12 op 0.2) emphasizing plane reorganization. - `loss` intent deltas: descending sound contour (-150 pitch), contraction (scale.to -0.04, motion duration ×0.95 — brief but grave), color toward purple-grave (hue replace 280, lower saturation/intensity), withdrawn presence (backdrop 0.05, no glow). ARIA `role="alert"` (W3C live region) is unrelated and untouched in soma/announce, soma/toast and morfo announce/field/form. The toast morfo gains `loss → role:'status' aria-live:'polite'` mapping — loss is consummated so it shouldn't interrupt. Verbs added per the book's worked examples: signal {warn, notify, emphasize}, shift {enter-mode, exit-mode, navigate}, commit {save, discard, delete}, contact {press, click, hover}, handle {pick, carry, drop}, emerge {reveal, show, hide}. Verified: vitest 9 files / 99 tests, smoke 68/68, morfo-check 66/66.	5 months ago
dev	2e062f216b	sema: canonical action verb vocabulary (SEMA_VERBS) ... Cross-component verb names that morfo `events[].name` should preferably align with. Lets sema / sound / vibra engines subscribe by verb instead of by component-specific event name, and lets eidos write transversal selectors like `[data-event^="dismiss"]`. Vocabulary (24 verbs, grouped by family alignment) - emerge: present, dismiss, open, close, expand, collapse - commit: commit, cancel, confirm, submit, reset, fail - alert: announce, alert - contact: activate, select, toggle - handle: acknowledge, edit, drag, resize - sustain: tick, progress Composite event names follow `{verb}-{variant}` (e.g. `commit-save`, `dismiss-outside`). The verb is the head; the rest is component-specific nuance the validator extracts and reports separately. `validateEventName(name)` returns `{ name, head, matchesCanonical, variant }`. Advisory — doesn't reject morfos, just surfaces drift for tooling / review (a future `sema:vocabulary` script can use it to flag composite event names whose head isn't canonical). Existing event names already align well - Toast: `present`, `announce`, `dismiss` — all canonical bare verbs. - Dialog: `open`, `close-save`, `close-cancel`, `close-dismiss`, `close-dismiss-outside`, `close-after-fail` — all canonical heads (`open`, `close`) with variants. Tests: 10 unit tests covering vocabulary integrity, isSemaVerb guard, validateEventName splitting/matching, and a snapshot of current dialog + toast event names against the catalog (all match). This is the second extension justified under the "2-of-3 rule": verbs are consumed by sema (subscription routing) AND eidos (selector generation), with the original morfo authoring as the third producer.	6 months ago