svelte-kit-vice/src/uix/morfo/README.md

# Morfo

**The cross-layer contract of a component's public DOM surface.**

Morfo is the single source of truth for a component's parts, data-attrs, ARIA contract, keyboard shortcuts, focus policy, and public event contract. The same morfo is consumed by soma (to wire the headless provider), by eidos (to generate CSS selectors), by sema (to bind perceptual channels), and by the docs site (to render part tables).

**One file per component**, at `src/uix/morfo/components/{kebab}.ts`. No prose — that's the component's README. No props — those live in `types.ts` with JSDoc. Just the machine-readable contract.

---

## Why morfo exists

Without morfo, a component's structural information lives in many places:

- Part names in `createAttrs({ parts: [...] })` inside the provider.
- Data-attr enums in `registerContract({ parts: {...} })` also in the provider.
- ARIA emission hardcoded in the provider's `$derived.by(...)` props.
- Keyboard handlers scattered across the provider.
- Public event names and their transport split across provider code, docs, and consumers.
- Prose descriptions in the README.
- Selector strings duplicated in eidos CSS, sema `.csem`, docs tables.

Renaming a part (`content` → `panel`) used to mean touching 6+ locations with zero automatic verification. Cross-layer drift (soma emits `data-dialog-content`, eidos styles `data-dialog-panel`) was silent.

With morfo, **every location reads from the same declaration**. Parts, data-attrs, and their enum values are authored once. `createAttrs` and `registerContract` consume the morfo directly. A smoke test validates the real DOM against the declaration on every CI run.

---

## What morfo contains

A `Morfo` is a plain TypeScript constant that describes:

- **`name`** — PascalCase display name (`"Dialog"`).
- **`kebab`** — kebab-case identifier (`"dialog"`), matches `data-{kebab}` and `createAttrs({component})`.
- **`scope`** — which layers implement this component: `['soma']`, `['soma', 'eidos']`, etc.
- **`apg`** — optional URL to the WAI-ARIA APG pattern when the component implements a formal one.
- **`focus`** — optional focus policy for overlays / composites.
- **`events`** — the component's public event surface: which semantic occurrences it may emit and expose to cross-layer consumers.
- **`parts`** — the part tree (recursive). Each part declares:
  - `name`, `kebab`, `kind` (`public` / `virtual`).
  - `archetype` — optional cross-component classification (see "Archetypes" below).
  - `defaultElement` (advisory), `role` (always-emitted).
  - `optional`, `supportsNesting`.
  - `states` — the state names this part can be in.
  - `data` — data-attributes emitted, with enum values when applicable and optional runtime source metadata when the contract wants to declare where the attr comes from.
  - `aria` — ARIA attribute contract (attr + value source + condition).
  - `keyboard` — keyboard shortcuts relevant when the part has focus.
  - `parts` — nested sub-parts (recursive).

See [`types.ts`](./types.ts) for the full TypeScript shape.

## What morfo does NOT contain

| Not in morfo | Lives in | Reason |
|--------------|----------|--------|
| Summary, overview prose | `{component}/README.md` | Editorial, not contract |
| Comparison vs Radix / Base UI / Bits | `{component}/README.md` | Third-party drift shouldn't pollute the contract |
| Usage examples | `{component}/README.md` | Narrative |
| Props (names, types, defaults) | `{component}/types.ts` with JSDoc | Canonical source is TS + JSDoc |
| Translations | `{component}/langs.ts` (idlangref) | Separate registry, consumed by the provider |
| Event handlers / runtime wiring, state machines | `{component}-provider.svelte.ts` | Execution logic, not contract data |
| Visual variants / recipes | `src/uix/eidos/` (future) | Layer-specific, not shared |

---

## How morfo gets executed (architecture)

Morfo is **declarative**. By itself it doesn't render, doesn't bind events,
doesn't write to the DOM. The piece that does is `MorfoRuntime`, which lives
in `soma/` and consumes a morfo together with the provider's reactive sources.

The closed architecture (post-2026-04-25) has six pieces with disjoint
responsibilities:

```
Morfo          declares
MorfoRuntime   transcribes
Provider       supplies sources, targets, handlers
Effects        sync attrs from state
SemanticEngine dispatches signals to perceptual channels
VisualChannel  materializes the signal in the DOM (data-event*, hold, cleanup)
ADom           applies DOM mutations (structural commit)
```

