74 Commits (08f2d82d94d026869d9edf2b1bf29473566a3b06)

Author	SHA1	Message	Date
dev	08f2d82d94	fix(words): one sans across all chrome — kill the mixed-typeface inspector ... The inspector mixed THREE fonts: labels in Lora (serif!), titles in system-ui, inputs in Instrument Sans. Root cause: eidos's "content" archetype (Accordion content) maps to the reading serif, and the inspector's `[scope] *` rule is only (0,1,0) — equal to the component's `[data-x]` font rule — so the Phase 3 code-split flipped the load order and the serif won. Fix: a `--words-chrome-font` token (= --font-ui, independent of the content `font-family` a theme may set to serif) + a rule forcing it across EVERY chrome surface (toolbar·bubble·slash·drawer·inspector·gutter menus) with a DOUBLED scope attribute (0,2,0) that beats any single-attribute component font regardless of code-split order. Verified in browser: all chrome = Instrument Sans (was Lora/system-ui/Instrument). Content keeps its reading font. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	ec77ec5a0b	refactor(words): prune 55 orphan recipe tokens — eidos suite green (Phase A) ... The words recipe declared a token vocabulary the CSS never used (the root of the drift). Pruned 55 declared-but-unused tokens: 38 direct (gap-*, toolbar-* ×9, button-size-*, command-*-hover, content-px-*, status-*, rail-*, selection-color, _accent-* ×5, line-height, max-inline-size, heading-font-size, content-py-after-placeholder) + 17 cascaded (the intent palette *-solid/ *-solid-hover/secondary-* slots that only fed _accent-* — callouts use the tinted track/border/text slots, kept). No wire candidates (rail had no consumer; ::selection already uses wash-soft). The recipe contract now matches actual usage → the orphan test goes green; full eidos suite 197/197 (all 3 words failures now fixed across increments 1/3/A). Visually inert: words.css references nothing removed (the "declares every var" test guarantees it). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	059f36d2fe	refactor(words): unify radius scale (audit increment 2) ... The small-control radius was a soup of 8 syntaxes for the same thing: 4px / var(--radius-2,4px) / 3px / even var(--space-1) (a spacing token used as radius). Added --words-radius-xs (= --radius-sm, 4px) — the missing small-control step under sm — and snapped all of them to the --words-radius-{xs,sm,md,lg} scale. Micro decorative radii (1-2px) and circles (50%) left as-is by design. Verified radius-xs=4px, editor renders, no regression. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	54d1f658ab	refactor(words): wash scale + token contract fix (audit increment 1) ... Kills the biggest visual-inconsistency soup: 18 ad-hoc color-mix opacities (4/6/8/12/14/16/22/30/35/40/45 %) collapsed to a 4-step canonical scale --words-wash-{faint,subtle,soft,strong} (6/16/30/44 %), applied across words.css; geometry %s (circles, widths) untouched. Hardcoded transition/ animation durations (120/140/100 ms) collapsed to --words-transition-duration. Declared the 2 used-but-undeclared tokens (--words-font-size-xs, --words-swatch) → the "declares every public var" recipe test goes green (1 of 3 words failures fixed). Editor verified in browser, no regression. See components/words/AUDIT.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	95be3b6cb1	perf(eidos): prune base.css to role-referenced scales (Phase 5) — −18 KB gz ... base.css shipped all 31 Radix donor scales, but the theme's roles only reference 9 (gray green indigo orange plum purple red slate teal). The other 22 were dead weight on every page: no component references raw --scale-* (they use --color-{role}-*), and runtime theming builds from JS scale data and writes RESOLVED values (build-scheme: variables[k]=hex), so it never reads the CSS scale tokens. renderThemeCss now emits only role-referenced scales by default; the full 31-scale donor palette ships opt-in in generated/palette.css (new renderColorPaletteCss). The CSS contract stays the full vocabulary (apps can still override any scale; load palette.css to use the extra 22). base.css 53.7→35.4 KB gz. Monolith (every page) 54.4→36.2 KB gz — combined with Phase 3, 113.5→36.2 KB gz total (−68%). Verified: roles resolve (primary=purple, button bg correct), pruned scales empty on regular pages, restored on /temas/color via palette.css. Updated the contract test to verify coverage against the full palette. check clean (13 errors are untracked heroscrolling demo + gitignored tmp/lexical); eidos suite at baseline (192/195, 3 pre-existing words failures). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	7255a52a0a	feat(eidos): shape Fase 3 — eventful corner morph (the differentiator) ... Shape becomes a two-moment channel: resting form (Fase 1) + the morph (event). Folded cross-modally into the existing `press-squeeze` contact firma — one press now drives scale (motion) + shadow-flatten (depth) + corner-firm (shape): the `continuous` corner squares up at the press peak (--shape-smoothing 2 -> 3 -> 2). - `@property --shape-smoothing { syntax: <number>; inherits: true }` so the number interpolates smoothly (mirrors the motion @property pattern). - Set only at the keyframe peak -> interpolates from/to the element underlying smoothing (respects a theme override). No-op for non-continuous corners (they do not read --shape-smoothing). Degrades with reduced-motion via the firma system. Material 3 Expressive is the only other system with shape morph (bespoke, closed); this rides the unified firma — one event, many modalities. Verified: check 0 errors; eidos config+motion+generated 78/78. Regenerated base.css. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	e04c098787	feat(eidos): shape Fase 2 — concentric nested-radius harmony ... `--shape-nest-gap` token + `[data-shape-nest]` rule: a nested element derives `border-radius: max(0px, var(--shape-outer-radius) - var(--shape-nest-gap))`, so its corners stay parallel to the parent (concentric). The parent exposes its radius via `--shape-outer-radius` (inherited); gap defaults to the nest token. nestGap is optional on ShapePrimitiveSet (a shape system can omit nesting); the token + rule are gated on its presence. Only SwiftUI (recent, platform) has concentric corners — none on the web as a token rule. Verified: check 0 errors; eidos config+generated 55/55. Regenerated base.css. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	7e26608ee0	feat(eidos): shape engine — Fase 1 (continuity + families) + SHAPE_ENGINE_RFC ... The 8th book channel (forma) — the one no web design system has elevated. Fase 1 lays the foundation: corner continuity + perceptual families as portable tokens. - ShapePrimitiveSet (config-driven): `smoothing` (superellipse exponent, 1=arc -> 2=squircle) + `families` map. STATIC_SHAPE ships rounded/continuous/cut/scoop. - Emission: `--shape-smoothing` token + `[data-shape=`{family}`]` rules setting `corner-shape` (round / superellipse(var(--shape-smoothing)) / bevel / scoop). Opt-in: magnitude stays in `--radius-*` (untouched), so corners degrade to the plain border-radius arc where `corner-shape` is unsupported (progressive, like the wide-gamut oklch of color). var() works inside superellipse() (Chrome 146). - Validation (validateShapePrimitives) + 2 tests + regen. Why it matters: the whole web field (Tailwind/shadcn/Chakra/Mantine/Ant/Radix Themes/Carbon/Fluent/Spectrum/Polaris/Primer) is "radius scale + circular arc + static". Continuity exists only in Apple (platform-locked); none on the web ships squircle as a token. This is the first. Verified: npm run check 0 errors; eidos config+generated 54/54. data-shape applies in the live runtime (continuous->squircle, cut->bevel, scoop->scoop). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	6998c5bde2	feat(eidos): depth Fase 4 — atmosphere (frost) + applyDepth runtime builder ... Closes the depth channel. Atmosphere as the channel's materials layer: - Per-plane `blur` cue (overlay 10px, modal 16px) + an opt-in frost rule `[data-depth=`{plane}`][data-frost]` -> translucent surface (color-mix 80%) + backdrop-filter blur. Gated on data-frost so it never turns an opaque overlay translucent by default; specificity 0,2,0 reliably overrides the component bg. - buildDepth(planes) (pure) + ActiveEidos.applyDepth/clearDepth — retune any plane cue (surface/shadow/halo/blur/scrim/z) at runtime, the depth sibling of applyColorScheme / applyTypeScale. Exported from $uix/eidos. Showcase: /temas/profundidad section Materiales — a frosted-glass panel over a vivid color mesh (frost blur + shadow + halo). The `scrim` cue stays an available token without a wired rule — modal backdrops are component-managed. Verified: npm run check 0 errors; eidos 185/188 (3 pre-existing `words` failures, unrelated). New tests: frost emission + applyDepth. Regenerated generated/base.css. Docs: DEPTH_ENGINE_RFC Fase 4 + token contract, THEMING 29. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	271a2f8ff0	feat(eidos): depth adoption — elevated components consume the channel (shadow + halo) ... The Fase 2 rim halo now reaches real UI, not just the showcase. Each elevated component's shadow signal (recipe tokens in recipes/base.ts + the few direct box-shadow uses) now composes `var(--depth-{plane}-shadow), var(--depth-{plane}-halo)`. Reaches: popover, dialog, drawer, dropdown/context/navigation-menu, menubar, select, tooltip, card, combobox, command, link-preview, words. Shadow signal only — z-index stays component-managed (the z bands are finer than the 5 planos), so zero stacking risk. Verified: dialog keeps its own z-index 71 and composes drop shadow + oklab halo. Retuning a plane now retunes every component on it. Verified: npm run check 0 errors; eidos 183/186 (3 pre-existing `words` failures, unrelated). Regenerated generated/base.css. THEMING 29 updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	0e0fbc05d7	feat(eidos): depth Fase 2 (oklab rim halo) + reference-grade /temas/profundidad ... Depth engine — Fase 2 (mode-adaptive mezcla): - New `halo` cue per plane: a top-edge rim-light computed in oklab (color-mix(in oklab, white N%, transparent); 5/7/8% on raised/overlay/modal). The `[data-depth]` box-shadow now composes `shadow, halo`. Invisible on light surfaces (the drop shadow leads), the lift cue on dark surfaces (where the drop shadow barely shows) — the mode-adaptive answer to "shadow lies in dark", scoped to the depth channel (global --shadow-* untouched). - Wired through config-types (DepthPlane.halo) + render-css (declare + compose) + config validation + STATIC_DEPTH + regenerated generated/base.css. Showcase — /temas/profundidad to reference depth (4 -> 9 sections): matches Material elevation catalog breadth and adds the two axes it lacks (eventful + open cage): - Responde a cada estado — dynamic elevation, live interactive control - La escalera de planos — z-stack of the 5 planes - Catalogo de planos en reposo — the resting-elevation spec table, our vocabulary - Luz vs sombra — light/dark side-by-side showing the halo mechanism - Accesibilidad — never the only channel, reduced-motion, forced-colors, contrast - Fix: mirror data-theme onto <html> so :root depth tokens stay mode-aware Docs: DEPTH_ENGINE_RFC (Fase 2 + 5 done, token contract + halo), THEMING 29. Verified: npm run check 0 errors; depth tests 50/50 (updated the box-shadow assertion to the shadow,halo composition). Pre-existing `words` recipe-contract failures unrelated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	a289ce666f	feat(eidos): depth engine — Fase 3 (canal eventful / momento-evento) ... The novel core: depth as something that OCCURS. The elevation dimension now lives in the event firma (the two-moment model event moment) — leveraging the existing signature system, NOT a parallel one: - present-rise (emerge): the box-shadow grows from flat -> the element resting plane shadow as it rises. A flat element (no resting shadow) is a no-op; a raised/overlay element animates its elevation proportional to ITS plane. - press-squeeze (contact): the shadow flattens to the surface at the press peak, then returns (recede). So depth + position/scale + sound + haptic all fire coordinated from one event. Degrades with reduced-motion (the global events.css cap); a theme overrides the keyframes/signatures (jaula abierta). No reference framework treats depth as eventful. Fase 2 (computed mode-adaptive shadow mix) deferred — the shadows are already mode-aware, so it is a refinement, not a gap (documented in the RFC). Verified: check 0 errors; motion + config + generated tests pass; browser — the present-rise keyframe is live with the box-shadow dimension. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	290f5d0c12	feat(eidos): depth engine — Fase 1 (plano unificado) + DEPTH_ENGINE_RFC ... Arranca el sprint de profundidad: depth como un plano unificado, config-driven y semántico — la base del canal "la profundidad es algo que OCURRE" del libro (el disparo eventful por sema llega en Fase 3). - DEPTH_ENGINE_RFC.md — la guía de diseño: estudio de los límites de los referentes, la tesis novel, y la doctrina "default fuerte, jaula abierta". - EidosConfig.depth.planes (DepthPlane + DepthPrimitiveSet). Set canónico: flush · raised · overlay · modal · recessed — cada uno COMPONE los primitivos existentes (surface/shadow/z), sin matemática nueva → cero rotura. - emite tokens --depth-{plane}-{cue} + reglas [data-depth='{plane}'] que aplican las señales aditivas seguras (box-shadow + z-index); surface + blur/scrim quedan como tokens opt-in (no pisan fondos de componente). - validado; config-driven (un tema añade/retunea planos — jaula abierta). - arregla un punto y coma latente en la emisión de variable-fonts, cazado aquí. Verificado: check 0 errores; tests nuevos (emisión canónica + plano custom); generated/base.css regenerado; navegador — data-depth='overlay' aplica la sombra overlay + z 400, 'recessed' aplica una sombra inset. (3 fallos de words pre-existentes.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	ecc514951f	feat(eidos): typography component props (Phase 3b) — wrap/tracking/leading/numeric/measure ... Wires the Phase 3 scales into <Text> and <Heading> + fixes a token collision the scales introduced. - Text/Heading props (additive): `tracking` / `leading` (reuse the existing --_x-letter-spacing / --_x-line-height vars → override the size-derived values), `wrap` (text-wrap: balance/pretty/nowrap), `numeric` (tabular/oldstyle → font-feature-settings), `measure` (max-inline-size). Heading defaults to `text-wrap: balance` (reference-grade titles); Text defaults to the CSS initial so the axes are no-ops until a prop is set. Heading reuses Text's scale unions. - COLLISION FIX: Phase 3a's config-driven --tracking-{tight,normal,wide,wider} collided with a pre-existing HARDCODED tracking scale in render-css (semantic badge/ui/… + scale tight/normal/wide/wider, all 0) emitted later → it won (everything resolved to 0, so the tracking prop did nothing). Removed the hardcoded scale lines; the config (typography.tracking, real optical values) now owns tighter/tight/normal/wide/wider. The semantic tracking tokens (badge/label/ui/prose/heading/display) stay (recipes use them, e.g. card-title --tracking-tight now picks up the real -0.02em). leading/features /measure don't collide (distinct keys). Verified in browser: tracking-wide 0.02em -> 0.32px; tracking-tight -0.02em -> -0.32px; heading default text-wrap balance; wrap=pretty, numeric=tabular, measure, leading all apply. check 0 errors; eidos suite green (3 pre-existing words failures only). Note: the pre-existing hardcoded semantic typography block (leading-ui/prose/… + tracking-badge/…) is still hardcoded, not config-driven — a separate cleanup. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	d85c2fd376	feat(eidos): typography scales — tracking/leading/features/measure + optical tracking (Phase 3a) ... TYPOGRAPHY_ENGINE_RFC Phase 3 (engine tokens). Additive scales, pure CSS, no binaries. - config-types: TypographyPrimitiveSet += tracking / leading / features / measure (optional Record<string,string>). - render-css: emits --tracking-{k} / --leading-{k} / --font-feature-{k} / --measure-{k}. - typography.ts defaults: tracking (tighter…wider), leading (none…loose), features (tabular = "tnum"+"lnum" for data, oldstyle/smallcaps/ligatures), measure (54/66/78ch). + optical tracking baked into the size tokens: small text slightly looser (xxs +0.01em), display tighter (xxxl -0.02em) — was all 0. - config.ts: validates the 4 scales (CSS-value maps). - generated/base.css regenerated. test: scales + optical tracking emission. Additive tokens (recipes/components consume var(--tracking-tight) etc.) so the scales are zero-risk; the only rendered change is the gentle optical tracking on headings/small text. check 0 errors; eidos suite green (3 pre-existing words failures only). Next (Phase 3b): wire the component props (wrap: balance/pretty, numeric: tabular, tracking/leading/measure) on <Text>/<Heading>. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	f53299d42b	feat(eidos): config-driven @font-face (Phase 2) — fonts as theme data (next/font model) ... TYPOGRAPHY_ENGINE_RFC Phase 2. Fonts are theme data (each theme owns its families), so @font-face becomes config-driven + generated — like the color palette — instead of a separate hand-written CSS file. This matches next/font / Fontaine (config -> @font-face), above the token-only frameworks (Radix/Tailwind/MUI) that leave loading to you. - config-types: FontFamily += faces (FontFace[]) / axes (FontAxes) / fallback (FontFallback, metric-override) / display / preload. Additive — the family stack still works from `family`+`fallbacks`. - render-css: renderFontFaceBlocks generates @font-face per face from the config, deduped by the real font name (a font shared across slots — Lora as secondary+display — emits once). Optional metric-override fallback @font-face (anti-CLS) injected into the stack as `'{family} Fallback'` when declared. Emitted first in renderStaticCss. - typography.ts: the BASE THEME's 14 @font-face migrated from fonts.css into the config (faces). TTF today (the theme's choice); a theme swaps to woff2/variable + fallback metrics by editing config only. - index.css: drops `@import './themes/fonts.css'` — the @font-face now ships in generated/base.css. (fonts.css superseded; left in place, no longer imported.) - generated/base.css regenerated (14 @font-face, Lora deduped). test: @font-face generation + dedup; merge-without-mutation assertion updated for the faces field. Verified in browser: 3 families registered, files resolve (200), fonts load on demand (swap). check 0 errors; eidos suite green (3 pre-existing words failures only). Deferred (capability typed, theme adopts when it has the assets): variable woff2, metric-override numbers (need fontkit/precompute), <link rel=preload> (head markup). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	667aa49331	feat(eidos): fluid typography engine (Phase 1) — Utopia clamp, rem, fluid headings ... TYPOGRAPHY_ENGINE_RFC Phase 1. Additive on TypographyPrimitiveSet, behind the frozen token contract (--font-size-X keeps its name; only the value formula changes, like color --scale-* hex -> oklch()). - type-scale.ts (pure, isomorphic, no canvas): the Utopia clamp() formula. fluidClamp / resolveTypeSize / isFluidSize. rem-based (a11y: scales with browser font-zoom). - config-types: TextMetric.size accepts `string | FluidSize` ({min,max,minVw?,maxVw?}). Plain length strings still valid -> backward-compatible. - render-css appendTypographyDeclarations: emits calc(resolveTypeSize(size) * --scaling) -> a fixed rem or a fluid clamp; the --scaling axis composes on top. - config.ts: validateSizeValue accepts a FluidSize (validates min/max/minVw/maxVw) so the base config validates (was the cascade root — FluidSize objects failed the string-only CSS-value check). - typography.ts: sizes in rem; headings (lg/xl/xxl/xxxl) fluid (min @480px -> max @1280px, max = previous fixed px so desktop is unchanged); body (md) fixed. hero/h1/h2 drop the manual { base, md } responsive sizes — the clamp covers the viewport. - generated/base.css regenerated. type-scale.test.ts (6 tests). 2 config-test assertions updated to the new rem/clamp values. Verified in browser: --font-size-xxxl 40px @480 -> 80px @1280; xxl 32->48; lg 18->20; md 16 fixed. check 0 errors; eidos suite green (3 pre-existing words failures only). canvas-text/<SText> unaffected (reads getComputedStyle real font, measures the clamp). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	21b2329a66	feat(eidos): prefers-contrast: more — stronger neutral chrome a11y (P3-2 follow-up) ... Completes the forced-colors a11y work. Users who request more contrast (macOS "Increase contrast", Windows, etc.) now get strengthened neutral chrome: borders bumped to neutral 7/8/9 (subtle/default/strong) and de-emphasized text to 12/11 (secondary/muted). Solid fills + primary text are already high-contrast, so they stay. renderPrefersContrastBlock emits a @media (prefers-contrast: more) block using `:root:root` (specificity 0,2,0) so it wins over the theme's :root regardless of stylesheet order. Values reference --primitive-neutral-* (resolve from the cascade; a theme omitting them just no-ops the declaration — graceful). Strictly additive (gated by the media query) and strictly STRONGER, so it can't regress the default look. Also marks audit P3-6 resolved: dispose() already routes documentElement access via dom (#lastAttrs.target + dom.apply), no direct document access remains. - generated/base.css regenerated. test: renderStaticCss emits the prefers-contrast block. docs: THEMING §28 + audit P3-2/P3-6. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	76e1877281	fix(eidos): consistent surface ladder light/dark — overlay above muted (P3-11) ... In the base light theme `overlay` was neutral-3, identical to `muted` (neutral-3), so popovers/menus/dialogs were indistinguishable from muted panels in light mode. Dark already had overlay=neutral-4. Light overlay -> neutral-4 makes the elevation ladder consistent across both modes: default(1) < raised(2) < muted(3) < overlay(4). Verified in browser (light popover): overlay L93% now distinct from muted L95.5% and default L99% (was overlay == muted). Dark unchanged. generated/base.css regenerated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	e6fd014d43	fix(eidos): snappier checkbox check — stroke draw 220ms -> --duration-fast (120ms) ... The checkmark stroke-dashoffset draw used a hardcoded 220ms while the box fill ran at --duration-fast (120ms) — nearly 2x, so the check read as laggy when toggling. Tokenize it to var(--duration-fast) so the stroke draws in sync with the box (one 120ms motion). Not the motion service (uix.motion) — this is a plain CSS transition in checkbox.css driven by the recipe `stroke-duration` token. Verified in browser: path transition 0.22s -> 0.12s, synced with the box. generated/base.css regenerated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	4eab3306b8	feat(eidos): forced-colors focus a11y (P3-2) + role border ramp 6->7 (P3-3) ... Closes the two color-quality items from THEMING_AUDIT P3. P3-2 · forced-colors (Windows High Contrast): under @media (forced-colors: active) the browser auto-maps borders/text/backgrounds to system colors BUT drops box-shadow — so the box-shadow focus ring (--focus-ring) vanishes and keyboard focus disappears. The foundation now always emits a system-colored outline fallback: @media (forced-colors: active) { :focus-visible { outline: 2px solid Highlight; outline-offset: 2px; } } Components that already focus via outline (e.g. Button) keep theirs by specificity; this is the fallback for the box-shadow ones. renderForcedColorsBlock in render-css.ts. P3-3 · role border ramp: the per-role `border` slot moved step 6 -> 7. In Radix's functional scale 6 is a subtle separator and 7 is the UI element border; step 6 read washed-out on real element borders (outline/surface/controls). element/hover/active (3/4/5) stay — Radix-canonical for component bg. DEFAULT_COLOR_ROLE_SLOT_STEPS. - generated/base.css regenerated (forced-colors block + --color-{role}-border -> step 7). - Verified in browser: --color-primary-border now resolves to primitive-7 (oklch 0.80 0.092 vs the softer step-6 0.86 0.072); checkbox borders render defined, not broken. - test: renderStaticCss emits the forced-colors outline block. - docs: THEMING §28 + audit P3-1/2/3 marked resolved + README ref row. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	909ab7f944	feat(eidos): wide-gamut OKLCH output, default-on (RFC Phase 2, strategy A) ... Each palette step is now emitted twice: the hex as a universal fallback, then an oklch() sibling that wins where supported (Chrome 111+/Safari 15.4+/Firefox 113+). The token layer is now OKLCH-native and wide-gamut-ready, with NO @media and NO config flag (it is the default behaviour). - render-css `appendColorScaleDeclarations`: hex line + `oklch()` sibling per `--scale-{name}-{step}`. Only opaque, parseable steps get the sibling; empty/ non-color values keep just the fallback. `--primitive-*`/`--color-*` are var() refs (untouched); alpha scales stay color-mix/rgba. - generated/base.css regenerated (+744 oklch sibling lines: 31 scales x 12 x 2 modes). Honest scope: the shipped Radix palette is authored in sRGB hex, so its oklch() siblings are sRGB-equivalent (verified: --scale-purple-9 -> oklch(0.5556 0.1829 305.86) paints #8e4ec6) -- identical today. The win is the OKLCH-native foundation: an OKLCH-authored theme or a vivid generated scheme now renders wider on P3 with no extra work. Making the SHIPPED palette visibly wide-gamut is Phase 3. Tests: full eidos suite green except 3 pre-existing words-track failures (confirmed unrelated via baseline). Docs: RFC §7 (status) + THEMING §27 + README ref row. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	c4d2e34dbc	feat(eidos): runtime theme builder API — eidos.applyColorScheme(seed) ... RFC Phase 4: derive a whole-system color scheme from ONE brand seed at runtime. Packages the demo-only builder into a first-class, tested API. - build-scheme.ts (pure): buildScheme(seed, opts) composes the uix.color engine (deriveScheme -> generateScale -> APCA on-solid -> compositing-inverse alpha) into the `--primitive-{role}-*` (+ `--color-{role}-contrast`) override map. seed -> { variables, roles }. No DOM. 6 tests. - ActiveEidos.applyColorScheme(seed, opts) / clearColorScheme(): resolves donor scales + background from the active theme, writes a managed `uix-eidos-scheme` style block AFTER the theme block (wins the cascade), and RE-DERIVES on mode change (follows light/dark). Returns BuildSchemeResult for introspection. opts: variant (tonal|vibrant|monochrome) + temper (intent coherence, keeps hue) + per-role overrides + selector. 4 tests (return value, intents, DOM block ordering + clear, mode re-derivation). - index.ts: export buildScheme + ApplyColorSchemeOptions + BuildScheme* types. - temas/color demo: themeOverride now dogfoods buildScheme (drops the duplicated emitRole/rgbaStr; identical output verified in-browser). - generated/base.css: regenerated for the loss->plum role fix (binding layer --primitive-loss-* now points at --scale-plum-*; keeps the contract test green). - docs: THEMING.md SS26 + COLOR_ENGINE_RFC SS6.2 (status: landed) + README ref row. Overriding the binding layer reprojects every --color-{role}-{slot} + the neutral chrome downstream; the 31-scale palette stays put. Math in $color, composition in eidos/lib (pure), DOM application in ActiveEidos. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	9bf7263366	feat(color): re-author gold + bronze as distinct metals (OKLCH) ... Radix's gold/bronze were near-identical in UI (chroma ~0.05, indistinguishable). Re-authored via uix.color (generateScale from metallic seeds): gold #d4af37 (yellow-gold, OKLCH H91) and bronze #cd7f32 (copper, H61), chroma ~0.13 — ~2.6x more saturated so the hue gap reads clearly (gold yellow vs bronze copper). Verified in-browser: gold rgb(212,175,55) vs bronze rgb(205,127,50), distinct. The other 29 scales stay exact Radix v3; header notes the exception. Palette stays Radix-as-default (swappable) per the engine-not-hues principle. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	2d1ccfbeab	fix(eidos): base theme tertiary gray->indigo, distinct from secondary/neutral ... Tertiary was `gray` — literally the same scale as neutral, and secondary (slate) is a near-gray too, so the three desaturated roles blurred together. Per Material 3's tertiary rule (rotate the primary hue ~60deg), tertiary now uses `indigo`: purple's cool neighbor, saturated enough to be distinct, in a hue band no intent occupies. Updated the one test that pinned tertiary=gray; regenerated base.css. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	be6bd540aa	feat(motion): motion engine as arts/motion service + F6 tokens + F7 typegen ... Relocate the motion runtime out of eidos into a runtime art (src/arts/motion, $motion), exposed as uix.motion and consumed by BOTH soma (Presence.motion -> motion.run) and eidos (delegates + registers presets) -- dissolving the soma->eidos coupling. Remove DialogProps.runMotion / eidos.motionRunner; the bridge is now EngineMotion.run (reads data-animation-style). Delete the 4 relocated dead files (lib/motion/{types,runtime,runner,presets/js}.ts); the preset DATA (presets/css.ts) stays in eidos. Regenerate generated/base.css. F6 - token rigor (Carbon): tokenize the raw firma durations (slower/deliberate/ emphatic/sustained holds, escalating by announce intent severity), add --motion-distance-xl (30px shared-axis), --motion-scale-through (0.92), the emphasized easing, and productive/expressive sets ([data-motion-set=expressive]). F7 - extensibility + typegen: app-extensible, type-safe preset-name registry (EidosMotionPresets, mirroring SemaChannelSignatures); MotionPresetName = keyof EidosMotionPresets | none | (string & {}). Also sweeps other in-progress working-tree edits (web/routes/temas/grafito). Verify: npm run check -> 1 pre-existing error (grafito), 0 new; motion 22/22, active-uix 25/25, Presence 2/2, Dialog 3/3. Pre-existing words-track failures unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	44fe111ca0	fix(eidos): dropdown-menu z-index + finish ActiveDom canonization (tabs, resize-observer) ... Bleed-through: the portaled [data-dropdown-menu-content] had z-index:auto, so any positioned page element with a positive z-index (e.g. a selected [data-toggle-group-item], z-index 1) painted THROUGH it. In the Words inspector the Add-block menu showed the Typography toggle chips ("Predeterminada" / "Normal") bleeding through. Added `content-z: 80` to the dropdown-menu recipe (matches `select`, its sibling click-triggered overlay) + `z-index: var(--dropdown-menu-content-z, 80)` on content + sub-content; regenerated base.css. The soma floating layer reads this computed z-index and mirrors it onto the positioner wrapper. The rest of the menu family (context-menu / menubar / navigation-menu) shares the same latent gap — deferred. Canonization (finishes the dom.raf rollout — zero raw requestAnimationFrame left in src/uix): - tabs-indicator.svelte: requestAnimationFrame/cancelAnimationFrame + new MutationObserver + new ResizeObserver -> eidos.dom.raf / observeMutation / observeResize (disposer pattern via ActiveEidos.require). - tabs.svelte: new ResizeObserver -> eidos.dom.observeResize. - resize-observer.svelte.ts: requestFrame/cancelFrame (raw handle) -> dom.raf (disposer); fixed the stale "Debounces via requestAnimationFrame" comment. Browser-verified in the Words demo: column Add-block menu is opaque and on top (elementFromPoint at the chip centers returns menu items, inMenu:true); the menu options are collapsed + localized (one Encabezado, one Lista con viñetas); empty-column delete works (column persists addressable with 0 children). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	4 months ago
dev	152d2ad960	Theming: Radix-parity palette + intent auto-derivation + color-model docs ... Two-level color model settled (THEMING.md section 25), replacing the anchor RFC: the palette is the source (scales, directly usable, designable); hierarchy roles alias scales explicitly; intents auto-derive from the palette by the book's canonical convention. - Palette library expanded 12 -> 31 scales at Radix Colors parity (exact values): radix-scales.ts (19 added: mauve/sage/olive/sand/tomato/ruby/crimson/plum/ violet/iris/indigo/jade/grass/brown/sky/mint/lime/gold/bronze) spread into base.ts. Each directly usable as --scale-{name}-{step}. - Intent auto-derivation: CANONICAL_INTENT_SCALES (neutral->gray, affirm->teal, fulfill->green, risk->amber, threat->red, loss->plum) + completeColorRoleMap. Intents omitted from a theme role map fill from the convention (identity = step 9); slots derive normally; override optional. ColorRoleMap: hierarchy required, intents optional. - Validation: hierarchy roles required; omitted intents validate the canonical scale exists in the palette. - index: export ScalingKey / SCALING_KEYS. - docs: THEMING.md section 25 (full color model + decisions), section 21 marked resolved, COLOR_MODEL_RFC resolved (anchor rejected). - test: base library asserts 31 scales x 12 steps. Verified: npm run check (0 new errors), vitest eidos (0 new regressions), browser (intents auto-derive: affirm=teal #0E9384, risk=amber #DC6803, loss=plum #7A3AAD at step 9). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	66ce4f354d	Theming: on-solid contrast by luminance (P2-2) + translucent role surfaces (P2-4) ... Two audit P2 quality defects, fixed at engine level. P2-2 - on-solid text illegible on light solids: The `contrast` slot defaulted to `--color-content-on-solid` (white) for every role. On light solids (amber/yellow, risk=orange ~2.3:1) white is sub-AA. The engine now picks by WCAG contrast (gamma-linearized) of the role step-9: when white fails (<3:1) it uses `--color-content-on-solid-contrast` (a dark, new OPTIONAL `content.onSolidContrast` semantic, #1c1917 in base). Only risk flips to dark in base (5.89:1); purple/red/teal/green keep white (convention, >=3:1). An explicit `slots.contrast` override is still honored verbatim. P2-4 - opaque tinted soft surfaces: The soft variant tint (Button + Badge `{role}-soft-bg`) was opaque (step-1 track + opaque color-mix hover) so it did not composite over non-uniform backgrounds. New derived tokens `--color-{role}-surface` (= a2) + `--color-{role}-surface-hover` (= a3) are translucent by construction (compositing-inverse alpha). Button/Badge soft consume them. Toast/Tabs untouched - they are cards, opacity is correct. - config-types: optional onSolidContrast + CONTENT_COLOR_OPTIONAL_KEYS. - config: content keySet allows the optional key; validator value-checks it. - render-css: wcagContrastRatio/wcagRelativeLuminance; luminance pick; emit on-solid-contrast + surface/surface-hover. - contract: on-solid-contrast + surface tokens per role. - themes/base: onSolidContrast #1c1917 (light + dark). - recipes/base: Button + Badge soft-bg -> surface, soft-bg-hover -> surface-hover. - docs: THEMING.md section 24 + section 22 item 2; audit P2-2/P2-4 resolved. Verified: npm run check (0 new errors), vitest eidos (0 new regressions), browser runtime (risk 5.89:1 dark text, surfaces translucent rgba). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	bceaef41e0	Theming: add `scaling` zoom axis (Radix parity), separate from density ... Introduce a global zoom axis independent of density, in parity with Radix Themes' `scaling` (90/95/100/105/110%). Scaling zooms px metrics INCLUDING typography (font-size, icon-size, space, control-height); density only moves layout rhythm + control height and leaves text fixed. The two axes compose multiplicatively. - config-types: SCALING_KEYS / ScalingKey / DEFAULT_SCALING; DensityPrimitiveSet drops the dead `scale` + `contentScale` (kept spaceScale, controlScale). - primitives/static: STATIC_SCALING (0.9..1.1). - render-css: appendScaledMetricDeclarations wraps metrics in calc(<raw>[ * var(--density-x-scale)] * var(--scaling)); appendScalingDeclarations emits --scaling-{key} + --scaling default; renderScalingBlocks emits [data-scaling] blocks. line-height/radius/border/shadow excluded. - config + contract: prune the removed density scalars. - active-eidos: `scaling` / `scalingSource` options, getScaling() on the preference source, data-scaling projection + dispose cleanup. - docs: THEMING.md section 23 + 20.1 reconcile; README density/scaling; SCALING_RFC.md. Verified: npm run check (0 new errors), vitest eidos (0 new regressions), browser cascade at 90/100/110 scales font/space/control x0.9/x1.1 and leaves radius/border fixed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	98d6799ad0	Theming: generate alpha scales via compositing inverse (P1-1) ... Replace the synthetic step-9-at-opacity alpha ramp with a real compositing inverse: each --scale-X-aN is the translucent color that, painted over the scale's background (white for light scales, black for dark, by step-1 luminance), reproduces the opaque solid step N (Radix model). Computed in render-css.ts for ANY theme (base + custom), so alpha is consistent-by-construction with the solid scale and cannot drift. alphaScales opt-in still wins verbatim; non-hex solids fall back to the legacy color-mix ramp. Verified: --scale-purple-a9 = rgb(92 0 173 / 0.6941) over white = #8e4ec6. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	3adc93b2d1	Banner: route palette through recipe forwarders (P1-5) ... - Add 40 recipes.banner.{intent}-{slot} forwarders (= var(--color-{intent}-{slot})) - banner.css reads --banner-{intent}-{slot} instead of foundation --color-{intent}-* directly - Banner is now retintable per-component via recipes.banner.* like button/badge; keeps data-intent (no API change) - Regenerated base.css; recipe contract balanced (40 declared = 40 consumed), no visual regression Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	218ccfcc5e	Theming: untitled-ui demo theme, engine fixes, audit + P0/P1 fixes ... - New untitled-ui demo theme + theming showcase route (web/routes/temas) - Engine: density tokens scale via calc(var(--density-*-scale)); contrast slot defaults to on-solid - Eidos theming audit (THEMING_AUDIT_2026-06-01.md) + two-tier color-model RFC (COLOR_MODEL_RFC.md) - P0: replace phantom foundation tokens in recipes + component CSS — shadows -> semantic scale (subtle/raised/overlay), add --space-7, --border-width-strong -> thick; neutral solid contrast -> step 12 (AA in light + dark) - P1: validate hex color values + per-theme semantic completeness; regression tests for contrast, density, dark output, and TSC multi-part/composition emission Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 months ago
dev	8afe2728bb	feat(words): comfortable reading scale for the content surface ... The editor used UI-cramped metrics (14px / 1.25 line-height / 8px block gap) which read as a form field, not a document. Give the CONTENT (not the chrome) a reading scale: body 14→16px, line-height 1.25→1.6, block gap space-2→space-3 (headings derive 1.5x for top margin). Chrome keeps its smaller --_words-font-size. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	4 months ago
dev	9e13d0083e	fix(words): refine the left margin band per feedback ... - Decouple band width from text inset: `--_words-rail-width` (1.25rem, the thin band) + `--_words-rail-gap` (1.25rem, breathing room) → text is no longer glued to the band edge. - Narrow the band: 2.5rem → 1.25rem (20px). - Lighter tones: rail-bg #ededed → #f5f5f5, rail-border #cfcfcf → #e3e3e3. Eidos CSS regenerated. Verified: band 20px + 1px #e3e3e3 edge, then 20px air before text at 40px. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	4 months ago
dev	540c35e679	feat(words): gutter rework — drop "+", move insert into drag menu, silver band ... User-directed editor rework, step 1 (left gutter): - Remove the "+" inserter button from the block-handle gutter. Its action moves into the drag-handle menu as a new "Insert below" item (folded into `act('insertBelow')`); the standalone `insertBelow` helper is gone. The separate seam inserter (words-block-inserter) is untouched. - Turn the left gutter into a soft silver margin band: narrow it (`--_words-gutter-size` 3.5rem→2.5rem) and paint it via a background-gradient on [data-words-content] — `--words-rail-bg` #ededed band with a 1px, slightly stronger `--words-rail-border` #cfcfcf right edge. Background only, so the contenteditable text / selection is undisturbed. Recipe tokens softened + eidos CSS regenerated. Verified in browser: gutter shows only the grip on hover (no "+"); the menu reads Insert below / Move up / Move down / Duplicate / Delete and "Insert below" inserts a paragraph (7→8 blocks) and closes the menu; the silver band renders at 40px with the 1px border. npm run check: 0 errors. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	4 months ago
dev	d126e16e65	fix(words): silence canvas truly, drag for list/table, no overlay hovers + day-end docs ... EV-G final pass + EOD documentation. Words editor: - Stop emitting `contact-focus` from soma. Removing the per-component cascade rule earlier didn't fully silence the editor — the `contact` family carries a BASE sound signature in SEMA_MAP (pitch 800, gain 0.25) that fires even without a cascade rule. The trigger call is commented out (event no longer emitted; telemetry empty). Per spec: "sigue apareciendo el puto sonido, el ring". - Drag handle + inserter now cover lists AND tables. Selectors expanded from `[data-words-node="block"][data-words-path]` to also match `[data-words-node="list"]` and `[data-words-node="table"]`. Top-level lists / tables get the grip + the "+" seam under them. - Removed :hover from `[data-words-block-handle]` and `[data-words-block-inserter-button]`. Gutter overlays are AMBIENT — visual state via data-attrs only (`data-open`, `data-grabbed`, `data-dragging`). Per spec: "quítale el hover al botón de añadir bloque, si el handle no tiene este tampoco". - Rail tokens hoisted to recipe: `words.rail-bg = #d4d4d4`, `words.rail-border = #9a9a9a`. Fixed-tone (not theme-aware) — the rail emulates the physical margin of a notebook; same look in light/dark. Recipe-css-contract test was rejecting raw hex in words.css. Docs: - CLAUDE.md hand-off 2026-05-28 #2 documenting the 6 EV-* Words sprints + 5 architectural decisions with lasting effect (canvas silent, fixed-tone tokens for physical metaphors, drag predicate covers list/table, ambient overlays, insertParagraph empty-block guard). - continue.md (CONTINUE.md) rewritten for tomorrow's pickup: TL;DR of the two halves (toggle-group structural + Words UX), remaining bugs (drag handle outside rail on code blocks, heading inline level change), and the heredados (POLISH-1b, F2.3-F2.6, DRAGDROP-SOMA). Verification: 467/467 morfo + sema + eidos + soma/words tests pass. 85/85 engine pass. `npm run check`: 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	ce95473261	feat(words): internal scroll for the content area + capture-phase scroll sync ... The editor body was unbounded vertically — long documents pushed the whole page instead of confining the scroll to the editor surface. Per spec: "la parte de la edicion deberia tener un scroll". Recipe: - Three new tokens `content-max-block-size-sm/md/lg` (50vh / 60vh / 70vh) mirror the existing `content-min-block-size-*`. Generated CSS regenerated. CSS: - `[data-words-content]` now carries `max-block-size: var(--_words-content-max-block-size)` and `overflow-y: auto`. The min-block-size baseline stays as the starting height for empty editors. When content grows past the cap, the body scrolls internally — the host card no longer balloons. - `scroll-padding-block: 1rem` hint so caret-into-view nudges leave breathing room. Block-handle / block-inserter / image-float-bar: - Switch scroll listeners from `window.addEventListener('scroll')` to `document.addEventListener('scroll', { capture: true })`. Scroll events don't bubble; the previous wiring only caught window scrolls. Now the gutter overlays (handle position, "+" snap target, image float bar anchor) re-measure when the user scrolls INSIDE the content area too. Verification: dev probe at /uix/components/words confirms `max-block-size: 600px`, `overflow-y: auto`, content scrollHeight (615px) > clientHeight (600px), `isInternallyScrollable: true` on a 1000px viewport (60vh of 1000 = 600). 467/467 tests pass across eidos + morfo + sema + soma/components/words. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	d3f9be4ab0	fix(toggle): add missing per-color track/hover/border forwarders ... The toggle palette cascade (palette-track / palette-hover / palette-border declarations in TSC) referenced --toggle-{X}-track, --toggle-{X}-hover, --toggle-{X}-border for X in {primary, neutral, secondary, affirm, risk, threat} — but the recipe only declared 5 forwarders per color (element / solid / solid-hover / text / contrast). The 3 missing slots × 6 colors = 18 unresolved tokens made --toggle-palette-{track,hover,border} resolve to empty for any non-neutral color (the host default DID declare them). Visible effect, only when a non-neutral color was active: - ghost-on-bg = var(--toggle-palette-track) → empty → transparent fallback - ghost-on-border = color-mix(... palette-border ...) → invalid → property dropped, border falls through to base layer - outline-on-bg = color-mix(... palette-element ...) was the one that worked because palette-element forwarders DID exist for all 6 colors Surfaced today while verifying the TSC v2.2 toggle-group color cascade fix in the browser. The toggle-group composition correctly overrode --toggle-palette-* on items, but the empty track/hover/border slots collapsed ghost-state styling downstream. Verified with browser probe (preview_inspect): - ghost + affirm: paletteTrack #0d1514, paletteHover #023b37, paletteBorder #145750 (was "") - ghost + threat: paletteTrack #191111, paletteHover #500f1c, paletteBorder #72232d (was "") - outline + primary: paletteTrack #18111b, paletteHover #3d224e, paletteBorder #54346b (was "") Tests: 100/100 pass in src/uix/eidos. Recipe contract guard accepts the new forwarders (kebab-case, valid var() values). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	9c6375c96e	feat(eidos): TSC v2.2 (parts + composition) + universal theming coverage ... Token Scope Contract universal — no más excepciones arquitectónicas. Los 3 componentes que vivían fuera de TSC v2.1 (select, avatar, toggle-group) ahora están dentro del contrato via dos extensiones nuevas. TSC v2.2 extensiones (lib/config-types.ts + render-css.ts + config.ts): - `parts: readonly string[]` en RecipeTokenMultiDeclaration — emite selectores comma-separados (`[data-{c}-x], [data-{c}-y]`) para componentes con data-color cascadeado per-part. Consumer: select. - `composition: { foreignRecipe: { targetSelector, tokens } }` sibling key — overrides cross-recipe scoped a la cascade del host. Consumer: toggle-group modifica `--toggle-palette-*` en sus items. Migraciones: - select: 3 private `_accent-{track,border,text}` con parts: ['trigger', 'content'] + 7 cascades color:X each. Removed orphan `_accent-solid` (CSS no consumía). - avatar: 6 tokens via composite scopes `['variant:X', 'color:Y']` con matrix helper inline. Badge usa parts: ['badge']. Reemplaza 24 bloques CSS × 2 partes. - toggle-group: composition block con 8 palette tokens × 4 colors. Reemplaza 4 bloques CSS per-color. Bug toggle-group post-composition (encontrado y arreglado): Tras la composition migration, el cascade del toggle-group seguía roto porque los tokens derivados (`--toggle-solid-on-bg`, `--toggle-outline-fg`, etc.) viven en scope `[data-toggle]`. El `[data-toggle-group-item]` es sibling (no descendant), así que `var(--toggle-solid-on-bg)` resolvía undefined. Fix: inlined derivation expressions directamente en `[data-toggle-group-item]` y sus variant cascades (solid/outline/ghost), referenciando palette tokens en su propio scope local. Validador + emisor + contract: - `validateRecipeComposition` valida el shape `{ targetSelector, tokens }` y rechaza composition entries con scope='root'. - `stripCompositionKey` + `emitComposition` separan el pipeline. - `appendRecipeContractTokens` skip-list para `composition` (no aparece como fake `--{c}-composition` knob). - `tokenKeys`/`tokenEntries` helpers en recipe-css-contract.test.ts filtran composition en todos los iteradores. Documentación: - THEMING.md §18 reescrito como "Cobertura universal de TSC". §7 extendido con subsecciones "Multi-part scope" y "Cross-recipe composition" + ejemplos completos. TOC actualizado. - eidos/README.md tabla de referencia ampliada con TSC v2.2 + §18. - CLAUDE.md gana hand-off "2026-05-27 #5" (TSC v2.2 + cobertura universal). - CONTINUE.md reescrito al estado actual de la sesión. Working tree también incluye sprint Words en paralelo (multiple authors): slash menu, find/replace regex, code language picker, table audit, toolbar family menu, code highlight engine. Tests: 786/786 pass en src/uix/{eidos,morfo,soma,sema}. `npm run check`: 6 errores pre-existentes (lib/_demo, soma/components/internal, web/routes/active) no relacionados. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	4 months ago
dev	e6eee766ee	Improve words editor tooling	5 months ago
dev	89f52c5e88	feat(eidos): Card, Avatar ext, Image, SText, Badge, service components + dates engine fixes ... Sprint completo: - Card (eidos + sema): elevation/intent/interactive, eventos select+activate. - Avatar: ring, AvatarBadge, AvatarGroup separados; demo Avatar standalone. - Image: status surface (idle/loading/loaded/error) consumiendo soma ImageProvider. - SText + STextVirtualList: canvas-text engine portado de morfo-driven-soma como componentes separados para optimizar bundle (no se importa canvas si no se usa). - Badge: primitivo eidos puro. - Trans, FormatNumber, FormatDate, RelativeTime: 4 service components greppables alrededor de uix.langs y uix.format. Nav group "Utilities". Bugs fix arts/format/dates (engine-dates.ts): 1. Preset / per-axis conflict: Intl.DateTimeFormat rechaza dateStyle/timeStyle con cualquier per-axis (weekday/era/year/month/day/dayPeriod/hour/minute/ second/fractionalSecondDigits) o con timeZoneName. Engine drop-ea ambos presets por defecto cuando detecta conflict (regla estricta — un solo per-axis hace ilegales los dos presets). 2. Per-call locale override: formatDate/Time/DateTime aceptan tercer arg locale?: string. No muta engine state. Cache (getCachedDateFormat) keyea por (locale x options). resolveCallHourCycle: cuando hay locale override y pref auto, el ciclo horario se resuelve desde el locale OVERRIDE. 3. withHourCycle precedence: caller hourCycle/hour12 ahora gana sobre preferencia del engine. Antes spread mal ordenado sobrescribia 'h12' del caller con 'h23' del engine cuando locale resolvia a 24h. FormatDate component vuelve a rutear siempre por uix.format.dates (cache + hourCycle + locale reactivo), pasando locale como tercer arg. Demos service components autonomos del toolbar global: cada uno owns su demoLocale state con 7 chips (es-ES/en-US/en-GB/de-DE/fr-FR/ja-JP/ar-EG). FormatDate stage filtra dateStyle/timeStyle por mode + chip hourCycle anadido. Tests: 14/14 passing en engine-dates.test.ts (+6 nuevos: conflict handling, locale override, hourCycle precedence). Docs: arts/format/README.md (handoff 2026-05-25 con las 3 reglas), README.md por service component, project_service_components_sprint_2026-05-25.md, feedback_service_demos_own_locale.md (pattern reusable). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	12a7e5cfd3	fix(uix audit): apply Kim audit remediations across morfo/soma/eidos/recipe layers ... Resolves 34 of 40 failures from src/uix/audit-uix-kimi-1.md. The remaining 6 are all Words component (excluded per project owner — actively developed on a separate track) or unrelated infra (cookie-adapter-client jsdom timeout). Key changes: - soma/provider/context.ts: swallow Svelte's `lifecycle_outside_component` in `context.set()` so unit tests can instantiate providers without a component tree (unblocked 18 picker tests in one line). - soma/textarea: route inline style writes through `dom.apply({attrs})` instead of direct `el.style.X = Y` (contract regex compliance). - soma/picker-shell: add minimal Provider component + morfo so the shared handle utility passes the morfo/component contract. - eidos/_layout: lift `shared.ts` to `eidos/lib/layout-helpers.ts` (the `_layout` directory wasn't a real component) and update 8 layout primitive imports. - eidos/command: replace `onMount` with `$effect` (visual layer can't use Svelte 4 lifecycle hooks per component-api contract); restructure `Item.Icon`/`Item.Shortcut` namespace so contract regex matches. - eidos/color-picker: extract hue spectrum hsl literals to sidecar `color-picker-spectrum.css`; keep main recipe color-literal-free. - eidos/lib/recipes/base.ts: declare 196 layout-primitive + chrome CSS vars (box, flex, grid, float, group, banner, container, section, separator, toggle-group, pin-input, scroll-area, splitter, navigation-menu, dropdown-menu, context-menu, date-range-field, time-range-field, plus per-component additions to date-field, color-picker, button, select). 197 missing → 0 non-Words. - morfo: add `data-dir` to carousel, `data-kind` to date-picker, add StrengthMeterLabel sub-part to password-field, register picker-shell. - 5 pickers (date/color/date-range/time/time-range): add `internals.ts` indirection so `exports.ts` doesn't re-export `*provider.svelte.ts` directly (contract D); rewrite virtual root types to plain object literals (no `WithChild`/`PrimitiveDivAttributes`). - 4 new READMEs (button, textarea, password-field, picker-shell) following the search-field canonical template. Test result: 2391/2397 passing (99.75%). Remaining 6 failures are all Words-scope or jsdom infra timeout — explicitly out of scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	bb56e94864	fix(password-field): chrome layout + meter visibility + form field styling ... Three real visual bugs caught after browser verification: 1. **No visible border around input + meter row.** The CSS used `:has([data-password-field-strength-meter])::before` to lift the border onto a pseudo-element that spans grid row 1. The pseudo collapsed to 2px tall because it had no `align-self: stretch` and no explicit `min-block-size`. Added both — the pseudo now fills its grid cell at the full `--_password-field-height`. Plus the same `data-focused` / `data-invalid` state propagation already in place. 2. **Strength meter segments invisible.** Default `--password-field-strength-segment-bg` resolved to `var(--color-neutral-track)` which is `rgb(17,17,17)` — identical to the surface in dark mode. Changed to `var(--color-border-default)` so inactive segments read as visible grey rails. Also bumped segment height from 4 → 6 px so the bar is clearly readable. 3. **Eye icon too small inside a thin trigger.** `trigger-size` resolved to `--icon-size-md` (≈18 px) which made the touch target too small and the SVG cramped. Promoted trigger-size to use `--control-height-{xs..md}` so it matches the input row height per size. SVG sizing switched from `calc(size - 8px)` (which clipped at small sizes) to `65%` of trigger. 4. **Stage wrapper collapsed to content width.** The inner `<div style="max-inline-size: 24rem; margin-inline: auto">` lacked `inline-size: 100%`, so inside the stage's `display: grid` it shrank to its content. Added the explicit `inline-size: 100%`. 5. **Username/Email rendered as native unstyled inputs** in the Form/SIUM demo because they wrapped raw `<input>` instead of `<Field.Input>` (Field.Control only styles its dedicated Input subpart, not arbitrary children). Swapped to `<Field.Input>`. 6. **SIUM error refs (`#?sium.errors.min_length|...`) rendered literal.** `Field.ErrorText` just renders the string it receives. Added a local `issueText(form, field)` helper that calls `uix.langs.ts(raw)` to resolve the langref and then interpolates `{{param}}` from `form.issues[field][0].params`. Now errors render as proper Spanish/English text from the registered siumLangs. Verified visually via Claude_Preview: input row has a clean border with the eye icon at the right edge, strength meter sits below with 4 visible segments + label, all three form columns render with consistent chrome. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	8d277fe929	fix(password-field): align input chrome with system + add Form/SIUM demo ... Style fix — input chrome was hand-rolled with raw color tokens (`--color-neutral-border`, `--ring-width`) instead of consuming the recipe layer like every other text input. Now matches search-field and number-field exactly: - Added `password-field` recipe to `src/uix/eidos/lib/recipes/base.ts` with the same surface as `search-field` (height, px, gap, font-size per size; border, focus, invalid, bg, color, focus-shadow tokens). - Regenerated `src/uix/eidos/generated/base.css`. - Rewrote `password-field.css` to consume the new tokens — same focus ring (`focus-shadow`), same border colors, same disabled opacity, same transition tokens. VisibilityTrigger gets its own border/bg/ color-on-hover scheme aligned with search-field's clear button. - Added per-size icon + caps font-size tokens so the trigger and caps pill scale with the input. Form + SIUM demo — answers "how does PasswordField validate?": Added a new subsection in the Live tab with three working forms wired through `<Form>` + `<Field>` and SIUM schemas: 1. Login (purpose='current', non-empty password) 2. Registration (purpose='new', complexity rules via regex pipes — uppercase + digit + symbol + 8+ chars, plus the visual StrengthMeter as a companion to the schema) 3. Password change (3 fields with a cross-field `refine()` so new === confirm; demonstrates SIUM's refine pattern) The section explicitly documents that PasswordField has no built-in complexity rules — validation is schema-first. The schema decides what's "correct"; PasswordField's flags propagate via Field's OR-merge of `formFieldState.isInvalid`. svelte-check: 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	940e94bb64	Build TextArea component + fix locale propagation bug across soma providers ... Major work in this session: 1. NumberField demo refactored to expose Intl.NumberFormatOptions live - 9 canonical presets (currency/unit/percent/compact/plain) - Locale/currency/unit lists derived from $libs/langs, $libs/currency, $format/units (no more hardcoded arrays) - Default locale from uix.format.numbers.getLocale() 2. Bug fix: locale prop ignored when soma.format service is active - soma/NumberField: 5 bypass points via new `hasOwnLocale` getter (decimalSeparator, groupSeparator, formatValue, formatEditValue, parseValue) - soma/Calendar: dateOrder respects locale prop (matches DateField precedence) - soma/RangeCalendar: same dateOrder fix - When the consumer passes `locale` prop, soma.nums/dates is bypassed and Intl is used directly with the prop locale 3. TextArea — new component, full 4-layer stack - morfo: 3 parts (provider/input/count), 3 events (commit-input/commit-submit/shift-count-overflow), APG textbox - soma: TextAreaProvider with autosize (scrollHeight measurement), submitOn modes (false|enter|shift+enter|mod+enter), maxLength soft clamp, Field integration (OR-merge), counter overflow tracking - eidos: 5 sizes × 3 variants × 8 colors, autosize suppresses CSS resize - sema: commit-submit + shift-count-overflow perceptual cues - demo: canonical 6-tab depth, all props exposed as live controls - PrimitiveTextareaAttributes added to soma/types/html.ts 4. Also includes accumulated unreleased work from prior sessions: - Eidos ports: announce, clipboard, drag-drop, feed, table, tree-grid, tree-view, virtual-grid, virtual-list, words - Their canonical demos under web/routes/uix/components/ - Semantic events defined for utility morfos (announce/clipboard/virtual-list/virtual-grid) - Tree indent guides fixed (TreeView ::before, TreeGrid stacked gradients) - Sidebar reorganized with Data + Utilities groups - Eidos words content layer and primitives Reference library survey performed before TextArea API design (Mantine, Radix Themes, Chakra v3, React Aria, Ark UI, Bits UI, shadcn, MUI, Prime). Decision documented: no separate CurrencyField/UnitField — single NumberField with formatOptions is the canon (matches all surveyed headless libs except PrimeReact's mode enum, which still uses 1 component). svelte-check: 0 errors in modified/created files. See CONTINUE.md for full session notes and next steps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	a804c39208	feat(eidos): Button + 9 demo rebuilds + picker recipe polish ... Build: - New <Button> compound (morfo + soma + sema + eidos): 6 variants (solid/soft/surface/outline/ghost/plain), 8 colors, 5 sizes, optional icon/endIcon snippets, loading state with built-in Spinner, asChild Slot pattern, intent-driven sema (commit-action with fromProp:intent). Demo rebuilds (canonical depth per DEMO_AUTHORING_GUIDE): - context-menu, dropdown-menu, pin-input, alert-dialog, toggle-group: full per-part Morfo contracts, reference-parity tables, ARIA contract tables, keyboard tables, composition controls. - color-field, time-field, time-picker, time-range-picker, color-picker, month-grid, year-grid: same canonical treatment; per-part data/aria/ keyboard iteration of raw morfo, reference parity vs react-aria/ ark-ui/Chakra/bits-ui/Mantine. Picker recipe polish: - PickerShell.Clear/Cancel/Close refactored to use <Button size="xs"> (affects 5 pickers — date / date-range / time / time-range / color). - TimePicker + TimeRangePicker: popover condensed (min-width 18rem -> 14 / 32 -> 28), per-channel accent (hour=primary, minute=secondary, second=neutral; end variant muted), ruler off by default, hour ruler cleaned to 0/6/12/18/23. - ColorPicker: typography token --_color-picker-trigger-font-size that scales with data-size (10/12/14px); autoFormat default true; Area recipe override for [data-x-channel='hue'] with rainbow gradient + saturation/brightness Y overlays. - ValueText eidos wrapper: fix children snippet bug that suppressed soma's displayValue fallback. - date-field.css: segment editing affordance (cursor + hover + active ring) via new --_date-field-accent-element token across 8 color cascades. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	015bd761bd	feat(eidos foundation): emit --style-{name}-* tokens for named typography styles ... `STATIC_TYPOGRAPHY.styles` already defined 11 named typography styles (hero, h1..h6, body, prose, label, caption, code) but the renderer only emitted families / sizes / weights — the style entries lived as data with no CSS reflection. Extend `appendTypographyDeclarations` so each named style emits: - `--style-{name}-font-family` → `var(--font-family-{family})` - `--style-{name}-font-size` → `var(--font-size-{size})` - `--style-{name}-line-height` → literal or `var(--font-line-height-{size})` - `--style-{name}-letter-spacing` → literal or `var(--font-letter-spacing-{size})` - `--style-{name}-font-weight` → `var(--font-weight-{weight})` (or numeric) - `--style-{name}-color` → `var(--color-{dot.path → dash-path})` Responsive sizes (e.g. `hero.size = { base: 'xxl', md: 'xxxl' }`) emit the base value into `:root` and per-breakpoint `@media (min-width: …)` blocks that override the same variables. Breakpoint thresholds match `$libs/dom/responsive` (sm: 480, md: 768, lg: 1024, xl: 1280, xxl: 1536). `renderStaticCss` now iterates `STYLE_BREAKPOINT_ORDER` after the main `:root` block and appends one media-query block per breakpoint that has at least one responsive override. The `indentBlock` helper preserves indentation inside the wrapper. `base.css` regenerated. svelte-check 0 errors, `npm run component:audit` 81 / 81 PASS unchanged. This is foundation-only; no components consume the new tokens yet — that lands in the typography port (Text + Heading + Display + Code + CodeBlock + Kbd + Mark + Highlight + Link). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	9fbf8e48b5	feat(number-field, search-field, combobox): audit-driven improvements ... Three components closing the 6-component audit batch. number-field - N1 RTL scrubber: invert horizontal delta sign when dir='rtl' so dragging right decrements (visually backward) in RTL layouts. Vertical unaffected. Added 2 RTL scrub tests; existing scrub test pinned to ltr. - N2 stepper height: Increment/Decrement now use --_number-field-height for inline-size/block-size/min-inline-size so they always match the input row at every size token (xs/sm/md/lg/xl). - N3 input focus ring: explicit [data-number-field-input]:focus-visible with --_number-field-accent-border box-shadow, alongside the existing Provider-level ring. search-field - S1 icon tokens: added --search-field-icon-size-{xs..xl} + icon-color + icon-margin-inline-end + a Morfo Icon part + soma/eidos wrappers. Demo uses <SearchField.Icon><Search /></SearchField.Icon>. - S2 debounceMs prop: soma wraps onValueChange in a timers.schedule with the provided delay. clear() cancels, submit() flushes synchronously. - S3 loading slot: new LoadingIndicator part (morfo + soma + eidos) + data-loading on Provider + CSS spinner via @keyframes search-field-spin honoring prefers-reduced-motion. combobox - C1 ClearButton part: new morfo trigger + soma provider + eidos wrapper with X icon. Hidden via [data-empty] (opacity + pointer-events:none). Click clears value + inputValue and refocuses input. - C2 allowsCustomValue: when true and no highlighted item, Enter commits the current inputValue as the value. Single mode closes after commit; multi appends + clears input + stays open. - C4 Backspace removes last tag in multi mode when input is empty. - C5 Sticky group headers: CSS position:sticky with content-overlay bg. Plus: fixed search-field demo's brittle parts[1] index reference to a named lookup (parts.find(p => p.kebab === 'input')). Verified: svelte-check --threshold error → 0 errors / 0 warnings / 4584 files. All component tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	f4707bd0c9	feat(month-grid, year-grid): add xs size ... Both grids now accept size='xs' alongside sm/md/lg. - recipe: add calendar-padding-xs / control-size-xs / day-size-xs / font-size-xs tokens (space-2, control-height-xxs=22px, font-size-xs). Regenerated generated/base.css. - eidos css: add [data-month-grid][data-size='xs'] and the year-grid equivalent before the existing sm block. - types: MonthGridSize / YearGridSize extend Size with 'xs'. - demos: size chip group now lists xs / sm / md / lg. Verified in browser at /uix/components/month-grid with size='xs': cell block-size = 22px, padding = 8px (space-2), font-size = 12px. 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