14 Commits (96393e43058a21aa19d1328867fe278a91dd0439)

Author	SHA1	Message	Date
dev	2de1718c3b	refactor(langs): words se pliega en palabras — y el nombre sale del corpus ... El pack words desaparece: sus strings de motor entran en palabrasLangs y las guardas (ACTIVE_DEV_TRACK, WIP_TRACKS) dejan de listar 'words'. Las menciones en comentarios de recetas, READMEs, SPECs, demos y docs de proceso pasan a Palabras. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 months ago
dev	116594e063	feat(docs): S1 — generated canonical-vocabulary appendix (STUMBLES #1) ... An agent building a component from the docs-book alone could not assign archetypes / holds / haptic kinds: the closed sets live only in code consts and the corpus (correctly) forbids copying them into prose, so they were invisible from the docs. STUMBLES #1, the top stumble. Fix: docs/canon/vocabularies.md is GENERATED from the consts by 'npm run docs:vocabularies' — the ONE sanctioned place the lists are spelled out (generated = no drift objection), which every other doc links to. It covers part archetypes (with a one-line role each), sema families with their default hold/persistence + per-intent overrides, verbs by family, intents, the perceptual-duration scale, haptic kinds, the 33 palette scales, sizes, variant archetypes, and the shared common.* strings. - scripts/docs-vocabularies.ts imports the consts (robust — no fragile JSDoc/regex parsing) and formats them; the generation is an exported function so docs-check can compare. - Added ARCHETYPE_DESCRIPTIONS to morfo/types.ts (co-located with ARCHETYPE_VOCABULARY, satisfies Record<MorfoArchetype,string>) as the authoritative one-liners the appendix reads — descriptions become first-class data instead of inline union JSDoc a tool would have to parse. - docs-check gains I7: it regenerates in-memory and fails if the committed file drifts from the consts (negative-tested: corrupt -> error, regen -> green). The appendix's own counts pass I1, so I1 doubles as a second guard. - Linked from README (E2 canon row + two 'I want to' shortcuts), CANON.md (doctrine here, enumerated lists there), architecture/morfo.md (pick a part's archetype), and the component-audit minimum-package list (STUMBLES #8). docs:check 0 errors; npm run check unchanged in my files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	730812c074	fix(uix): clear the catalog's clean functional-error flags + reframe C10 tiers ... Cleared the error-severity flags that were mature components missing a documented exception, not real gaps: - 4 service components (format-date, format-number, relative-time, trans) get their E-2.2 exception: they render text via $format/$langs with no visual recipe — no {name}.css by design. - alert-dialog gets its R-1.1 exception: it composes Dialog (soma reuses the Dialog runtime, data-dialog-* markers reach the DOM, dialog.css paints the chrome) — a [data-alert-dialog] root rule would style nothing. - card gets its missing A-1.3 texts.label (+ langs entry, registered) — card had no label at all. C10 (maturity tiers) reframed after the classification exercise showed the audit VERDICT is the maturity oracle, and 'experimental' is nearly empty once exceptions are documented: stable = PASS (82); preview = NEEDS-WORK on docs/demo only (E-2.3/F-1.x/D-*) — functionally sound but underdocumented, which includes mature components like button/table/listbox (a README gap is not immaturity); experimental/WIP = a real FUNCTIONAL gap or foreign track. C10 folds into C8 (document the tier + exceptions when writing READMEs). Real gaps registered, NOT silenced: float-panel A-3.7 (28 mutating keyboard actions, 6 events — a morfo-completeness question), card-group (no morfo), natural-time-picker A-3.1; announce/clipboard R-1.5 (live-region / composed-focus) await their READMEs in C8 to host the exception. npm run check at the 59 baseline; alert-dialog -> PASS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	bbd9c467e5	test(eidos): triage the 15 long-red suite failures — 289/289 green, check 61→59 ... Accumulated test debt (the eidos suite had been red across several feature landings — THEME-SYS-1 named z-index, palette-first static donor library, spin-field extraction, icon stroke-map refinement — none of them regressions; baselined against HEAD). Each triaged stale-vs-bug by confirming current behavior in code before touching a line. Stale tests (code correct/improved, assertion not updated): - z-index '76' -> 'var(--z-index-overlay-tooltip)' (the code is guarded by THEME-SYS-1 in contracts.test.ts — the raw integer is forbidden). - frost '80%' -> 'var(--depth-overlay-translucency, 80%)' (parameterized). - C7 size-bundle coordinate ('--control-height-md' -> '--size-md-control-height'). - icon visual-stroke ratios 1.5->1.125, 1->0.923 (stroke map md 2->1.5, xxl icon 48->52px; the arithmetic follows). - delegate/CSS-only purple-9: the slim foundation legitimately emits the role-referenced donor scales (purple=primary) as overridable :root defaults; the real delegation guarantee is 'no baked [data-theme] block', which the assertion now checks. Test over-flagging (fixed the test, not the code): - CSS-only shared layer: spin-field (no wrapper/index) excluded from the wrapper/barrel/namespace contracts (CSS_ONLY_LAYERS). - soma-runtime vars: 'var(--x, fallback)' is runtime-optional (the STUMBLES #7 soma->eidos surface) — only bare 'var(--x)' requires a recipe declaration. - orphan check made corpus-wide: composition means a sibling consumes a component's tokens (date-picker/month-grid consume calendar-control-*). - natural-time-picker fixed-tone sky colors documented-exempt (Words-rail doctrine). - dialog drift-detector converted to a synthetic fixture (dialog.css no longer ships the dead rule it self-tested against). Real code fixes: - declare '--pin-input-cell-readonly-bg' (I consumed it in C2b without declaring it). - remove 5 truly-dead tokens (drawer content-bg + 4 color-field format-select/segment — 0 consumers anywhere in eidos/soma/web). - clamp time-picker's 'size' to PopoverSize before forwarding (xs->sm): TimePickerSize has xs, PopoverSize doesn't — a latent type bug my recipe change surfaced via a complexity-budget flip. The fix dropped check 61->59, also clearing navigation-menu-content of the same class. card-group flagged as a REAL gap (KNOWN_MISSING_MORFO): it ships parts + chrome but no morfo (morfo-first violation) — tracked, not silenced. Verified: vitest src/uix/eidos 23 files / 289 tests green; npm run check 59 (better than the 61 baseline); component:audit 0 BROKEN. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	6001d9bb47	feat(eidos): C7 — size-bundle adoption swept across the recipe catalog ... The size bundle (--size-{k}-control-height / -font-size / -icon-size, theming/reference §5) was emitted + guarded but consumed by ONE recipe (the toggle pilot). This sweep points every recipe at the canonical size COORDINATE instead of the raw primitive of the same coordinate: 366 refs across 34 recipes (--control-height-{k} -> --size-{k}-control- height, and the font-size / icon-size coordinates likewise). Retuning a size's bundle now reaches every consumer; a recipe that maps a key to a DIFFERENT size's coordinate stays visible as a deliberate deviation. The bundle vars are pure aliases of the primitives, so this is computed-value identical — verified in a live browser: the accordion chain --accordion-trigger-min-height-md = --size-md-control-height = --control-height-md all resolve to calc(36px * 1 * 1). The generated diff is 366-for-366 pure name swaps, nothing else moved. base/xxxl have no size bundle and correctly stay on the typographic primitive. Guard: recipe-css-contract forbids the raw size-coordinate primitive in recipe token values (var(--control-height-{k}) etc.) — the drift can't creep back. This is the ⚠️->✓ that theming/notes' comparison table flags as the size canon's remaining asterisk (canon + guard, now + consumption). component:audit 0 BROKEN; npm run check at the 61-error baseline; the size-bundle guard + palette-cascade guard both green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	0a80da8d2b	docs+fix: old docs quarantined in docs/old-deprecated; STUMBLES doc-class fixes ... Two user findings from the Knob build exercise (an agent building a new component from the docs alone — STUMBLES.md). Quarantine: the superseded fossils no longer share shelf space with the live corpus. docs/old-deprecated/ (with an index README explaining what lands there and pointing readers at docs/README.md) now holds the executed audits and fix plans: fable_audit, fable-eidos-audit, inherit_audit + inherit_fix_plan, ARCHETYPE_COHERENCE_AUDIT_2026-06-19 (still citable — the component-guide banner and the eidos components README repoint to it), COMPONENT_COHERENCE_AUDIT. pendiente.md (a live pending list, not a fossil) moved to docs/process/. docs-check treats the folder as sealed chronicle (I1/I2 exempt; I6 skips its internal links, as its README promises). Root-level *.md is now: README, CLAUDE, AGENTS + the user's own working files. STUMBLES fixes applied on the spot (the doc-class ones): - #2 kind drift: the REAL enum is 'public' | 'private' | 'virtual' (MorfoPartKind, 671/9/14 uses) — morfo.md omitted 'private', the checklist invented 'internal' (0 uses). Both fixed; I2 gains the phantom-'internal' guard. A-2.1's row now says what the audit script actually checks (kebab only — the archetype may vary, the Toggle provider-IS-trigger doctrine). - #6: the langs catalog SHAPE (flat keys, per-language leaves, named export, index registration) is now shown in morfo.md instead of only its location. - #8: component-audit s0 defines the minimum brief package as an explicit 8-file list. The engineering-class stumbles are registered as plan batches S1-S6 (generated vocabularies appendix, continuous-gesture trigger doctrine, part-absent condition, Gesture.rotate, the soma->eidos CSS-var contract, minor frictions). docs:check 0 errors, 11-warn baseline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	62815cb485	feat(eidos): C6 — universal palette cascade moves into the generator ... palette-{slot} is now RESERVED recipe vocabulary: normalizeRecipeTokens (render-css) appends the full per-scale color:{scale} cascade for every donor scale in PALETTE_SCALES to any token named palette-track/element/ border/solid/solid-hover/text/contrast — author-declared color:* declarations win, only absent scales are appended. This is the structural end of the hand-maintained-subset era: a recipe opts into the per-instance palette by naming the token, and the generator guarantees all scales (the 31-vs-33 drift class cannot recur at this layer). Applies to app-config recipes too, since the hook sits where every RecipeTokenSet is normalized. Button's seven manual spreads are gone from base.ts (the helpers moved into the generator); its generated output is byte-identical. Toggle — which already exposed palette-* tokens — universalized itself: +330 generated lines, and <Toggle color="teal"> / color="steel" verified resolving in a live browser (steel and fuchsia are exactly the two scales the hand-kept lists used to miss). eidos-lint now classifies donor-scale values on data-color as sanctioned eidos-only vocabulary (the TSC color:* axis extension) instead of invalid — the morfo enum keeps declaring the semantic roles, per the pilot's deliberate runtime-open design. Guard: recipe-css-contract pins the LAST scale of PALETTE_SCALES for every palette-bearing recipe in the generated css. Also: the stale '31 physical color scales' test TITLE says 33 (its body already asserted 33). Recorded in the plan: the eidos suite carries 15 pre-existing failures in 6 files (baselined against HEAD before this change) — their triage is its own batch. npm run check at the 61-error baseline; lint toggle baseline green again. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	bfcff0e3c0	fix(uix): C5 — every eventful morfo declares its sema expression mode ... The 30 eventful morfos that never declared expression: ALL have a per-component pack in src/uix/sema/components/ — so the classification (book-deviations D.4: pack / family-default / delegated / none) is unambiguous: expression: 'pack' across the board, placed after scope per the switch/button idiom. The sema surface of the contract is now explicit on all 82 eventful morfos instead of inferred from pack-file existence. morfo:vocabulary clean (the one naming warn is media-player, foreign WIP); npm run check at the 61-error baseline. Additional persistence/a11ySemantic annotations deliberately NOT mass-applied — per D.9 the canonical table is reference, authors declare per real consumer (the six that need them already do). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	85e2356d49	fix(uix): C4 — APG anchors for 29 interactive components (20 patterns + 5 documented absences) ... Every interactive morfo now either anchors its W3C APG pattern or documents that none exists. Real patterns (20): the picker family + command + search-field anchor combobox (field/input + popup, the pattern's own popup taxonomy); date-field mirrors time-field's spinbutton (per-segment contract); rating-group -> radio; navigation-menu -> disclosure (the APG's own site-nav guidance); splitter -> windowsplitter; tag-group/tags-input/virtual-grid -> grid; clipboard/file-upload -> button (the trigger IS the widget); announce -> alert (live region); form -> the form landmark; image-adjustments -> slider; table -> table. The A-1.4 valve (documented exception) is wired like the R-x rules, and five components whose widget has NO APG pattern say so in their README instead of faking an anchor: cropper (2-D manipulation), pagination (nav + composed Buttons), stepper, timeline (display list), image-picker (media picker). Remaining warns are the four expected: card/drag-drop/virtual-list host their note when C8 writes their READMEs, media-player is foreign WIP. Catalog: 83 PASS / 47 NEEDS-WORK / 0 BROKEN (was 75/50/5 at the audit's start). npm run check at the 61-error baseline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	3b08711d77	fix(uix): C3 — literal typography swept across 16 recipes (R-2.7 clean) ... Two classes. Real fixes: 8 numeric font-weights tokenized to var(--font-weight-medium/semibold/regular) in command, date-range-picker, link-preview, listbox, menubar, textarea, time-range-picker x2 — same rendered weight, but the foundation now propagates (verified in a live browser: the token resolves to 500). Honest annotations: the proportional/identity literals get their /* literal: <reason> */ valve instead of a fake token — avatar initials/badge scale with the avatar diameter (physically proportional), the calc(1em - (md - sm)) family is the Field label-one-step-down doctrine with a token-derived delta, 1em is context identity (fab glyph, password toggle), the x0.85 captions are proportional to their field token, and combobox's -1px is an optical adjustment on a token-derived size. component:audit R-2.7: 16/16 clean; npm run check at the 61-error baseline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	e009bdf80f	fix(uix): C2b — invalid/disabled/readonly states: real fixes + cited exceptions ... The R-1.2/R-1.3/R-1.4 sweep, same method as C2a (evidence first): each offender is either a REAL missing state or a shared-layer/composed case that must not duplicate rules. Real fixes, all verified in a live browser (computed-style probes, with the transition-mid-flight trap from the demo guide s13 accounted for): switch/toggle/rating-group get the family invalid tint (--color-threat-element, the shipped checkbox/pin-input precedent); toggle gets its readonly cursor; pin-input cells get the readonly muted-surface treatment mirroring date-field segments; the SHARED spin-field layer gains the readonly treatment it lacked (one fix covers css-field + number-field); natural-time-picker gets the disabled opacity/pointer rule mirroring date-field. Exception valve wired into R-1.3/R-1.4 (was only R-1.1/1.2/1.5/E-2.2) and cited exceptions added: css-field/number-field (states live in the shared spin-field layer), dialog (data-disabled sits on the VIRTUAL provider — defaultElement none — and the pressable surfaces are composed Buttons), color-picker (color-field owns the invalid rules), date-range-field (the runtime overlays data-date-field-input on the same elements, per its own recipe header), time-picker (composed time-field chrome). natural-time-picker keeps its two warns for its C8 pass rather than guessing paint targets. All 10 audited components now PASS with 0 R-1.x pending; npm run check at the 61-error baseline. css-field/number-field READMEs fixed on disk but unstaged (unrelated local modifications). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	9975a67d53	fix(uix): C2a — R-1.5 recognizes the framework's own focus patterns; class resolved ... The audit's focus check grepped only for :focus-visible, blind to how the framework actually shows focus: the universal archetype ring (archetypes.css [data-archetype]:focus-visible with its documented exclusions), the field shell's :focus-within, and the canonical state-attr ring ([data-focused] + focus-ring tokens, soma-written — the spin-field/search-field pattern). Blindly adding :focus-visible rules to the 10 flagged recipes would have recreated the exact 'double border' anti-pattern archetypes.css documents against. The check now accepts the four sanctioned evidences (textarea and search-field pass on their own css; date-picker passes via exception) and the remaining non-ring cases carry cited R-1.5 exceptions: css-field/number-field (ring lives in the shared spin-field layer), dialog (content panel is the documented foundation exclusion; close/trigger are composed Buttons), date-picker (foundation ring + content exclusion), metrics/timeline (no focusable part — interactive only by events). clipboard/announce host their exception when C8 writes their READMEs. css-field/number-field READMEs fixed on disk but left unstaged (they carry unrelated local modifications). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	abede885c7	fix(uix): C1 — zero BROKEN components; documented-exception valve in the audit ... The 5 BROKEN components (cascade, gradient-builder, menu-dial, motion, qr-code) are BROKEN no more: cascade/motion/menu-dial now PASS, gradient-builder/qr-code drop to NEEDS-WORK with only demo-phase (D-*) and C8 items left. Framework-level piece: component-audit gains the documented-exception valve the checklist already used for A-2.3/R-1.7 — a greppable 'R-x.y exception: reason' line in the component README turns the rule into a PASS that reports the reason. Wired for R-1.1, R-1.2, R-1.5 and E-2.2; the checklist rows say the same. This separates deliberate design (cascade and motion deliberately ship NO recipe — they ride the foundation stagger + state presets; menu-dial's focus/disabled states live in the composed Fab/Button recipes) from plain omission, which stays an error. Mechanical fixes: texts.label + langs entries for cascade/motion (new files, registered) and gradient-builder (label added to its existing entry); menu-dial's missing default export. README contract sections (Baseline/Comparativa/Decisiones/Gaps/Passive justification + Audit exceptions) added to cascade, motion, menu-dial and qr-code — mostly re-heading content those docs already argued; comparativas grounded in M3 speed dial/MUI SpeedDial/PrimeVue, Framer Motion/AnimatePresence/ Svelte transitions, ark-ui/qr-code-styling per component. Verified: component:audit 130 -> 78 PASS / 52 NEEDS-WORK / 0 BROKEN; npm run check at the 61-error pre-existing baseline (0 own). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago
dev	73826b9f81	docs(process): component-coherence plan — audited weaknesses + C1-C10 batches ... Consolidated audit (2026-07-02): 130 components -> 75 PASS / 50 NEEDS-WORK / 5 BROKEN; palette-31 wired in 7 recipes, size-bundle in 1, focus-visible missing in 11, 17 literal-typography recipes, 41/82 eventful morfos without expression:, 33 without APG anchor, 28 without README. Demos (D-*) explicitly deferred to the next phase (component info web). Batches C1-C10 with per-batch verification. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 months ago