### What each morfo field maps to at runtime

| Morfo field | Runtime executor | Purpose |
|---|---|---|
| `parts[].data` (with `value`) | Effect of attrs | Reactive `data-*` |
| `parts[].aria` | Effect of attrs | Reactive `aria-*` |
| `parts[].role` | Effect of attrs | Stable role |
| `parts[].keyboard` | `runtime.keydown(part, event)` | Key dispatch |
| `events[].prewrite` | `trigger()` step 1 | Transient markers |
| `events[].semantic` | `trigger()` step 2 (emit payload) | Perceptual signal |
| `events[].commits` | **Nobody executes**; smoke validates | Documentation |
| `focus` | Configures FocusScope layer | Layer bootstrap |

`commits` is **descriptive**, not prescriptive. The actual causal chain is
`handler -> state mutation -> effect -> dom.apply`. The `commits` declaration
documents what an external observer will see and is checked by the smoke
suite.

### The `trigger(eventName)` sequence

```
1. prewrite imperative (data-last-action, etc.)
2. await semantic.emit(event)
3. provider's synchronous handler mutates state
4. effects derive and apply structural attrs (data-state, aria-*)
```

State is the only source of truth. The DOM is derivative.

### Provider responsibilities

The provider supplies what morfo cannot infer:

```ts
const runtime = createMorfoRuntime(morfo, {
  dom: this.soma.dom,
  semantic: this.soma.semantic,
  states: { open: () => this.opts.open.current },
  props: { disabled: () => this.opts.disabled.current },
  parts: { content: () => this.contentId.current },
  events: {
    'open': () => { this.opts.open.current = true },
    'close-cancel': () => { this.opts.open.current = false }
  }
});
```

Each part-provider then renders only the static identity:

```ts
readonly props = $derived.by(() => runtime.partProps('trigger'));
// returns: { id, ref attachment, 'data-{component}-trigger': '' }
```

Everything mutable (`role` derived from prop, `aria-*`, `data-state`, `data-intent`)
is written by the runtime's effects via `dom.apply`. Svelte does not render
those attrs.

### Operational rules

- `partProps(part)` returns only static identity (id, ref, marker).
- `dom.apply` is the only writer of mutable attrs.
- Event handlers are synchronous. Async work happens before `trigger()` is called.
- Guards (`if (disabled) return`) live at the call-site, not inside the handler —
  if they enter the handler, the perceptual signal already fired.
- `Semantic` may use `Dom` (downward dependency); `Dom` does not know `Semantic`.

See [src/uix/README.md](../README.md) §2.bis for the cross-layer view.

---

## Archetypes — cross-component part classification

Beyond the component-specific `kebab`, a part can declare an `archetype`
that tags it as part of a cross-component category. This is what lets
**eidos** style "all triggers" or "all overlays" with a single transversal
selector instead of enumerating every component.

```ts
{
  name: 'Trigger',
  kebab: 'trigger',
  archetype: 'trigger',  // ← cross-component category
  role: 'button',
  // ...
}
```

The runtime emits `data-archetype="..."` on the part's DOM element via
`partProps`. Static identity (never mutates), so it ships through
`partProps`, not through `dom.apply`.

### Vocabulary (24 archetypes)

```
provider · trigger · content · overlay · viewport
item · option · indicator · thumb · track
label · title · description · close · action
header · image · fallback · arrow · separator
group · input · segment · preview
```

Defined in [`types.ts:ARCHETYPE_VOCABULARY`](./types.ts) and validated by
the sium schema. Optional field — omit when a part is genuinely unique to
its component (`Slider.Range`, `PinInput.Segment` internals).

### Provider as trigger vs container

When `Provider` IS the interactive element (Toggle, Switch, Checkbox —
where `defaultElement: 'button'` and the user clicks the Provider itself),
its archetype is `'trigger'`. When `Provider` is just a root container
(`defaultElement: 'div'/'section'/'nav'`), archetype is `'provider'`.
Decide per-morfo.

### Adding a new archetype

Only add when at least two existing components share the role with the
same conceptual meaning. The vocabulary stays small on purpose. If only
one component has it, leave the part without an archetype.

