9 Commits (29ce812f9492baadcb75bb54c3dcda03f585e955)

Author	SHA1	Message	Date
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	d1850a7de4	demos/collapsible: add soma snippet alongside eidos in Live tab ... The collapsible demo only rendered the eidos snippet, which made the "compound shape is the same" doctrinal point invisible: a reader couldn't see that soma and eidos expose the same multi-part API, differing only in import path and what each layer guarantees. Now both code blocks stack in the Live tab: - soma: includes the `<script>` boilerplate (`let open = $state(false)`) to make the headless/structural-only nature explicit - eidos: same shape, different import, no setup boilerplate (consumer binds open directly with `onOpenChange={handleChange}` for the demo trace) Per doctrine §10, only single-part components (toggle/switch) get a flat default export — multi-part keeps compound on both layers, so the two snippets share shape. That's correct. The DIFFERENCE is the import path, the visible boilerplate, and what each layer adds (soma: structural contract; eidos: same surface + recipe CSS). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a9ad71118b	fix: dark mode + collapsible demo layout shift ... Two real bugs reported on the collapsible demo: 1. **Dark mode broken across all migrated components.** - The docs site layout sets `document.documentElement.dataset.theme = 'light'|'dark'` — those are the selector names the docs CSS uses. - The eidos themes (themes/base/{light,dark}.css) only respond to `[data-theme='base-light'|'base-dark']`. Different namespace. - Result: docs grays swap in dark mode but eidos doctrinal palette (primary/secondary/neutral/affirm/fulfill/risk/threat/loss) stays in light values, so component text renders dark on dark. - Fix: each eidos theme now accepts BOTH selectors. `[data-theme= 'base-light'], [data-theme='light'], :root { ... }` and equivalent for dark. Existing consumers that use `base-*` keep working; the short `light/dark` aliases handle the docs site convention. 2. **Collapsible trigger jumps from center to left when expanded.** - The preview-stage uses `display: flex; justify-content: center; align-items: center;` — natural for buttons/switches that don't grow. - `Collapsible.Provider` is `display: block` so it shrink-fits its content as a flex item. Closed = trigger-width (centered visually); open = trigger + content width (longer, so the visual center anchors trigger at the left edge). - Fix: collapsible demo overrides the preview-stage style with `justify-content: flex-start; align-items: flex-start` and wraps the provider in a `max-inline-size: 32rem` panel. Disclosure ergonomics need anchor-left + grow-down, not center. - Also swapped the body's `--gray-50` (docs site token) for `--color-surface-raised` + `--color-content-primary` (eidos doctrinal tokens) so the panel inherits the dark-mode swap. npm run check holds at the 39-error baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	d10281bc94	collapsible: migrate to eidos wrapper pattern (third pilot) ... Third component migrated to the eidos wrapper subdirectory pattern, following the new "check air baseline first" discipline. Air baseline recovered from commit 0a391408^: - air/components/collapsible: 3 wrappers (Provider/Trigger/Content) with `class` passthrough, `bind:open`, `onOpenChange`, manual `air.interaction.play('expansion', enter|exit)` perceptual emit. - No size, intent, color, or chevron slot. Migration decisions (presented BEFORE coding per scope-approval rule): - Two doctrinal events (`expand` + `collapse`, both emerge family, sequence='pre', no intent — emerge is transitional). Replaces air's manual `air.interaction.play` with `runtime.trigger('expand'| 'collapse')` which atravieses visual + sound + vibra channels. - No intent/color/size — air didn't have them and disclosure is non-evaluative per guide §3.1. - Multi-part API: Provider + Trigger + Content (no flat default per doctrine §10). Files: - src/uix/morfo/components/collapsible.ts: scope expanded to ['soma', 'sema'], events array added with two emerge events. - src/uix/soma/components/collapsible/collapsible-provider.svelte.ts: runtime.events handlers `expand`/`collapse` mutate state; toggle() fires runtime.trigger(next ? 'expand' : 'collapse'). - src/uix/eidos/components/collapsible/{collapsible.css, collapsible-provider.svelte, collapsible-trigger.svelte, collapsible-content.svelte, types.ts, index.ts, README.md}. - src/uix/eidos/components/collapsible.css (legacy flat) deleted. - src/uix/eidos/index.css: import path updated to subdirectory. - web/routes/collapsible/+page.svelte: full interactive testbed with tabs (Live, Soma, Morfo, Sema, Eidos, Notes) mirroring switch's structure. Sema tab shows per-channel signature cards for both expand and collapse events. Disciplina formalizada en CLAUDE.md hand-off + memory entry: "Check air baseline first" before any future eidos migration. Switch shipped without this check and lost ResponsiveProp<Size> (regression). Don't repeat with collapsible/dialog/drawer/popover/toast/avatar. npm run check holds at the 39-error baseline. Tests 218/218 green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	48b646ecc4	demos/switch: full Sema tab visualisations matching toggle ... The earlier switch demo Sema tab was a stub linking to the toggle docs page. Now it ships the full per-channel signature cards (motion preview with x8 amplification, sound spectrum bars, color affects, presence preview), the live intent picker, and the Play button that fires on the live switch via uix.semantic.emit. Mirrors the structure used in toggle so the two pilots stay symmetric for future migrations. The play-button targets data-switch (was data-toggle in the toggle demo). The intent-picker drives the same `intent` state that the soma-driven recipe consumes through data-color, so Play replays motion + sound + the data-color theme on the actual track without flipping state. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	4d26761263	docs + switch: align active docs to canon, migrate switch to eidos wrapper ... Phase 4 (docs alignment with the canonical guide): - active_architecture.md — Dialog example refactored to the new event shape (target inside semantic, explicit verb + sequence). Verbs table grouped by family with the post-canon vocabulary (select/ toggle moved to commit, edit removed from handle, new verbs added). Section 10 (Estado actual) updated to 2026-05-08 with current progress: doctrina cerrada, eidos en producción, SoundChannel eager-init, switch migrated, etc. "Para profundizar" §14 points at the canonical guide. - morfo/README.md — Step 5.5 added covering the doctrinal event shape with all fields (semantic.family, .verb, .target, .sequence, .intent) and the two naming shapes ({verb}-{variant} and {family}-{verb}). - sema/README.md — verbs section restructured to Record-by-family matching the runtime; documents the verbs that moved between families per the canon. Naming shapes section updated with both forms and validateEventName signature. - CLAUDE.md — "Session hand-off" rewritten with the post-canon state. Pointer at GUIA_IMPLEMENTACION_SEMAUIX.md as the canonical source. Pending list refreshed: switch is the immediate next component, persistence/a11ySemantic/polymorphism deferred until real consumers appear. Switch migration to the eidos wrapper pattern: - morfo/components/switch.ts — adds events: [{ commit-toggle }] with the doctrinal shape (verb=toggle, sequence=post, intent fromProp binding to the 4 supported intents). New data-* (data-color with the 6-token Toggle/Switch subset, data-readonly, data-invalid, data-required) and corresponding aria-*. scope expanded to ['soma', 'sema']. - soma/components/switch/types.ts — adds intent, color, readonly, invalid, aria-labelledby props with full JSDoc. Subset constrained per guide §3.1 (Toggle/Switch row). - soma/components/switch/switch-provider.svelte.ts — runtime-direct, Field integration via FieldProvider.get(), isDisabled/isReadonly/ isRequired/isInvalid OR-merge derivations, intent ↔ color resolution (intent wins when evaluative), runtime.trigger( 'commit-toggle') in onclick. - soma/components/switch/components/switch.svelte — wires the new props through bindProps. - eidos/components/switch/{switch.css, switch.svelte, types.ts, index.ts, README.md} — full subdirectory pattern, mirroring toggle. Recipe drops legacy success/warning/danger/info selectors; declares the 6 doctrinal data-color values directly. Wrapper auto-renders Switch.Thumb inside the track and exposes an optional `thumb` snippet for in-thumb glyphs. - eidos/components/switch.css (legacy flat) deleted; eidos/index.css updated to import the subdirectory recipe. - web/routes/switch/+page.svelte — interactive testbed with all soma props as live controls + tabs (Live, Soma, Morfo, Sema, Eidos, Notes). Mirrors toggle's structure. npm run check holds at the 39-error baseline. Tests 217/217 green. Pending: - Migrate collapsible / dialog / drawer / popover / toast / avatar to the eidos wrapper pattern. - Persistence + holds-by-intent — defer until first signal.warn / signal.alert consumer. - a11ySemantic + polymorphic events — defer until concrete need. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f5a2a7fb49	eidos: pilot wrapper pattern + doctrinal API conventions ... Toggle as the eidos pilot: subdirectory layout (recipe + Svelte wrapper + types + index + README) replacing the flat CSS-only form. Pattern is documented in eidos/components/README.md and the toggle README. Shared types live in eidos/lib/types.ts. First export is `Size` (8 values xxs..xxl + full); components narrow with `Extract<Size, ...>` per the per-component-subset doctrine. No `Eidos` prefix on types — module path already conveys the layer. API doctrine: - soma stays compound (Toggle.Provider) for symmetry with multi-part - eidos exports both default + Provider so single-part components accept both `<Toggle>` (ergonomic) and `<Toggle.Provider>` (compound-style consumers) SoundChannel eager-init fixes the autoplay race: AudioContext is created + resumed synchronously on the first user gesture (capture-phase listener registered in the constructor), avoiding the previous race where the first emit() scheduled the resume in a microtask outside the gesture window. Demo page (web/routes/toggle/+page.svelte) restructured so the live preview renders ALWAYS above the tablist — Sema-tab Play buttons can fire on the real toggle. Motion preview amplifies scale ×8 visually only; doctrinal values stay in the <dl>. Conventions 7-13 added to src/docs/sema-implementation-guide.md covering: directory structure, wrapper composition, no Eidos prefix, soma compound vs eidos flat, iconOnly sr-only body, sound eager-init, docs-preview amplification. CLAUDE.md gets a session hand-off block listing where things stand and next concrete steps (migrate switch/collapsible/dialog/drawer/popover/ toast/avatar; wire topbar sound mute to masterGain; rename theme tokens to drop the success/warning/danger fallback aliases). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	4546e448bd	demos: web/routes/* for the 8 migrated soma components ... First demos under the new web/routes location (configured by phase C of the cleanup as `kit.files.routes`). One demo per component: toggle, switch, collapsible, avatar, dialog, drawer, popover, toast. Layout (web/routes/+layout.svelte): - Bootstraps the UIX via createActiveUix({ lang: { schema: {}, defaultLocale: 'es' } }) — minimal config, full UIX surface. - Wraps in <Uix> which sets the active-uix context and creates the Soma scope so providers can require it. - Imports the eidos index.css so the visual layer is applied. - Tiny demo-only stylesheet (web/routes/layout.css) for the page chrome (topbar, demo grid, sections) — explicitly NOT part of eidos. Each demo page exercises the public API: - toggle: bound, initially-pressed, disabled - switch: bound, disabled - collapsible: bound show/hide, disabled trigger - avatar: loaded, error fallback, delayed - dialog: basic with overlay + focus trap + escape dismissal - drawer: right / left / bottom (with handle) - popover: click + hover trigger - toast: 4 intents (fulfill, risk, threat, neutral) via createToaster Verified end-to-end with scripts/demo-probe.ts (Playwright): - All 9 routes (landing + 8 demos) serve 200. - Zero console errors except avatar's pravatar.cc network failure (sandbox limitation, not a real bug). - Interactive checks: dialog open shows modal + overlay backdrop + focused Cancel button; popover open positions floating content next to trigger; toast Fulfill shows the green-tinted shadow driven by data-event-intent='fulfill' from sema's visual channel reacting to the morfo's announce event semantics — confirms the full morfo → sema → eidos pipeline works end-to-end on a migrated soma component. scripts/demo-probe.ts: small Playwright runner that loads each route, captures console errors, takes a screenshot of the static state, then clicks the trigger on dialog/collapsible/popover/toast for a second "open" screenshot. Output goes to g:/tmp/demos/. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8e800031fe	cleanup phase C: reconfig SvelteKit + aliases + web/routes skeleton ... svelte.config.js / vite.config.ts: - Drop dead aliases: \$lib, \$glob, \$langs, @/ling, @/logr, @/glob, @/actx, @/uiux, \$terra (their target dirs were removed in phase B). - Add \$reactive at the top level (was previously hidden under the "legacy" block; the target src/libs/reactive is current). - Set kit.files.routes to "web/routes" — demos move out of src/ and will be re-authored from scratch alongside the new architecture. - vite.config.ts: extract the alias map into a single `aliases` const shared by both Vite resolve and the server-test project, instead of duplicating it. web/routes/+layout.svelte + +page.svelte: minimal SvelteKit boot so `npm run dev` and `npm run build` find a routes tree. Real demos (active-uix, soma, morfo, sema, eidos) will be added as sibling routes once the runtime is wired. Verified: `npx svelte-kit sync` regenerates .svelte-kit/tsconfig.json without any of the dead aliases. .svelte-kit/types/web/routes/ is populated, confirming the new routes path is active. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago