5 Commits (540c35e67967f89a095bfdc471e9507f740c45de)

Author	SHA1	Message	Date
dev	e6e438b62a	Tighten uix audit contracts	5 months ago
dev	6da109875d	Prune legacy Eidos CSS runtime	5 months ago
dev	e6862265e2	sema/morfo/eidos: typed selector builder + dialog wrapper + emerge color ... sema architecture - sema-map: 5-channel registry (motion / sound / color / presence / haptic) via SemaChannelSignatures declaration merging; engine stamps data-event-* tokens; flat CSS-style cascade replaces the eventLabel-overrides middle layer. - sema-map: emerge family gains base.color so intent deltas can shift hue / saturation / intensity. Without a base, the resolver was skipping the channel and Dialog open with intent='threat' rendered as neutral blue in the Sema tab visualisation. - types: SEMA_FAMILY_POLICY const drives compile-time + runtime intent requirements per family. Object shape so future per-family policy fields fit alongside. Emerge events MAY now declare intent (canon update — a Dialog confirming threat carries it in its very appearance). - chans: rename vibra→haptic, add HapticChannel V1 (Vibration API); SoundChannel eager-init on first user gesture (autoplay race fix). morfo selector discipline - morfo/selectors.ts (new): semaSelector(morfo, partKebab, matchers?) — type-checked against morfo.parts and morfo.events. Sema cascade rules MUST use it; hand-written strings are an architecture violation that breaks silently when morfo renames a part. - dialog morfo: open carries intent via fromProp; close-cancel / close-dismiss / close-dismiss-outside drop intent (cancellation has no evaluative load); close-save stays hardcoded fulfill (commit fulfils the user's decision regardless of dialog context). eidos dialog migration (4th pilot) - eidos/components/dialog/: full subdirectory wrapper — flat <Dialog> + compound Provider/Trigger/Overlay/Content/Title/Description/Close/Header/ Footer; size + position responsive props; sheet auto-form on narrow viewports; closePosition for the auto-X. - sema/components/dialog.ts: cascade rules use semaSelector(dialogMorfo, 'content', matchers?). Intent block adds character (haptic kind / pattern) but never overrides pitch / gain / contour — those are intent.deltas signature ownership and overriding flattens per-intent perceptual difference. demo controls + dialog page - src/lib/_demo (DemoSwitch / DemoEnum / DemoText / DemoRange) — unified controls reused across all component demos. - web/routes/dialog: live preview always rendered above tabs; per-event Sema tab with independent intent probe; signature visualisation + Play buttons with fallback target chain. documentation - CLAUDE.md: intent.deltas signature ownership rule; eidos drift defense doctrine (types over lint); 2026-05-09 hand-off entry. - morfo/README: Typed selector builder section. - eidos/README: linter section reframed as opt-in safety net for plain CSS recipes; the architectural mechanism is compile-time typing. - sema/README: open channel registry + flat cascade docs + override semantics + intent policy const + selector builder discipline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	29ce812f94	collapsible: flat <Collapsible> ergonomic default + compound parts ... Per the doctrine update in GUIA §13: eidos for multi-part components exposes BOTH a flat default that auto-composes Provider/Trigger/Content AND the compound parts for advanced cases. Soma + morfo remain the universal composable foundation underneath. Why: with the previous "compound only" rule for multi-part, eidos collapsible was a pure pass-through that added nothing operational — the consumer wrote the same import + same shape as soma. The flat default makes eidos earn its layer by collapsing the 90% case to a single call: // 90% case — flat ergonomic <Collapsible bind:open> {#snippet trigger()}Show details{/snippet} <p>Body content.</p> </Collapsible> // Advanced — compound (parts in different subtrees, multi-trigger, // conditional content) <header><Collapsible.Provider bind:open> <Collapsible.Trigger>Show</Collapsible.Trigger> </Collapsible.Provider></header> <aside> <Collapsible.Content>...</Collapsible.Content> </aside> The architectural virtue: if the flat doesn't fit, a developer drops to soma + morfo and composes freely. No vendor lock-in in the visual layer; eidos is the design system convention, soma is the universal primitive. Files: - src/uix/eidos/components/collapsible/collapsible.svelte (NEW): flat default that auto-composes Provider + Trigger + Content via a `trigger` snippet for the toggle label and `children` for the body. - src/uix/eidos/components/collapsible/types.ts: adds `CollapsibleFlatProps = SomaCollapsibleProps & { trigger?: Snippet }`. - src/uix/eidos/components/collapsible/index.ts: exports `default` (flat) plus named `Provider`/`Trigger`/`Content` (compound). - src/uix/eidos/components/collapsible/{trigger,content,provider}.svelte: fixed children destructuring so snippets propagate cleanly to soma (was previously spreading $props() blindly which can lose snippet bindings in Svelte 5). - src/docs/GUIA_IMPLEMENTACION_SEMAUIX.md: NEW §13 "Doctrina del API: soma compound, eidos opinionado" formalises the two-shape rule and the architectural virtue (soma+morfo as universal foundation). Renumbered §13/§14 → §14/§15. - web/routes/collapsible/+page.svelte: live preview now uses the flat form; eidos snippet shows the flat shape; soma snippet keeps the compound shape; Notes tab updated. - src/uix/eidos/components/collapsible/README.md: rewrote API section with both shapes + the "if neither fits, use soma+morfo" escape. Tests 218/218 green. npm run check baseline 39. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	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