---

## The 2-of-3 rule for extending morfo

Morfo is the cross-layer contract between **soma**, **sema**, and **eidos**
— not a convenience repository for soma. An extension to morfo is justified
only when **at least two of the three layers** consume it.

| What | Soma | Sema | Eidos | In morfo? |
|---|---|---|---|---|
| `parts[].data` + `aria` + `role` | ✅ | — | ✅ | ✅ |
| `parts[].archetype` | ✅ (emit) | ✅ (verbs by role) | ✅ (transversal selectors) | ✅ |
| `parts[].keyboard` | ✅ (dispatch) | — | — | ✅ (was already there) |
| `events[].semantic` family/intent | ✅ (signal payload) | ✅ (vocabulary) | ✅ (selector tinting) | ✅ |
| `events[].prewrite` (e.g. `data-last-action`) | ✅ (apply) | ✅ (sequence) | ✅ (tint exit anim) | ✅ |
| `data-starting-style` / `data-ending-style` | ✅ (Presence) | — | ✅ (animations) | ✅ |
| Computed state from N props | — (provider exposes virtual prop) | — | — | ❌ |
| `firstOf` value source (priority chain) | ✅ only | — | — | ❌ |
| `prop-not-nullish` condition | ✅ only | — | — | ❌ |
| Field-context OR'ing | — (provider, virtual prop) | — | — | ❌ |

Soma-only conveniences live in the provider — typically as a "virtual
prop" that the provider exposes via runtime `props` sources, then morfo
reads with `propRef`. The line stays clean: morfo declares structure +
contracts; provider decides logic.

---

## Anatomy of a morfo file

Minimal template:

```ts
// src/uix/morfo/components/dialog.ts
import type { Morfo } from '../types';
import { v } from '../types';                     // value builders: v.literal, v.stateRef, v.partRef, v.propRef, v.translationRef

export const dialogMorfo = {
  name: 'Dialog',
  kebab: 'dialog',
  scope: ['soma'],
  apg: 'https://www.w3.org/WAI/ARIA/apg/patterns/dialog/',

  focus: {
    initial: 'first-focusable',
    trap: true,
    return: 'trigger',
    restore: true
  },

  parts: [
    {
      name: 'Provider',
      kebab: 'provider',          // special: 'provider' emits data-dialog (no suffix)
      kind: 'virtual',            // context-only, no DOM
      defaultElement: 'none',
      optional: false,
      data: [],
      aria: []
    },
    {
      name: 'Trigger',
      kebab: 'trigger',
      kind: 'public',
      defaultElement: 'button',
      role: 'button',
      optional: false,
      states: ['open', 'closed'],
      data: [{ attr: 'data-state', values: ['open', 'closed'] }],
      aria: [
        { attr: 'aria-haspopup', value: v.literal('dialog') },
        { attr: 'aria-expanded', value: v.stateRef('open') },
        { attr: 'aria-controls', value: v.partRef('content') }
      ]
    },
    {
      name: 'Content',
      kebab: 'content',
      kind: 'public',
      defaultElement: 'div',
      role: 'dialog',
      optional: false,
      states: ['open', 'closed'],
      data: [
        { attr: 'data-state', values: ['open', 'closed'] },
        { attr: 'data-last-action',
          values: ['saved', 'cancelled', 'dismissed', 'failed'],
          severity: 'optional' }
      ],
      aria: [
        {
          attr: 'aria-labelledby',
          value: v.partRef('title'),
          condition: { when: 'part-present', part: 'title' },
          severity: 'recommended'
        }
      ],
      keyboard: [{ key: 'Escape', action: 'close' }]
    },
    {
      name: 'Title',
      kebab: 'title',
      kind: 'public',
      defaultElement: 'div',
      role: 'heading',
      optional: true,
      data: [],
      aria: [{ attr: 'aria-level', value: v.propRef('level'), severity: 'recommended' }]
    }
  ]
} as const satisfies Morfo;
```

The `as const satisfies Morfo` pattern is **mandatory**, not cosmetic. It does two things at once:

- **`as const`** preserves the literal types (`kebab: 'dialog'`, not `string`). This is what lets `createAttrs(dialogMorfo)` return `{ provider: 'data-dialog'; trigger: 'data-dialog-trigger'; ... }` with autocomplete and typo detection in every provider that consumes the morfo.
- **`satisfies Morfo`** validates that the object conforms to the `Morfo` interface without widening it. If a field is missing or mistyped, TypeScript reports it at the declaration — same safety as `: Morfo =` annotation, without the type widening.

A morfo annotated `: Morfo =` still works at runtime but yields `createAttrs(...): Record<string, string>` — no autocomplete, `attrs.trigerr` compiles. All 66 morfos in the codebase use `as const satisfies Morfo`; new morfos must do the same.

---

## Authoring a new morfo

### Step 1 — Create the file

Write `src/uix/morfo/components/{kebab}.ts` exporting a `{camelName}Morfo` const.

**Naming rules**:
- `name`: PascalCase. `"Dialog"`, `"DateRangePicker"`, `"ColorField"`.
- `kebab`: kebab-case. `"dialog"`, `"date-range-picker"`, `"color-field"`. Must match `data-{kebab}` and `createAttrs({component})` in the provider.
- Part `kebab`s must be **unique across the whole morfo** — no nested path namespacing. If a conflict arises, rename (e.g. `item-trigger` instead of `trigger`).
- The orchestrator part uses `kebab: 'provider'` — special-cased to emit `data-{component}` with no suffix. Matches `name: 'Provider'` for naming coherence.

### Step 2 — Declare parts

For each part, decide:

- **`kind`**:
  - `'public'` when the consumer composes the part (e.g. `<Dialog.Trigger>`).
  - `'virtual'` for internal coordinators that have no DOM of their own (context-only providers, focus guards). Use with `defaultElement: 'none'`.
- **`defaultElement`**: the HTML element the wrapper renders by default. Advisory — the consumer can override via `child` snippet. See the `MorfoElement` union in [`types.ts`](./types.ts).
- **`role`**: always-emitted ARIA role. Declare this even when the element has an implicit role (e.g. `<button>` has `role=button`) — this makes the contract polymorphism-safe: if the consumer uses `<div>` via `child`, the role still applies.
- **`optional`**: `true` if the part may be absent from a valid composition (Title, Description, Close, Overlay, Indicator, Separator). `false` for required parts (root + core).
- **`states`**: only declare if the part carries a `data-state` enum. List the exact values (e.g. `['open', 'closed']`). Required for `stateRef` ARIA values to validate.
- **`supportsNesting`**: `true` if this part can nest inside itself (Dialog inside Dialog, Menu inside Menu). Informational — enables eidos to style nested instances with scoped selectors.

### Step 3 — Declare `data` entries

For each data-attr the provider emits:

```ts
data: [
  // Enum-valued: the complete set.
  { attr: 'data-state', values: ['open', 'closed'] },

  // Same attr, but now declaring its runtime source too.
  { attr: 'data-state', values: ['open', 'closed'], value: v.stateRef('open') },

  // Presence-only flag: emitted only when true, absent otherwise.
  { attr: 'data-disabled', severity: 'optional' },

  // Conditionally-emitted attr.
  {
    attr: 'data-starting-style',
    severity: 'optional',
    condition: { when: 'state-equals', state: 'open', value: 'starting' }
  }
]
```

**Severity rules**:

- `'required'` (default) — the attr must always be emitted. Missing = error in strict mode.
- `'recommended'` — emitted in most cases. Missing = warning.
- `'optional'` — emitted only when its condition is met (e.g. `data-disabled` only when disabled). Missing ≠ error.

Use `'optional'` for all presence-only flags so morfo-check doesn't flag them as missing when they're legitimately absent.

### Step 4 — Declare `aria` entries

ARIA values use a tagged union via builders:

```ts
aria: [
  { attr: 'aria-haspopup', value: v.literal('dialog') },           // static literal
  { attr: 'aria-expanded', value: v.stateRef('open') },             // refs states[]
  { attr: 'aria-labelledby', value: v.partRef('title') },           // refs another part's kebab
  { attr: 'aria-level', value: v.propRef('level') },                // refs a consumer prop
  { attr: 'aria-label', value: v.translationRef('common.buttons.close') }  // refs a langs.ts idlangref
]
```

**Value kinds**:

- `v.literal(value)` — static string invariant. `aria-haspopup="dialog"`, `aria-modal="true"`.
- `v.stateRef(name)` — the attribute value derives from a named state. Validator requires `name` to be in the containing part's `states[]`.
- `v.partRef(target)` — the attribute value is the id of another part. Validator requires `target` to be an existing kebab in the morfo.
- `v.propRef(prop)` — the attribute value comes from a consumer prop (override, passthrough).
- `v.translationRef(key)` — the attribute value resolves to a translation.

Add `condition` when the ARIA is emitted only in some cases:

```ts
condition: 'always'
condition: { when: 'part-present', part: 'title' }
condition: { when: 'state-equals', state: 'open', value: 'true' }
condition: { when: 'prop-truthy', prop: 'modal' }
condition: { when: 'prop-falsy', prop: 'disabled' }
```

### Step 5 — Optional: keyboard and focus

```ts
keyboard: [
  { key: 'Escape', action: 'close' },
  { key: 'Tab', action: 'focus-next' },
  { key: 'Shift+Tab', action: 'focus-prev' }
]

focus: {
  initial: 'first-focusable',          // 'first-focusable' | 'trigger' | { partRef: 'content' }
  trap: true,
  return: 'trigger',                    // 'trigger' | 'previous' | { partRef: '...' }
  restore: true
}
```

Focus is only required for overlay/composite components (Dialog, Drawer, Popover). Plain controls omit it.

### Step 5.5 — Optional: semantic events

Events declare what semantic occurrences the component emits. Per the
canonical guide
[`src/docs/GUIA_IMPLEMENTACION_SEMAUIX.md`](../../docs/GUIA_IMPLEMENTACION_SEMAUIX.md)
§5.1, the shape is:

```ts
events: [
  {
    name: 'commit-toggle',
    semantic: {
      family: 'commit',                       // one of 7 SEMA families
      verb: 'toggle',                         // canonical verb (advisory, validated)
      target: v.partRef('provider'),          // which part receives data-event-*
      sequence: 'post',                       // 'pre' | 'coincident' | 'post'
      intent: {                               // valenced families only
        fromProp: 'intent',                   // bind to a public prop
        default: 'neutral',
        supported: ['neutral', 'affirm', 'risk', 'threat']
      }
    }
  }
]
```

Field rules:

- **`name`** — the addressable id used by `runtime.trigger(name)`.
  Convention: `{verb}-{variant}` (e.g. `dismiss-outside`,
  `close-cancel`) or `{family}-{verb}` (e.g. `commit-toggle`,
  `commit-save`). The validator accepts both shapes.
- **`semantic.family`** — one of `contact`, `commit`, `signal`,
  `handle`, `emerge`, `shift`, `sustain` (per `SEMA_MAP`).
  Transitional families (`emerge`, `shift`, `sustain`) carry NO intent.
  Valenced families (`contact`, `commit`, `signal`, `handle`) require
  an `intent` (literal or fromProp binding).
- **`semantic.verb`** — optional, advisory. Must be in
  `SEMA_VERBS[family]` when present.
- **`semantic.target`** — the `partRef` whose DOM element receives the
  `data-event-*` attrs during the visual hold. Lives inside `semantic`
  per the doctrinal shape (was at event-level pre-2026-05-08).
- **`semantic.sequence`** — when the perceptual signal happens
  relative to the structural state change. Default `'pre'` preserves
  the runtime semantics where the signal completes before the commit.
  Use `'post'` when the celebration belongs after the new state lands
  (commit pulses on completed actions). `'coincident'` is for
  in-flight processes (sustain).

For a comprehensive worked example see the toggle and dialog morfos.

### Step 6 — Wire the provider

In `src/uix/soma/components/{kebab}/{kebab}-provider.svelte.ts`:

```ts
import { createAttrs, registerContract } from '../../attrs';
import { dialogMorfo } from '../../../morfo/components/dialog';

const attrs = createAttrs(dialogMorfo);
registerContract(dialogMorfo);

// attrs is typed as
//   {
//     readonly provider: 'data-dialog';
//     readonly trigger: 'data-dialog-trigger';
//     readonly content: 'data-dialog-content';
//     readonly overlay: 'data-dialog-overlay';
//     readonly title: 'data-dialog-title';
//     readonly description: 'data-dialog-description';
//     readonly close: 'data-dialog-close';
//   }
// — literal-typed from the morfo's `as const` shape.
```

That's it. No more inline `createAttrs({component, parts})`, no more `registerContract({name, version, parts: {...}})`. A typo like `attrs.trigerr` or `attrs.content-wrong` is a compile error, not a runtime silent-undef.

---

## Validation

Three layers catch three classes of drift:

### 1. Sium schema (build / dev)

`src/uix/morfo/schema.ts` exports `validateMorfo(morfo)` which:

- Checks shape: types, enum discriminators, literal unions.
- Checks cross-field invariants:
  - Every part `kebab` is unique in the morfo.
  - Every `partRef.target` resolves to an existing part.
  - Every `stateRef.state` exists in the containing part's `states[]`.
  - Every `state-equals` condition's `state` exists in the containing part.
  - `focus.initial.partRef` / `focus.return.partRef` resolve.
  - `scope` is non-empty.
  - `kebab` matches `/^[a-z][a-z0-9-]*$/`.

Run a morfo through this to catch authoring errors early. See [`components/dialog.test.ts`](./components/dialog.test.ts) for a reference test.

### 2. Strict mode in `assertContract` (dev runtime)

The provider's `assertProps` walks the emitted data-attrs and checks their values against the registered contract. In dev mode, a value not in the declared `values[]` logs a warning:

```
[soma] dialog.content: "data-state" has value "opening" but contract expects one of: open, closed
```

### 3. Smoke + morfo-check (CI)

Two npm scripts exercise the morfos against the real DOM:

- `npm run smoke` — Playwright walks all `/test/soma/*` routes. Catches `pageerror`, `console.error`, translation-key-not-found, context-not-found. Not morfo-specific but catches common regressions.

- `npm run morfo:check` — For each morfo, navigates to `/test/soma/{kebab}` and validates:
  - Every declared data-attr with `severity: 'required'` is emitted.
  - Every emitted data-attr value matches `values[]` if declared.
  - No undeclared `data-{component}-*` attrs are emitted (except `data-_*` private).

- `npm run morfo:vocabulary` — Flags `data-state` enums that diverge from canonical vocabularies (`open|closed`, `active|inactive`, `checked|unchecked|indeterminate`, etc.). WARN-level; novel vocabularies may be legitimate but should be reviewed.

Both scripts require `npm run dev` running in another terminal.

---

## The data-attr convention

`createAttrs(morfo)` derives data-attr names from parts:

| Part kebab | Emitted attr |
|------------|--------------|
| `'provider'` | `data-{component}` — no suffix (orchestrator) |
| `'trigger'` | `data-{component}-trigger` |
| `'item-group'` | `data-{component}-item-group` |

Never `data-soma-*`, never `data-eidos-*` — always `data-{component}[-{part}]`.

Private attrs for internal debug / state use the `data-_*` prefix (convention only — no enforcement), which is skipped by strict-mode validation.

---

## Handling polymorphism (consumer renders a different element)

The `child` snippet pattern allows consumers to swap the default element:

```svelte
<Dialog.Trigger>
  {#snippet child({ props })}
    <a href="/about" {...props}>About</a>
  {/snippet}
</Dialog.Trigger>
```

Morfo's `defaultElement` is **advisory** — the provider doesn't enforce it. What IS guaranteed is `role`: the provider always emits the explicit role (e.g. `role="button"` on a Trigger even though `<button>` has it implicitly). When the consumer renders as `<a>`, the role stays correct.

Keyboard handlers should also be element-agnostic: emit `onkeydown` that handles both Enter and Space for "activate" regardless of the underlying element, since `<a>` only handles Enter natively and `<div>` handles neither.

---

## Sema alignment

[Sema](../sema/sema_pre.md) is the future perceptual/semantic layer. It consumes the same DOM surface that morfo declares — no extra hooks needed. The morfo authoring rules that support Sema:

- **Transition markers**: components with enter/exit transitions declare `data-starting-style` and `data-ending-style` on the transitioning part.

- **Causal exit states**: components with multiple semantically distinct exit paths (Dialog: saved / cancelled / dismissed / failed; Toast: dismissed / auto-timeout / action) declare `data-last-action` with enumerable `values`. The provider is expected to update `data-last-action` **before** `data-state` changes, so Sema can tint the exit animation per-action. (Tracked by a dedicated MutationObserver timing test — future work.)

- **Cross-component vocabulary consistency**: the `morfo:vocabulary` script groups components by data-attr semantic (disclosure → `open|closed`, lifecycle → `loading|idle|success|error`) and flags divergent vocabularies for review.

These don't change the morfo shape — they're authoring conventions that enable Sema without requiring a Sema-aware provider.

---

## Files in this package

```
src/uix/morfo/
├── README.md          ← (this file) developer guide
├── types.ts           ← Morfo interface + v.* builders
├── schema.ts          ← sium-based validator + CANONICAL_VOCABULARIES
├── compile.ts         ← compileMorfo(morfo) → CompiledMorfo (cached by WeakMap)
├── runtime.ts         ← MorfoRuntime that interprets the compiled morfo
├── PERMUTATION_RUNNER.md ← CI tool spec for state-space validation
├── index.ts           ← package barrel
└── components/
    ├── dialog.ts      ← one morfo per component
    ├── accordion.ts
    ├── ...
    └── dialog.test.ts ← reference test pattern
```

---

## Commands

| Command | Purpose |
|---------|---------|
| `npm run check` | TypeScript type-check across the repo (catches shape errors in morfos). |
| `npx vitest run src/uix/morfo` | Run morfo unit tests (schema invariants). |
| `npm run smoke` | Playwright smoke over all `/test/soma/*` routes (requires dev server). |
| `npm run morfo:check` | Validate emitted DOM vs morfo per-component (requires dev server). |
| `npm run morfo:vocabulary` | Flag data-state enums that diverge from canonical vocabularies. |

---

## Common pitfalls

**Using `: Morfo =` instead of `as const satisfies Morfo`.** The annotated form widens all literals to `string`, so `createAttrs(morfo)` degrades to `Record<string, string>` — no autocomplete, typos slip past the compiler:

```ts
// ❌ Wrong — works at runtime, but loses literal types.
export const dialogMorfo: Morfo = { ... };
const attrs = createAttrs(dialogMorfo);
attrs.trigerr;  // compiles as `string`, runtime undefined

// ✅ Right — literal-preserved shape.
export const dialogMorfo = { ... } as const satisfies Morfo;
const attrs = createAttrs(dialogMorfo);
attrs.trigerr;  // compile error — no such part
attrs.trigger;  // typed as 'data-dialog-trigger'
```

All 66 morfos in the codebase use the `as const satisfies Morfo` form. This is mandatory, not stylistic.

**Duplicate kebab in the tree.** `item` in one part and `item` in another = error. Rename one.

**`stateRef` without declaring `states[]`.** If a part emits `aria-expanded` via `v.stateRef('open')`, the part **must** declare `states: ['open', ...]`. Otherwise the validator throws.

**`partRef` to a non-existent kebab.** Common after renaming a part. The validator catches this — but the dev-time warning is silent if you skip `validateMorfo`.

**Missing `severity: 'optional'` on presence flags.** If you declare `{ attr: 'data-disabled' }` without severity, strict mode treats it as required. Add `severity: 'optional'` so morfo-check doesn't flag it missing when the flag is legitimately absent.

**Provider emits a data-attr not in the morfo.** Strict mode logs a warning at runtime; morfo-check fails in CI. Either add the attr to the morfo or rename the provider's emission to `data-_*` (private).

---

## See also

- [types.ts](./types.ts) — the TypeScript interfaces (authoritative reference).
- [PERMUTATION_RUNNER.md](./PERMUTATION_RUNNER.md) — CI tool that cycles components through their state space.
- [COMPONENT_GUIDE.md](../soma/COMPONENT_GUIDE.md) — soma component authoring (morfo-specific discipline: translation-namespace grep, DOM-topology audit, smoke validation).
- [sema/README.md](../sema/README.md) — semantic layer (morfo provides everything Sema needs via `events[].semantic`).
- [`src/docs/sema-implementation-guide.md`](../../docs/sema-implementation-guide.md) — convenciones doctrinales del API (Parte IV).