[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_785":786,"_787":788},"routes/_app.x.$handle.$name",{"_98":97,"_32":45,"_106":88,"_27":107,"_13":14,"_108":-5,"_11":109,"_110":111,"_112":113,"_114":115,"_116":117,"_20":-5,"_118":-5,"_119":-5,"_120":25,"_121":122,"_123":124,"_125":-5,"_126":-5,"_127":128},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_43":44,"_32":45,"_38":46,"_47":-5,"_48":25,"_49":50,"_51":50,"_52":53,"_54":-5,"_18":55,"_56":-5,"_57":25,"_58":-5,"_59":-5,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":-5,"_71":72,"_73":72,"_74":75,"_76":75,"_77":75,"_78":72,"_79":72,"_80":81,"_82":83,"_84":85,"_86":25},"version",182,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":25,"_27":28,"_29":28},"file",{"_30":31,"_32":33,"_34":20,"_35":37,"_38":39,"_40":14,"_41":42,"_24":25},"previous",{"_30":31,"_32":33,"_34":20,"_35":36},"deleted",false,"deletedHere","path","docs/roadmap.md","latestPath","fileId","45b8411a-798a-11f1-b04a-1607ee4eb77e","name","roadmap.md","fileType","content","# Kylä UI — Roadmap\n\nThe dependency-ordered plan for reaching v1. Each row links a PRD in the\n[issue tracker](issues/); vocabulary is in [`../CONTEXT.md`](../CONTEXT.md) and the\nload-bearing decisions are in [`adr/`](adr/). This doc is the synthesis — the\n\"what next and in what order\" — not a re-spec of any single feature.\n\n## Built\n\n- **Styling foundation** — `cn`, `tw` (token utilities with the mandatory `color:`\n hint), `variants`, `KylaProvider` + Mode, provisional token stylesheet.\n- **`Button`** — the reference component (typed variants → tokens, semantic\n element, forwarded ref, escape-hatch `className`, token focus ring). \"Built\"\n means the pattern is proven, not that it's at VT coverage parity — see\n ADR-0005's coverage-parity clause and item 2 below.\n- **Substrate proof** — `nbbaier/kyla-ui-spike`, all four spikes green (Radix\n Dialog under the React-18.2.0 pin, Twind + CSS-var tokens, Provider injection,\n `light-dark()` + `data-mode`).\n\n## Planned — dependency order\n\nEach PRD is `ready-for-agent`. Later rows assume earlier ones.\n\n| # | Feature | PRD | Depends on | Why it's here |\n|---|---------|-----|-----------|----------------|\n| 1 | **Structural scales & palette** | [`structural-scales-palette`](issues/structural-scales-palette/PRD.md) | — | Highest-leverage deferred item: fixed spacing/radius/type scales + real AA-checked palette, **conforming to the Val Town UI style guide** ([ADR-0005](adr/0005-val-town-visual-language-default-theme.md)). Where consistency actually lives; unblocks the set. Establishes the first test harness. |\n| 2 | **v1 zero-dep component set** | [`v1-component-set`](issues/v1-component-set/PRD.md) | 1 | Text/Heading, Card, Input, Textarea, Label, Badge, Stack, Box, Divider, Select — the rest of the importable core, following the `Button` pattern — plus a `Button` revision slice closing its VT variant/state coverage gap (ADR-0005). |\n| 3 | **Dialog (Radix-backed)** | [`dialog-radix`](issues/dialog-radix/PRD.md) | 2 | First headless-backed component, behind its own import path, out of the barrel. Exercises the hybrid split (ADR-0002) in real code. |\n| — | **Preview shell conventions** | [`gallery`](issues/gallery/PRD.md) (folded in) | — | Bring the `preview/` HTML shell in line with platform conventions (real `.html` file, no inline `\n \n \n

\n \n \n`;\n\nexport default async function (req: Request): Promise {\n const { pathname } = new URL(req.url);\n\n // view-source link → redirect to this val\n if (pathname === \"/source\") {\n return new Response(null, {\n status: 302,\n headers: { Location: parseVal().links.self.val },\n });\n }\n\n // serve any val file (transpiled to JS for .ts/.tsx) so the browser can run\n // the client bundle and its relative imports (./app.tsx, ../mod.ts, ...).\n if (pathname.endsWith(\".ts\") || pathname.endsWith(\".tsx\")) {\n return serveFile(pathname, import.meta.url);\n }\n\n return new Response(html, {\n headers: { \"content-type\": \"text/html; charset=utf-8\" },\n });\n}\n",[],[211,415],"bd982d70-d147-4681-9ef1-354e2a19b0a3","client.tsx","42cc926a-7987-11f1-814e-1607ee4eb77e",["D",1783375727322],"/** @jsxImportSource https://esm.sh/react@18.2.0 */\nimport React from \"https://esm.sh/react@18.2.0\";\nimport { createRoot } from \"https://esm.sh/react-dom@18.2.0/client\";\nimport { Preview } from \"./app.tsx\";\n\nconst root = document.getElementById(\"root\")!;\ncreateRoot(root).render();\n",[],[211,423],"4ff971c2-fb5e-4c5f-a8f7-d5d7cc872908","app.tsx","42cc23d4-7987-11f1-814e-1607ee4eb77e",["D",1783375727322],"/** @jsxImportSource https://esm.sh/react@18.2.0 */\nimport React from \"https://esm.sh/react@18.2.0\";\n\n// The real library — imported, never modified.\nimport { Button, cn, KylaProvider, tw, useKylaMode } from \"../mod.ts\";\nimport type { ColorToken } from \"../src/theme/tw.ts\";\nimport type { Mode } from \"../src/theme/provider.tsx\";\n\nconst VARIANTS = [\"primary\", \"subtle\", \"ghost\", \"danger\"] as const;\nconst SIZES = [\"sm\", \"md\", \"lg\"] as const;\n\nconst COLOR_TOKENS: ColorToken[] = [\n \"base\",\n \"elevated\",\n \"recessed\",\n \"fg\",\n \"fg-muted\",\n \"line\",\n \"hairline\",\n \"accent\",\n \"accent-fg\",\n \"danger\",\n];\n\n/** A titled section on an elevated card. */\nfunction Section({\n title,\n subtitle,\n children,\n}: {\n title: string;\n subtitle?: string;\n children: React.ReactNode;\n}) {\n return (\n \n

{title}

\n {subtitle && (\n

\n {subtitle}\n

\n )}\n

{children}

\n \n );\n}\n\n/** Small monospace label. */\nfunction Tag({ children }: { children: React.ReactNode }) {\n return (\n \n {children}\n \n );\n}\n\n/** Light / dark / system switcher, driven by the library's own mode hook. */\nfunction ModeSwitcher() {\n const { mode, setMode } = useKylaMode();\n const modes: Mode[] = [\"light\", \"dark\", \"system\"];\n return (\n

\n Mode\n \n {modes.map((m) => (\n setMode(m)}\n className={cn(\n \"rounded-md px-3 py-1 text-sm font-medium capitalize transition\",\n m === mode\n ? cn(tw.bg(\"accent\"), tw.text(\"accent-fg\"))\n : cn(tw.text(\"fg\"), tw.bg(\"elevated\", \"hover\")),\n )}\n >\n {m}\n \n ))}\n

\n \n );\n}\n\nfunction ButtonMatrix() {\n return (\n

\n {/* variants × sizes */}\n {VARIANTS.map((variant) => (\n

\n \n {variant}\n \n variant=\"{variant}\"\n

\n {SIZES.map((size) => (\n \n ))}\n \n

\n ))}\n

\n );\n}\n\nfunction TokenSwatches() {\n return (\n

\n {COLOR_TOKENS.map((token) => (\n \n \n

{token}

\n --kyla-{token}\n

\n ))}\n \n );\n}\n\nfunction WipBanner() {\n return (\n \n

\n 🚧 Preview / work in progress. This page renders the{\" \"}\n current Kylä UI surface — one component (Button) plus the theme\n system. Palette values are provisional and more components are on the way.\n

\n \n );\n}\n\nexport function Preview() {\n return (\n \n \n

\n {/* header */}\n

\n Kylä UI\n

\n Consistently styled components for Val Town apps. (Kylä ·\n Finnish for “village”.)\n

\n \n

\n\n \n\n \n \n \n\n \n

\n alert(\"Saved! (from Kylä Button)\")}\n >\n Save\n \n \n \n \n

\n \n\n \n \n \n\n \n

\n ✅ In place\n

Styling core — cn / tw / variants
KylaProvider + light / dark / system mode
Semantic design tokens
Button

\n 🔜 To come\n

The rest of the v1 component set
The real, AA-checked palette
Spacing / radius / type scales
Radix-backed components (e.g. Dialog)

\n \n\n \n Preview is illustrative — not a stable API.\n \n view source\n \n \n

\n \n \n );\n}\n",[],[211,430],["D",1783375727322],[281,282,283],[211],"6f86134b-51f8-4215-adb3-0cef19c2c19c",["D",1784058609992],[],[217,33],"54a387aa-0967-4741-9b4b-803276e7346a","val-town-style-guide.md","c81d8562-798e-11f1-8388-1607ee4eb77e","c798cbce-798e-11f1-b338-1607ee4eb77e",["D",1783578006344],"# Val Town UI style guide — design tokens reference\n\nResearch reference for ADR-0005 (`docs/adr/0005-val-town-visual-language-default-theme.md`)\nand the scales/palette PRD (`docs/issues/structural-scales-palette/PRD.md`). Extracted\n2026-07-06.\n\n## What was found, and from where\n\nVal Town's marketing/app site is a **Remix SSR** application, so a plain HTTP `GET` of each\n`https://www.val.town/_ui/` page returns the **real, server-rendered component\nmarkup** — every element with its full Tailwind utility class list. The token layer lives in\nthe site's compiled Tailwind **v4** stylesheet, linked from every page and served from\n`https://static2.esm.town/assets/tailwind-.css` (current hash at extraction time:\n`tailwind-Dy1Hj0e7.css`). That file contains the Tailwind v4 `@theme` block (the full\n`--color-*` scale in **oklch**, plus `--spacing`, `--radius-*`, `--text-*`, `--font-weight-*`)\n**and** Val Town's own semantic color aliases split across the light `@theme`/`:root` layer\nand a `.dark {…}` block.\n\n**This is the primary, authoritative source** and it is machine-readable end-to-end:\ncomponent class lists → utility classes → resolved token values, all from the live site.\n\nA **secondary** source — the val **`dcm31/townie-mobile`**, `frontend/style.css` (read via\nthe Val Town MCP `read_file`) — is the distilled token set its author hand-fed to Fable. It\nagrees with the live site on the design *language* (slate + sky, IBM Plex Sans, iA Writer\nQuattro eyebrows, dark-ink-on-accent, 8px radius) but its literal hex values are **Tailwind\nv3** (e.g. `--vt-sky: #38bdf8`), which differ numerically from the live site's Tailwind\n**v4** oklch derivations (`sky-400` → `#00bcff`). Reconciliation is called out below.\n\n### Colour-space note\nThe live tokens are **oklch** (Tailwind v4). Every hex in this doc is a **computed**\noklch→sRGB conversion (D65, standard sRGB transfer). Hexes are labelled as computed; the\noklch string is the source-of-truth value. Contrast ratios are likewise computed from those\nsRGB values.\n\n### Reconciliation: townie-mobile (v3 hex) vs live `_ui` (v4 oklch)\n\n| Role | townie `style.css` (v3 literal) | live `_ui` (v4 oklch → computed hex) | Agree? |\n| --- | --- | --- | --- |\n| Accent | `--vt-sky #38bdf8` (sky-400) | `sky-400` `oklch(74.6% .16 232.661)` → `#00bcff` | Same token name; v4 hex more saturated |\n| Deep accent | `--vt-sky-deep #0369a1` (sky-700) | `sky-700` `oklch(50% .134 242.749)` → `#0069a8` | Same name, v4 slightly different |\n| Border | `--vt-border #e2e8f0` (slate-200) | `slate-200` `oklch(92.9% .013 255.508)` → `#e2e8f0` | **Identical** |\n| Accent-fg | send btn `text-sky-950` on `bg-sky-400` | primary btn `text-sky-950` on `bg-sky-400` | **Identical convention** |\n\nBoth confirm **VT = Tailwind slate + sky**. Treat the **live `_ui` v4 oklch values as\ncurrent source of truth**; townie's hexes are the older/hand-distilled variant.\n\n---\n\n## 1. Color palette\n\n### 1a. Val Town semantic aliases (the actual theme layer)\n\nVT defines exactly **five** semantic color tokens, each aliased to a raw scale step, with a\nlight default (in the `@theme`/root layer) and a `.dark` override. Source:\n`tailwind-Dy1Hj0e7.css`, `:root`/`@theme` and `.dark{…}` blocks (verbatim property names).\n\n| Semantic token | Light → raw | Light hex (computed) | Dark → raw | Dark hex (computed) |\n| --- | --- | --- | --- | --- |\n| `--color-background` | `--color-white` | `#ffffff` | `--color-black` | `#000000` |\n| `--color-text` | `--color-black` | `#000000` | `--color-white` | `#ffffff` |\n| `--color-border` | `--color-slate-200` | `#e2e8f0` | `--color-slate-700` | `#314158` |\n| `--color-muted` | `--color-gray-600` | `#4a5565` | `--color-gray-300` | `#d1d5dc` |\n| `--color-shadow` | `--color-gray-50` | `#f8fafc`* | `--color-gray-900` | `#101828`* |\n\nVerbatim: `.dark{--color-text:var(--color-white);--color-background:var(--color-black);--color-border:var(--color-slate-700);--color-muted:var(--color-gray-300);--color-shadow:var(--color-gray-900)}`\nand light `--color-text:var(--color-black);--color-background:var(--color-white);--color-border:var(--color-slate-200);--color-muted:var(--color-gray-600);--color-shadow:var(--color-gray-50)`.\n(*`--color-shadow` gray hexes are approximate; used as a shadow tint, not a surface.)\n\nNotable: **dark-mode background is true black** (`#000`) with true-white text — an OLED-style\nmaximum-contrast choice, not a dark-gray. There is **no** semantic token for elevated /\nrecessed surfaces or for accent — those come from raw `sky-*`/`slate-*` utilities in the\ncomponents (§1b, §5).\n\n### 1b. Raw scale steps used across components (Tailwind v4 oklch)\n\nEvery value below is a class observed in live `_ui` component markup. oklch is the source\nvalue; hex is computed. Full scales for slate/sky/rose/emerald/gray exist in the file; these\nare the steps actually referenced.\n\n**Neutrals — `slate` (structure) and `gray` (muted text)**\n\n| Token | oklch | Hex (computed) | Role in `_ui` |\n| --- | --- | --- | --- |\n| `white` | `#fff` | `#ffffff` | Base surface (light) |\n| `slate-50` | `oklch(98.4% .003 247.858)` | `#f8fafc` | Secondary button fill (light); read-only input bg |\n| `slate-100` | `oklch(96.8% .007 247.896)` | `#f1f5f9` | Default button fill; soft/filled input fill (light) |\n| `slate-200` | `oklch(92.9% .013 255.508)` | `#e2e8f0` | **Border** (`--color-border` light) |\n| `slate-300` | `oklch(86.9% .022 252.894)` | `#cad5e2` | Input border (light); hover border on filled input |\n| `slate-400` | `oklch(70.4% .04 256.788)` | `#90a1b9` | Input hover border (light) |\n| `slate-700` | `oklch(37.2% .044 257.287)` | `#314158` | **Border** (`--color-border` dark); input border (dark) |\n| `slate-800` | `oklch(27.9% .041 260.031)` | `#1d293d` | Default button fill (dark); soft input fill (dark) |\n| `slate-900` | `oklch(20.8% .042 265.755)` | `#0f172b` | Secondary button fill (dark); read-only input bg (dark) |\n| `slate-950` | `oklch(12.9% .042 264.695)` | `#020618` | (deepest neutral) |\n| `gray-300` | `oklch(87.2% .01 258.338)` | `#d1d5dc` | **Muted text** (`--color-muted` dark) |\n| `gray-600` | `oklch(44.6% .03 256.802)` | `#4a5565` | **Muted text** (`--color-muted` light) |\n| `black` | `#000` | `#000000` | Text (light); base (dark) |\n\n**Accent — `sky`**\n\n| Token | oklch | Hex (computed) | Role in `_ui` |\n| --- | --- | --- | --- |\n| `sky-50` | `oklch(97.7% .013 236.62)` | `#f0f9ff` | Secondary/clear button hover fill (light) |\n| `sky-100` | `oklch(95.1% .026 236.824)` | `#dff2fe` | Default button hover fill; active card (light) |\n| `sky-200` | `oklch(90.1% .058 230.902)` | `#b8e6fe` | Default button active; accent text (dark) |\n| `sky-300` | `oklch(82.8% .111 230.318)` | `#74d4ff` | **Input focus ring** |\n| `sky-400` | `oklch(74.6% .16 232.661)` | `#00bcff` | **Primary button fill (light)** — the accent |\n| `sky-500` | `oklch(68.5% .169 237.323)` | `#00a6f4` | **Button focus ring**; input focus border |\n| `sky-700` | `oklch(50% .134 242.749)` | `#0069a8` | **Primary button fill (dark)** |\n| `sky-800` | `oklch(44.3% .11 240.79)` | `#00598a` | Accent text on light (hover/aria-current) |\n| `sky-950` | `oklch(29.3% .066 243.157)` | `#052f4a` | **Text on `sky-400` primary fill (light)** |\n\n**Danger — `rose`; Success — `emerald`**\n\n| Token | oklch | Hex (computed) | Role |\n| --- | --- | --- | --- |\n| `rose-50` | `oklch(96.9% .015 12.422)` | `#fff1f2` | Private privacy-badge bg |\n| `rose-300` | `oklch(81% .117 11.638)` | `#ffa1ad` | **Danger button fill (light)** |\n| `rose-400` | `oklch(71.2% .194 13.428)` | `#ff637e` | Danger button hover; focus ring |\n| `rose-800` | `oklch(45.5% .188 13.697)` | `#a50036` | **Danger button fill (dark)**; badge text |\n| `rose-950` | `oklch(27.1% .105 12.094)` | `#4d0218` | **Text on danger fill (light)** |\n| `emerald-100` | `oklch(95% .052 163.051)` | `#d0fae5` | Public privacy-badge bg |\n| `emerald-400` | `oklch(76.5% .177 163.223)` | `#00d492` | **Success/green button fill (light)** |\n| `emerald-950` | `oklch(26.2% .051 172.552)` | `#002c22` | Text on success fill (light) |\n\nAlso referenced: `red-300`/`red-700` for input invalid rings; `amber-*` and `blue-*` for\ncallout variants; `orange-*` for the \"unlisted\" privacy badge.\n\n---\n\n## 2. Spacing scale\n\n`--spacing: .25rem` → **base unit 4px** (Tailwind v4 default; all `gap-*`/`p-*`/`h-*`/`w-*`\nutilities are multiples of it). No bespoke VT spacing tokens. Container widths are also\ndefined (`--container-xs 20rem … --container-7xl 80rem`) if a max-width scale is needed.\n\nComponent-level spacing is captured per component in §5.\n\n---\n\n## 3. Border-radius scale\n\nFrom the `@theme` block (verbatim):\n\n| Token | rem | px | Where used in `_ui` |\n| --- | --- | --- | --- |\n| `--radius-xs` | `.125rem` | 2px | — |\n| `--radius-sm` | `.25rem` | 4px | — |\n| `--radius-md` | `.375rem` | 6px | — |\n| `--radius-lg` | `.5rem` | **8px** | **Buttons, inputs, selects, textareas, cards, sidebar panels** (the workhorse) |\n| `--radius-xl` | `.75rem` | 12px | Large buttons; callouts |\n| `--radius-2xl` | `1rem` | 16px | — |\n| `--radius-3xl` | `1.5rem` | 24px | — |\n| `rounded-full` | 9999px | — | Privacy badges, pills |\n\nCanonical control radius = **8px (`rounded-lg`)**; large controls step up to 12px\n(`rounded-xl`). Matches townie's \"8px radius.\"\n\n---\n\n## 4. Typography\n\n**Font families** (from `tailwind-.css` `html` rule + `app.css` `@font-face`)\n\n| Role | Stack | Source |\n| --- | --- | --- |\n| Sans (body/UI) | `\"IBM Plex Sans\", -apple-system, sans-serif` | `html,:host{…font-family:IBM Plex Sans,-apple-system,sans-serif;line-height:1.5}` |\n| Mono | `\"iA Writer Mono\", \"Menlo\", \"Consolas\", \"ui-monospace\", monospace` | `--font-mono` |\n| Eyebrow / display | `\"iA Writer Quattro\"` (weights 400/700, normal+italic) | `app.css` `@font-face` blocks |\n\n**Type scale** (`--text-*` with paired `--line-height`, verbatim)\n\n| Token | size | line-height (computed) | approx px |\n| --- | --- | --- | --- |\n| `text-xs` | `.75rem` (12px) | `calc(1 / .75)` = 1.333 | 12 / 16 |\n| `text-sm` | `.875rem` (14px) | `calc(1.25 / .875)` = 1.429 | 14 / 20 |\n| `text-base` | `1rem` (16px) | `1.5` | 16 / 24 |\n| `text-lg` | `1.125rem` (18px) | `calc(1.75 / 1.125)` = 1.556 | 18 / 28 |\n| `text-xl` | `1.25rem` (20px) | `calc(1.75 / 1.25)` = 1.4 | 20 / 28 |\n| `text-2xl` | `1.5rem` (24px) | `calc(2 / 1.5)` = 1.333 | 24 / 32 |\n| `text-3xl` | `1.875rem` (30px) | `1.2` | 30 / 36 |\n\nControls (buttons/inputs) default to `text-sm` (14/20). `text-[11px]` is used for privacy\nbadges. Default body line-height is `1.5`.\n\n**Font weights** (`--font-weight-*`): normal 400, medium 500, semibold 600, bold 700,\nextrabold 800. Buttons are **`font-bold` (700)**; badges are **`font-semibold` (600)**;\ninputs/selects `font-normal` (400).\n\n---\n\n## 5. Component-level styling specs\n\nAll class lists below are verbatim from live `_ui` SSR markup (`www.val.town/_ui/`),\ncondensed to the meaningful tokens (dropped the long `[&:not([disabled])]:` guards where they\nonly wrap a hover/active listed here).\n\n### Button (`/_ui/button`)\n**Base:** `inline-flex items-center justify-center gap-x-2 shrink-0 whitespace-nowrap\nselect-none cursor-pointer disabled:cursor-not-allowed disabled:opacity-50 outline-0\nfocus-visible:ring-2 transition font-bold`\n\n**Sizes:** `sm` = `text-sm h-8 px-3 rounded-lg` · `md`(default) = `text-sm h-10 px-4\nrounded-lg` · `lg` = `text-base h-12 px-5 rounded-xl`. Icon-only appends `!px-0 w-8` (sm) /\n`w-10` (md).\n\n**Focus ring:** `ring-2 ring-sky-500` (rose-400 for danger, emerald-500 for green,\nslate-700 for blend).\n\n| Variant | Light fill / text / border | Light hover → active | Dark fill / text | Dark hover → active |\n| --- | --- | --- | --- | --- |\n| `default` | `bg-slate-100 text-slate-800` | `bg-sky-100 text-sky-800` → `bg-sky-200` | `bg-slate-800 text-slate-200` | `bg-sky-900 text-sky-200` → `bg-slate-800` |\n| `primary` | `bg-sky-400 text-sky-950` border-transparent | `bg-sky-500` → `bg-sky-600` | `bg-sky-700 text-white` | `bg-sky-600` → `bg-sky-700` |\n| `secondary` | `bg-slate-50 text-black border-slate-200` | `bg-sky-50 text-sky-800 border-sky-200` → `bg-sky-100` | `bg-slate-900 text-white border-slate-800` | `bg-sky-900 text-sky-200 border-sky-500` → `bg-slate-800` |\n| `clear` | `text-black` (no fill) | `text-sky-800 bg-sky-500/10` → `bg-sky-500/5` | `text-white` | `text-sky-200 bg-sky-500/40` → `bg-sky-500/20` |\n| `danger` | `bg-rose-300 text-rose-950` border-transparent | `bg-rose-400` → `bg-rose-500` | `bg-rose-800 text-white` | `bg-rose-700` → `bg-rose-800` |\n| `green` | `bg-emerald-400 text-emerald-950` border-transparent | `bg-emerald-500` → `bg-emerald-600` | `bg-emerald-700 text-white` | `bg-emerald-600` → `bg-emerald-700` |\n| `blend` | `mix-blend-color-burn bg-slate-500 text-black border-slate-700` | `bg-slate-600` → `bg-slate-700` | `mix-blend-color-dodge bg-slate-500 text-white border-slate-400` | `bg-slate-400` → `bg-slate-300` |\n\nKey convention: **primary/danger/green fills use a dark-ink-on-bright-color pairing in\nlight mode** (`text-sky-950`/`text-rose-950`/`text-emerald-950`) and flip to **white ink on\na deeper fill in dark mode** (`text-white` on `sky-700`/`rose-800`/`emerald-700`).\n\n### Input / Select / Textarea (`/_ui/input`, `/select`, `/textarea`)\n**Base:** `block w-full border outline-0 transition disabled:cursor-not-allowed\ndisabled:opacity-50 text-sm h-10 px-3 rounded-lg`. sm = `h-8 px-2`.\n\n- **Default variant:** `bg-background text-black border-slate-300`, hover\n `border-slate-400`; dark `text-white border-slate-700`, hover `border-slate-600`. (Note it\n uses the semantic `bg-background` token, so field bg = white/black by mode.)\n- **Filled/soft variant:** `bg-slate-100 text-black border-transparent`, hover\n `border-slate-300`; dark `bg-slate-800 text-white`, hover `border-slate-700`.\n- **Focus:** `focus-visible:ring-2 focus-visible:ring-sky-300` + `focus-visible:border-sky-500`.\n- **Invalid** (`aria-invalid`/`user-invalid`): `ring-red-300 border-red-300` (dark\n `ring-red-700 border-red-700`), hover `border-red-400`.\n- **Read-only:** `read-only:bg-slate-50` (dark `bg-slate-900`).\n- **Disabled:** `opacity-50 cursor-not-allowed`.\n- **Select** adds `appearance-none pr-10 cursor-pointer`; **Textarea** adds `h-auto py-2`;\n a `code` content variant adds `font-mono`.\n\n### Card (`/_ui/card`)\nSurface uses `bg-background`, `border`, `rounded-lg`, `transition`; hover\n`hover:border-blue-400 dark:hover:border-blue-600 hover:shadow-lg` (note: cards hover\n**blue**, not sky). BigCard is the larger variant.\n\n### Callout (`/_ui/callout`)\n**Base:** `flex flex-wrap items-center gap-2 pl-4 pr-2 py-2 min-h-12 text-sm rounded-xl\nborder`. Color variants (light → dark):\n- info/blue: `text-blue-800 bg-blue-50 border-blue-100` → `text-blue-200 bg-blue-950 border-blue-900`\n- warning/amber: `text-amber-800 bg-amber-100 border-amber-200` → `text-amber-100 bg-amber-950 border-amber-900`\n\n### Privacy Badge (`/_ui/privacy-badge`)\n**Base:** `inline-flex items-center justify-center font-semibold text-[11px] h-5\nmin-w-[56px] rounded-full px-2`. Variants:\n- public: `text-emerald-800 bg-emerald-100 saturate-50`\n- private: `text-rose-800 bg-rose-50`\n- unlisted: `text-orange-800 bg-orange-50`\n\n### Dropdown / panel (`/_ui/dropdown`)\nFloating panel: `bg-background rounded-lg shadow-lg` (width `w-64`, margin `m-2`).\n\n### Shadows\nTailwind defaults (`shadow-lg` on cards/panels/dropdowns). The `--color-shadow` semantic\ntoken (gray-50 light / gray-900 dark) tints shadow color per mode. townie additionally used\ncustom `0 2px 12px rgba(15,23,42,.05)` composer shadows (slate-tinted).\n\n---\n\n## 6. Mapping onto Kylä tokens\n\nKylä `--kyla-*` → Val Town values. **Both light and dark are now primary-sourced** from the\nlive `_ui` Tailwind v4 theme (semantic aliases + component usage). Hexes are computed from\noklch.\n\n| Kylä token | VT source | Light | Dark | Notes |\n| --- | --- | --- | --- | --- |\n| `--kyla-base` | `--color-background` | `#ffffff` (white) | `#000000` (**true black**) | VT dark base is pure black (OLED), not gray. |\n| `--kyla-elevated` | *(no VT token)* | `#ffffff` + shadow | `#0f172b` (`slate-900`) | VT has no elevated-fill token in light; raise via `shadow-lg`. In dark, `slate-900` (secondary-button fill) is the natural raised surface. See Gaps. |\n| `--kyla-recessed` | component `bg-slate-100`/`bg-slate-50` | `#f1f5f9` (`slate-100`) | `#1d293d` (`slate-800`) | Filled input / default-button wells. `slate-50 #f8fafc` is a shallower recess (secondary btn, read-only). |\n| `--kyla-fg` | `--color-text` | `#000000` | `#ffffff` | true-black / true-white. |\n| `--kyla-fg-muted` | `--color-muted` | `#4a5565` (`gray-600`) | `#d1d5dc` (`gray-300`) | VT's real, now-sourced muted token — AA-safe both modes (§7). Supersedes the earlier `slate-700` guess; the two are near-equivalent (`gray-600` 7.56:1, `slate-700` 10.36:1) — either is fine, `gray-600` is the literal VT value. Definitely **not** `slate-400`. |\n| `--kyla-line` | `--color-border` | `#e2e8f0` (`slate-200`) | `#314158` (`slate-700`) | The one VT border token. Note controls use `slate-300`/`slate-700` for *field* borders — a touch stronger than the panel border. |\n| `--kyla-hairline` | *(no VT token)* | `#f1f5f9` (`slate-100`) | `#1d293d` (`slate-800`) | VT has no lighter-than-border token; propose one step lighter (light) / the elevated fill (dark). See Gaps. |\n| `--kyla-accent` | primary button fill | `#00bcff` (`sky-400`) | `#0069a8` (`sky-700`) | VT's accent **changes by mode**: bright sky-400 in light, deeper sky-700 in dark. Focus rings use `sky-500 #00a6f4`. |\n| `--kyla-accent-fg` | primary button text | `#052f4a` (`sky-950`, dark ink) | `#ffffff` (white) | Dark ink on the bright light-mode fill; white on the deep dark-mode fill. **Never white on sky-400** (§7). |\n| `--kyla-danger` | danger button fill | `#ffa1ad` (`rose-300`) | `#a50036` (`rose-800`) | Pale rose w/ dark ink (light) → deep rose w/ white (dark). |\n| `--kyla-danger-fg` *(implied)* | danger button text | `#4d0218` (`rose-950`) | `#ffffff` | Kylä has no danger-fg token — see Gaps. |\n| `--kyla-radius` | `--radius-lg` | `8px` | `8px` | Scale 2/4/6/8/12/16/24; large controls 12px. |\n\nScale-level (needed by the PRD):\n\n| Concept | VT value (light = dark unless noted) |\n| --- | --- |\n| Spacing base | `--spacing: .25rem` = 4px |\n| Radius scale | 2 / 4 / 6 / 8 / 12 / 16 / 24 px (`xs…3xl`); control default 8 |\n| Sans | `\"IBM Plex Sans\", -apple-system, sans-serif` |\n| Mono | `\"iA Writer Mono\", \"Menlo\", \"Consolas\", \"ui-monospace\", monospace` |\n| Eyebrow/display | `\"iA Writer Quattro\"` (400/700) |\n| Body type | `text-base` 16px / lh 1.5; controls `text-sm` 14/20 |\n| Weights | 400 / 500 / 600 / 700 / 800; buttons 700, badges 600 |\n| Hues | accent = sky · danger = rose · success = emerald · neutral = slate/gray |\n\n---\n\n## 7. Gaps and AA concerns\n\n### Gaps — Kylä tokens with no direct VT semantic equivalent\n\n- **`--kyla-elevated`, `--kyla-recessed`, `--kyla-hairline`:** VT's semantic layer is only\n `background / text / border / muted / shadow`. There is **no** token for a second surface\n level. In light mode VT elevates by shadow over the same white; recessed/hairline surfaces\n come from raw `slate-50`/`slate-100` fills at the component level. The proposed values are\n the observed component fills, not named VT tokens — reasonable but an extrapolation.\n- **`--kyla-danger-fg` / accent-fg split:** VT expresses \"ink on a colored fill\" per\n component (dark-950 in light, white in dark) rather than as a token. Also, VT uses several\n distinct accent roles a single `--kyla-accent`/`--kyla-accent-fg` can't hold: **fill**\n (`sky-400`/`sky-700`), **focus ring** (`sky-500`, inputs `sky-300`), and **accent text on\n a surface** (`sky-800` light / `sky-200` dark, used for hover/aria-current). Consider\n `--kyla-accent-ring` and `--kyla-accent-text` in addition to fill+fg.\n\n### VT tokens/roles Kylä has no home for\n\n- **`--color-shadow`** (gray-50 light / gray-900 dark) — a mode-aware shadow tint; Kylä has\n no shadow token.\n- **Field border ≠ panel border:** inputs use `slate-300`/`slate-700`, panels use\n `slate-200`/`slate-700` (`--color-border`). Kylä's single `--kyla-line` flattens this.\n- **Semantic status set beyond danger:** VT ships `emerald` (success/green button, public\n badge), `amber`/`blue` (callouts), `orange` (unlisted badge). Kylä has only `danger`.\n- **`blend` button** (`mix-blend-color-burn`/`-dodge`) — a mode-adaptive technique, no token.\n\n### WCAG AA (ratios **computed** from oklch→sRGB; 4.5:1 body, 3:1 large/UI)\n\n| Foreground | Background | Ratio | Verdict |\n| --- | --- | --- | --- |\n| `text` black | `background` white (light) | **21.0:1** | Pass AAA |\n| `text` white | `background` black (dark) | **21.0:1** | Pass AAA |\n| `muted` gray-600 | white (light) | **7.56:1** | Pass |\n| `muted` gray-300 | black (dark) | **14.26:1** | Pass |\n| primary `sky-950` | `sky-400` fill (light) | **6.37:1** | Pass |\n| primary white | `sky-700` fill (dark) | **5.86:1** | Pass |\n| default `slate-800` | `slate-100` fill (light) | **13.34:1** | Pass |\n| default-hover `sky-800` | `sky-100` (light) | **6.53:1** | Pass |\n| danger `rose-950` | `rose-300` fill (light) | **8.19:1** | Pass |\n| danger white | `rose-800` fill (dark) | **7.92:1** | Pass |\n| green `emerald-950` | `emerald-400` fill (light) | **7.83:1** | Pass |\n| `slate-700` (field border/text) | white | **10.36:1** | Pass |\n| **white** | **`sky-400`** (anti-pattern) | **2.18:1** | **FAIL** — do not put white on the light accent; VT correctly uses `sky-950`. |\n\nTakeaways for Kylä:\n1. Every default VT foreground/surface pairing clears AA comfortably (5.9–21:1) in **both**\n modes — safe to adopt wholesale.\n2. `--kyla-accent-fg` must be **dark ink (`sky-950`) in light** and **white in dark**; a\n single fixed value can't serve both because `sky-400` needs dark ink (white fails at\n 2.18:1) while `sky-700` needs white.\n3. `--kyla-fg-muted` = `gray-600` (light) / `gray-300` (dark) is AA-safe; keep the mode\n split rather than one value.\n4. Note the deliberate **true-black dark background** — visually aggressive (21:1); fine for\n AA, but worth a conscious call vs a softer `slate-950 #020618` if Kylä prefers less glare.\n\n---\n\n## 8. Sources\n\n**Primary — live `_ui` (Remix SSR, plain HTTPS GET; class lists verbatim):**\n1. `https://www.val.town/_ui/button`, `/callout`, `/card`, `/dropdown`, `/input`, `/select`,\n `/textarea`, `/forms`, `/privacy-badge` — server-rendered component markup with full\n Tailwind class lists (cited per component in §5).\n2. `https://static2.esm.town/assets/tailwind-Dy1Hj0e7.css` — compiled Tailwind v4 stylesheet:\n the `@theme` `--color-*` (oklch) / `--spacing` / `--radius-*` / `--text-*` /\n `--font-weight-*` tokens, the `html` font-family rule, and VT's semantic aliases in the\n root layer + `.dark{…}` block (all quoted verbatim in §1a, §3, §4). Hash read from the\n pages' `` tags.\n3. `https://static2.esm.town/assets/_app-*.css` — `@font-face` for iA Writer Quattro\n (400/700, normal+italic).\n\n**Secondary — distilled token set (via Val Town MCP `read_file`):**\n4. `dcm31/townie-mobile` → `frontend/style.css` — `--vt-sky #38bdf8`, `--vt-sky-deep\n #0369a1`, `--vt-border #e2e8f0` (Tailwind **v3** hexes), IBM Plex Sans body, iA Writer\n Quattro eyebrow (10px/700/0.14em uppercase). Reconciled against the live v4 values in the\n intro; agrees on token names and the dark-ink-on-accent convention, differs on exact hex.\n\n**Value resolution / conversion:**\n5. oklch→sRGB hex and all §7 contrast ratios are **computed** (D65 sRGB), not read from a\n source. oklch strings in §1 are the source-of-truth values.\n\n**Informal, non-verbatim signal (not used for any concrete value in this doc):**\n6. `https://www.val.town/secret-styleguide` — Val Town's broader internal\n component library (Tag, Alert, Link, Pagination, Table, Tooltip, Card/\n ProjectCard/BigCard, and ~20 more, many product-specific). Unlike the `_ui/*`\n pages, this one does not expose Tailwind class attributes to a plain fetch —\n only rendered layout/component names are recoverable. Cited in the\n `v1-component-set` PRD's VT Parallelism Audit purely as a qualitative signal\n (e.g. confirming Card is really \"ProjectCard,\" or that \"Tag\" is the closer\n analog to a generic Badge) — never as a source of hex/class values the way\n §1–§5 are.\n\nNothing here is invented: every token traces to a CSS property name or a component class\nlist; every hex/ratio is a labelled computation from a sourced oklch value.\n",[],[217,451,444],"reference","7bfbe88f-a1d2-4bed-ba24-1cf295c3ee4b",98,["D",1783378956608],[278],[217,451],"0915f809-3f54-4924-8765-185d4f1f95d1","PRD.md","45c41f76-798a-11f1-99dd-1607ee4eb77e","45627c76-798a-11f1-b04a-1607ee4eb77e",["D",1783578006344],"# PRD: v1 zero-dependency component set\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n> Builds out the rest of the v1 component inventory (see the\n> [roadmap](../../roadmap.md)), following the `Button` reference. Depends on the\n> [structural scales & palette](../structural-scales-palette/PRD.md)\n> foundation for spacing/type. Excludes the Radix-backed `Dialog`\n> ([its own PRD](../dialog-radix/PRD.md)).\n\n## Problem Statement\n\nKylä ships exactly one component (`Button`). To build a real app — even the todo\nStarter — a consumer needs text, layout, form, and container primitives. Without\nthem they drop to raw HTML styled with hand-written Twind, which reintroduces the\nper-app inconsistency Kylä exists to prevent, and loses the bounded accessibility\nguarantees (label association, focus ring, semantic elements) that come baked into\nKylä components.\n\n## Solution\n\nShip the v1 zero-dependency visual component set plus the one styled-native\ncomponent, each authored exactly like `Button`: typed variant props mapped to\ntokens via `variants()`, a semantic HTML element, forwarded ref + rest props, a\ntoken-based visible focus ring where interactive, an escape-hatch `className`\nmerged last via `cn()`, and ADR-0003's bounded accessibility baseline. Spacing and\ntype come from the structural scale tokens, so the set is consistent with itself\nand with anything built on top of it.\n\n**Inventory:** `Text`/`Heading`, `Card`, `Input`, `Textarea`, `Label`, `Badge`,\n`Stack`, `Box`, `Divider`, and styled-native `Select` — plus a **revision slice\nfor `Button`**, closing the VT variant/state coverage gap flagged by ADR-0005's\ncoverage-parity clause (the roadmap marks `Button` \"Built,\" but built ≠ at\nparity).\n\n## User Stories\n\n1. As a consumer, I want a `Text` component with typed size/weight/tone props, so that body copy uses the type scale without me choosing `text-*` classes.\n2. As a consumer, I want a `Heading` component (or `Text as=\"h1\">`), so that headings are semantic and on-scale.\n3. As a consumer, I want a `Card` with surface and padding variants, so that I can group content on an elevated surface consistently.\n4. As a consumer, I want an `Input` with a visible token focus ring and disabled state, so that text entry looks and behaves on-system.\n5. As a consumer, I want a `Textarea` matching `Input`, so that multi-line entry is consistent with single-line.\n6. As a consumer, I want a `Label` that associates with a field via `htmlFor`, so that clicking the label focuses the input and screen readers announce it.\n7. As a consumer, I want a `Badge` with typed tones, so that I can show status/labels on-system.\n8. As a consumer, I want a `Stack` layout primitive with a direction and a gap drawn from the spacing scale, so that I lay out children without hand-writing flex + gap classes.\n9. As a consumer, I want a `Box` primitive, so that I have a styled generic container with the escape hatch when no semantic component fits.\n10. As a consumer, I want a `Divider`, so that I can separate content with an on-system hairline.\n11. As a consumer, I want a `Select` that looks on-system but keeps native ``; sizes matching `Input`. VT adds\n `appearance-none pr-10 cursor-pointer` (§5) — match that base styling.\n- **Dependency:** consumes the scale tokens from the\n [scales PRD](../structural-scales-palette/PRD.md). If that lands first,\n components reference scale tokens directly; the spacing/type props map onto\n those steps.\n- **Accessibility (ADR-0003):** real `` ↔ field `id` association;\n correct semantic elements; token visible focus; no broken native keyboard\n behavior; AA contrast inherited from the default palette. Anything needing\n custom ARIA is out — that's the Radix tier.\n- **Public surface unchanged in shape:** finished components + `cn()` + Provider.\n No headless primitives exposed.\n\n## VT Parallelism Audit (ADR-0005 coverage parity)\n\nPer-component record of what the ADR-0005 coverage-parity clause requires:\ndoes a VT counterpart exist, what does it cover, and where does Kylä's plan\nmatch, intentionally diverge, or have a real gap. Sourced primarily from\n`docs/reference/val-town-style-guide.md` §5 (verbatim `_ui` classes — the\nauthoritative source). Where a component's only VT signal comes from\n`val.town/secret-styleguide` (Val Town's broader internal component library,\nnot the sourced `_ui` reference), that's called out explicitly as informal —\nthat page doesn't expose class attributes over a plain fetch, so nothing from\nit is a verbatim spec the way §5's `_ui` entries are.\n\n| Kylä component | VT counterpart | Parity status |\n| --- | --- | --- |\n| `Button` | `/_ui/button` | **Gap, tracked** — [ticket 04](issues/04-button-variant-parity.md): 4 of 7 color variants covered, icon-only sizing missing. |\n| `Text`/`Heading` | No componentized VT equivalent; VT's type scale/weights (§4) apply directly. `secret-styleguide`'s \"Page Heading\" is a same-shaped signal (large heading at two sizes) but not a sourced spec. | **No gap to close** — use VT's type-scale steps for `size`/`weight`; there's no VT variant count to match since VT doesn't ship this as a reusable component. |\n| `Card` | `/_ui/card` — in VT's own internal library this is the \"ProjectCard\"/\"BigCard\" family (`secret-styleguide`), i.e. a domain-specific project tile, not a generic container primitive. | **Real mismatch, not a coverage gap.** VT's card is flat `bg-background` + `border`, elevating only via `hover:shadow-lg` + `hover:border-blue-400` (§5) — it never uses a raised or inset *fill*. Kylä's `surface: elevated/recessed` assumes a fill-based hierarchy that has no VT counterpart anywhere. This is ADR-0005's already-recorded intentional divergence (Kylä keeps its own richer surface hierarchy), but it means the component's *default* rendering, not just its token palette, needs a deliberate call — see the Implementation Decisions bullet above. |\n| `Input`/`Textarea` | `/_ui/input`, `/_ui/textarea` | **Gap:** filled/soft variant and `read-only` treatment (§5) not yet in the pinned surface. |\n| `Label` | No dedicated VT primitive — VT associates labels inline within its field markup rather than shipping a standalone component. | **No gap to close** — Kylä's standalone `Label` is a Kylä-only primitive (needed because Kylä's components are more granular than VT's field markup), not a port. |\n| `Badge` | No generic VT Badge. `/_ui/privacy-badge` is a narrow, product-specific analog (public/private/unlisted only). `secret-styleguide`'s \"Tag\" (5 states: neutral/danger/positive/warning/fun, at 3 sizes) is the closer *conceptual* analog but isn't a sourced spec. | **No gap tracked here** — tone set stays a Kylä design call. If revisited later: `positive` would map onto the already-landed `success` token; `warning`/`fun` have no home in Kylä's current token vocabulary and shouldn't be invented ad hoc inside a component PRD. |\n| `Stack`/`Box`/`Divider` | No VT primitive equivalent. `secret-styleguide`'s \"Bento layout system\" is the nearest signal (a product-layout grid for arranging project cards), not a reusable primitive. | **No gap to close** — Kylä-only design calls, same reasoning as `Badge`. |\n| `Select` | `/_ui/select` | **Gap:** `appearance-none pr-10 cursor-pointer` (§5) not yet in the pinned surface. |\n\nTakeaway: three components (`Text`/`Heading`, `Label`, `Stack`/`Box`/`Divider`)\nand `Badge` have no VT surface to port at all — that's a legitimate parity\nverdict, not an unaudited hole. `Card` is the one case where \"port VT's\nvalues\" and \"keep Kylä's structure\" actively pull in different directions and\nneeds an explicit default decision, not just a token mapping.\n\n## Testing Decisions\n\n- **What makes a good test:** it asserts the component's *external* output and\n behavior — the rendered element, the token classes it emits, and its\n accessibility wiring — never the internal `variants()`/`cn()` call. Testing the\n emitted class string via the rendered HTML also guards the silent Twind\n \"missing `color:` hint\" failure, since a dropped hint shows up as an absent\n token class.\n- **Seam (highest available):** **server-render the component to an HTML string**\n (`renderToStaticMarkup`) and assert on the markup. Uniform across the set.\n - Assert the semantic element (``, `

`, `<select>`, `<hr>`,\n     heading tags for `Heading`).\n   - Assert token utility classes are present for the chosen variant/tone (e.g.\n     `Badge tone=\"danger\"` emits `bg-[color:var(--kyla-danger)]`).\n   - Assert accessibility wiring: `Label htmlFor` matches an `Input id`; `Input`\n     forwards `type`; `disabled`/`aria-invalid` render; the focus-ring classes\n     are present on interactive components.\n   - Assert `className` wins over the component's own conflicting class (the\n     `cn()` contract).\n- **Modules tested:** every component in `src/components/`.\n- **Prior art:** the harness established by the\n  [scales PRD](../structural-scales-palette/PRD.md); if this ships first, it\n  establishes the render-to-HTML harness itself. `Button` is the reference for\n  what a component's rendered output should look like.\n\n## Out of Scope\n\n- **`Button`'s polymorphic rendering** (VT's Router Link / external-link button\n  forms) — needs a Slot-style primitive Kylä doesn't have yet. Flagged by the\n  variant-parity audit, not built here.\n- **`Dialog`** and any Radix-backed component — [separate PRD](../dialog-radix/PRD.md).\n- v1.1+ deferred components: `Checkbox`, `Radio`, `Spinner`, `Alert`, then\n  `Popover`, `Menu`, `Tabs`, `Tooltip`, `Combobox`, `Toast`, `Table`.\n- The **Gallery** rendering of these components — [separate PRD](../gallery/PRD.md).\n- Defining the scales themselves — [scales PRD](../structural-scales-palette/PRD.md).\n\n## Further Notes\n\n- Building the set will dogfood the scale tokens and likely surface gaps (as\n  `Button` surfaced the state-prefixed token-utility gap). Feed those back into\n  the scales/`tw` layer rather than working around them in a component.\n- Keep each component small enough that the `Button` pattern stays legible; the\n  uniformity is the point.\n",[],[217,465,466,458],"issues","v1-component-set","f6c92ac2-2025-4b56-b48f-4a0095db9ead","04-button-variant-parity.md","9686e794-7b5c-11f1-a8cd-1607ee4eb77e","7d593b50-7b2a-11f1-801b-1607ee4eb77e",["D",1783578006344],8,"# 04 · Button variant & state coverage parity with VT\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: v1 zero-dependency component set](../PRD.md)\n\n## What to build\n\nA **revision** to the existing `Button` (`src/components/button.tsx`), not a\nrewrite: close the coverage gap between Kylä's 4 shipped variants and VT's 7\n(`docs/reference/val-town-style-guide.md` §5), plus VT's icon-only sizing\nconvention. Kylä's prop _names_ stay its own (ADR-0005) — this ticket ports\n_coverage_, not vocabulary.\n\nEnd-to-end behavior:\n\n- `variant` gains an unbordered filled-neutral member (mirrors VT `default`:\n  `bg-slate-100`/`text-slate-800` light, `bg-slate-800`/`text-slate-200` dark\n  — i.e. `--kyla-recessed`/`--kyla-fg`), named `neutral`.\n- `variant` gains a `success`-backed member (mirrors VT `green`), using the\n  `success`/`success-fg` tokens already landed in v152 — no token work needed.\n- `variant` gains `blend`, reproducing VT's mode-adaptive technique\n  (`mix-blend-color-burn` light / `mix-blend-color-dodge` dark) over\n  `--kyla-recessed`, so the button visually tints to whatever surface it sits\n  on.\n- `subtle` and `ghost` are re-verified (not renamed) for behavioral parity\n  with VT's `secondary` (border + hover-tint) and `clear` (text-only +\n  translucent hover) — note any intentional divergence found.\n- `size` gains icon-only handling: square dimensions per size step (VT's\n  `!px-0 w-8`/`w-10` pattern) instead of padded text sizing.\n- Every new/changed variant keeps the existing token-based focus ring,\n  disabled state, forwarded ref, and `className`-wins contract unchanged.\n\n## Acceptance criteria\n\n- [ ] `Button`'s `variant` union covers `neutral`, a `success`-backed variant,\n      and `blend`, each emitting the correct token utility classes (asserted\n      via rendered markup) and passing AA in both modes using only\n      already-landed tokens (`success`, `success-fg`, `accent-ring`,\n      `accent-text`, `danger-fg`).\n- [ ] Icon-only sizing is available and renders square dimensions matching\n      VT's icon-only pattern per size step.\n- [ ] `subtle`/`ghost` remain behaviorally equivalent to VT's\n      `secondary`/`clear`; any intentional divergence is called out in this\n      ticket's Comments.\n- [ ] All existing guarantees (forwarded ref, `type=\"button\"` default,\n      `className` wins, token focus ring, disabled state) still hold for\n      every variant, old and new.\n- [ ] Render-to-HTML tests (reusing the harness from ticket 01) cover every\n      variant × the icon-only path.\n- [ ] `preview/app.tsx`'s `VARIANTS`/button matrix is updated to include the\n      new variants, so the preview page stops under-representing the\n      component (the trigger for this ticket).\n\n## Out of scope\n\n- Polymorphic rendering (VT's Router Link / external-link button forms) —\n  needs a Slot-style primitive Kylä doesn't have yet; flagged in the parent\n  PRD's Out of Scope, not built here.\n- Renaming any existing variant to match VT's literal names — ADR-0005 keeps\n  Kylä's own vocabulary.\n\n## Blocked by\n\n- [01 — Render-to-HTML harness + Text / Heading](./01-render-harness-and-typography.md)\n  — provides the render-to-HTML harness this ticket's tests reuse.\n\nNot blocked by the scales/palette PRD's remaining tickets — `success`,\n`success-fg`, `danger-fg`, `accent-ring`, `accent-text` already landed in v152\n(see [structural-scales-palette issue 01](../../structural-scales-palette/issues/01-real-palette-and-contrast-harness.md)).\n",[],[217,465,466,465,468],"ddaf2fb0-9d6b-4ea3-b028-986ecbc8780f","03-form-field-primitives.md","7d8b7d22-7b2a-11f1-92f9-1607ee4eb77e",140,["D",1783555785020],"# 03 · Form field primitives — Label, Input, Textarea, Select\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: v1 zero-dependency component set](../PRD.md)\n\n## What to build\n\nShip the interactive form set with the ADR-0003 bounded-accessibility baseline, so\nconsumers get on-system fields with a visible token focus ring and correct label\nassociation without hand-wiring ARIA.\n\nEnd-to-end behavior:\n\n- `Label` associates with a field via `htmlFor` ↔ field `id`.\n- `Input` and `Textarea` share sizes matching `Button`, carry a token visible focus\n  ring (`tw.ring`/`tw.ringOffset`), and wire an `invalid` state to `aria-invalid`\n  and the `danger` token. `Input` forwards `type`.\n- `Select` is a styled-native `<select>` (sizes matching `Input`) that keeps native\n  keyboard behavior with zero added dependencies.\n- Each follows the `Button` authoring contract (`variants()`, semantic element,\n  `forwardRef` + rest props, `className` merged last via `cn()`) and is exported\n  from the `mod.ts` barrel.\n\n## Acceptance criteria\n\n- [ ] `Label`, `Input`, `Textarea`, `Select` render their correct semantic elements, forward refs/rest props, and are exported from `mod.ts`.\n- [ ] `Label htmlFor` matches an `Input id` (association asserted via rendered markup); `Input` forwards `type`.\n- [ ] Focus-ring classes are present on the interactive components; `disabled` and `aria-invalid` render, with `invalid` mapped to the `danger` token.\n- [ ] `className` wins over conflicting classes; render-to-HTML tests cover element + a11y wiring + token classes and pass under `deno test`.\n\n## Blocked by\n\n- [01 — Render-to-HTML harness + Text / Heading](./01-render-harness-and-typography.md) — provides the render-to-HTML harness and the `Button`-pattern reference.\n- [Real palette + first contrast test harness](../../structural-scales-palette/issues/01-real-palette-and-contrast-harness.md) — provides the `danger` / focus-ring tokens.\n- [Fixed spacing scale + graduated radius scale, with typed accessors](../../structural-scales-palette/issues/02-spacing-and-radius-scales.md) — provides the spacing tokens the field sizes map onto.\n",[],[217,465,466,465,477],"288d5744-e826-4c89-abe8-0b59c71dfa5e","02-layout-and-container-primitives.md","7da62bd6-7b2a-11f1-92f9-1607ee4eb77e",["D",1783578006344],"# 02 · Layout & container primitives — Stack, Box, Divider, Card, Badge\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: v1 zero-dependency component set](../PRD.md)\n\n## What to build\n\nShip the non-interactive visual set — layout primitives and containers — each\nauthored on the `Button` pattern and consuming the spacing-scale tokens so layout\nstays on-system by construction.\n\nEnd-to-end behavior:\n\n- **Layout:** `Stack` (typed `direction` row/column, `gap` from the spacing scale,\n  alignment), `Box` (minimal styled generic container, no required variants), and\n  `Divider` (orientation, uses the `hairline`/`line` token).\n- **Containers:** `Card` (typed `surface` = `elevated`/`recessed`, `padding` from\n  the spacing scale) and `Badge` (typed `tone` set, `size`).\n  Per the parent PRD's VT Parallelism Audit: VT's card has no elevated/recessed\n  *fill* — it's flat (`base`) + `border`, elevating only via\n  `hover:border-blue-400` + `hover:shadow-lg`. `Card`'s **default** `surface`\n  must render that flat/bordered look, not a raised fill; `elevated`/`recessed`\n  stay available as explicit, Kylä-only opt-ins.\n- Every component maps typed props → token classes via `variants()`, uses a\n  semantic element, forwards ref + rest props, merges `className` last via `cn()`,\n  and is exported from the `mod.ts` barrel.\n\n## Acceptance criteria\n\n- [ ] `Stack`, `Box`, `Divider`, `Card`, and `Badge` are exported from `mod.ts`, each forwarding refs/rest props.\n- [ ] `Stack` gap and `Card` padding consume spacing-scale tokens; `Divider` uses the hairline token; a bad variant value is a compile error.\n- [ ] `Card surface` and `Badge tone` emit the expected token utility classes (e.g. `Badge tone=\"danger\"` emits the danger color class), asserted via rendered markup.\n- [ ] `Card`'s default `surface` (no prop passed) renders the flat/bordered VT-parity look (`base` surface + border + hover border/shadow), not a raised `elevated` fill.\n- [ ] `className` wins over each component's conflicting class; render-to-HTML tests cover element + token classes and pass under `deno test`.\n\n## Blocked by\n\n- [01 — Render-to-HTML harness + Text / Heading](./01-render-harness-and-typography.md) — provides the render-to-HTML harness and the `Button`-pattern reference for the set.\n- [Fixed spacing scale + graduated radius scale, with typed accessors](../../structural-scales-palette/issues/02-spacing-and-radius-scales.md) — provides the spacing tokens `Stack`/`Card` consume.\n",[],[217,465,466,465,485],"c413abd1-0faa-4b45-8758-34d68039f76b","01-render-harness-and-typography.md","7d9843ae-7b2a-11f1-ad10-1607ee4eb77e",142,["D",1783555785097],"# 01 · Render-to-HTML harness + Text / Heading\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: v1 zero-dependency component set](../PRD.md)\n\n## What to build\n\nStand up the render-to-HTML test harness for the component set and ship the first\ntwo components — `Text` and `Heading` — authored exactly like `Button`. Consumers\nget typed typography whose sizes come from the type scale and whose tones come from\nthe palette; every later component slice reuses the harness this ticket establishes.\n\nEnd-to-end behavior:\n\n- `Text` and `Heading` with typed `size` (type-scale steps), `weight`, and `tone`\n  (`fg`/`fg-muted`/`accent`/`danger`) props, a polymorphic `as` for the element,\n  `forwardRef` + rest props, and an escape-hatch `className` merged last via `cn()`.\n  Both are exported from the `mod.ts` barrel.\n- A `renderToStaticMarkup` harness that renders a component to an HTML string for\n  assertions — the uniform seam for the whole set. If this slice lands before the\n  scales PRD's own tests, it establishes the render-to-HTML harness itself.\n\n## Acceptance criteria\n\n- [ ] `Text` and `Heading` render the correct semantic element (`Heading` emits the right heading tag; `Text` a sensible default), forward refs/rest props, and are exported from `mod.ts`.\n- [ ] `size`/`weight`/`tone` map to token utility classes drawn from the type scale and palette; a bad prop value is a compile error via typed unions.\n- [ ] `className` wins over the component's own conflicting class (the `cn()` contract), asserted against the rendered markup.\n- [ ] A reusable render-to-HTML harness exists; `Text`/`Heading` tests assert element + token classes + `className`-wins and pass under `deno test`.\n\n## Blocked by\n\n- [Real palette + first contrast test harness](../../structural-scales-palette/issues/01-real-palette-and-contrast-harness.md) — provides the palette tones and the `tw.*` color accessor pattern.\n- [Type scale (size + line-height) + overridable font, with loading](../../structural-scales-palette/issues/03-type-scale-and-font.md) — provides the type-scale steps `Text`/`Heading` map onto.\n",[],[217,465,466,465,492],"886b6498-1056-48f0-8993-5b2487d179a6",138,["D",1783555784691],[272,273,274,275],[217,465,466,465],"d85a6580-b615-42a1-b715-f4de6d7e3e91","452a7b3c-798a-11f1-97fb-1607ee4eb77e",82,["D",1783377020147],[271,276],[217,465,466],"ea09760d-bd6a-4dc8-a58d-1a9089a9068c","45dcb4a0-798a-11f1-9f6a-1607ee4eb77e","458c169e-798a-11f1-80ac-1607ee4eb77e",128,["D",1783381148674],4,"# PRD: Structural scales & real palette\n\nStatus: ready-for-agent Labels: ready-for-agent\n\n> The highest-leverage item on the [roadmap](../../roadmap.md): the spacing /\n> radius / type scale is where visual consistency actually lives. This PRD turns\n> the provisional token stylesheet into a real, fixed structural foundation. It\n> is the prerequisite for the [v1 component set](../v1-component-set/PRD.md).\n\n## Problem Statement\n\nKylä's whole promise is that apps look coherent by default. But today the token\nsystem only ships semantic **color** tokens with _provisional_ hex values, plus\na single `--kyla-radius`. There is no spacing scale, no type scale, and no\ngraduated radius scale, and the palette has never been checked for AA contrast.\n\nThe consequence is already visible: the preview page hand-writes `px-4 py-2`,\n`text-lg`, `gap-6`, `mt-5`, `text-[10px]` — raw Twind numbers chosen ad hoc.\nEvery component built this way re-decides spacing and type independently, which\nis exactly the inconsistency Kylä exists to eliminate. Consumers who trust the\ndefault theme also have no guarantee that foreground/background pairings are\nlegible.\n\n## Solution\n\nShip a real, opinionated, **fixed** set of structural scales — spacing, radius,\nand type (size + line-height, with the font family and any needed weights) —\nplus a real, AA-verified color palette bound to the existing semantic tokens.\nBecause the structural scales are fixed and consumed by every component, spacing\nand type become consistent by construction. The consumer override surface stays\ndeliberately small (`--kyla-accent`, `--kyla-radius`, `--kyla-font`); everything\nstructural stays fixed — that fixedness _is_ the consistency (ADR-0001,\nCONTEXT.md).\n\nThe default palette carries AA contrast as a quiet guarantee (ADR-0003),\nverified mechanically rather than by eye.\n\n## User Stories\n\n1. As a consumer, I want a fixed spacing scale exposed as tokens, so that\n   padding and gaps are consistent across every component and every app without\n   me choosing pixel values.\n2. As a consumer, I want a fixed type scale (size + line-height), so that text\n   hierarchy is coherent without me hand-picking `text-*` classes.\n3. As a consumer, I want a font-family token I can override, so that I can\n   express brand while keeping the rest of the system fixed.\n4. As a consumer, I want a graduated radius scale derived from the overridable\n   `--kyla-radius`, so that rounding stays proportional when I change the base\n   radius.\n5. As a consumer, I want the default palette to meet WCAG AA contrast in both\n   light and dark mode, so that my app is legible without me auditing colors.\n6. As a consumer, I want the small override surface (accent, radius, font) to be\n   documented and stable, so that I know exactly what I may safely redefine.\n7. As a consumer, I want structural tokens (spacing, type, surfaces, borders) to\n   stay fixed, so that I cannot accidentally break visual consistency by\n   overriding them.\n8. As a component author, I want a sanctioned, typed way to reference scale\n   tokens, so that I compose spacing and type from the scale instead of raw\n   Twind numbers.\n9. As a component author, I want the scale accessors to sit alongside the\n   existing `tw` color helpers, so that authoring one component uses one\n   consistent vocabulary.\n10. As a component author, I want the type scale to bundle line-height with\n    size, so that I cannot set a size without its intended leading.\n11. As a maintainer, I want the palette's AA guarantee enforced by a test, so\n    that a future palette edit that breaks contrast fails CI rather than\n    shipping.\n12. As a maintainer, I want the scale definitions to live in one place\n    (`tokens.ts`), so that the design foundation has a single source of truth.\n13. As a maintainer, I want the scales expressed as CSS custom properties\n    resolved with `light-dark()` where mode-dependent, so that mode still flips\n    with zero JS.\n14. As an end user, I want legible text and comfortable spacing in whatever mode\n    my OS prefers, so that the app is usable by default.\n15. As a consumer upgrading, I want the scale token _names_ to be stable, so\n    that a Release that retunes values doesn't break my component usage.\n\n## Implementation Decisions\n\n- **Source of values (ADR-0005):** the palette and structural scales **conform\n  to the Val Town UI style guide** — they are _ported_, not invented here.\n  Concrete values come from the VT style-guide research/reference doc under\n  `docs/` (see\n  [ADR-0005](../../adr/0005-val-town-visual-language-default-theme.md)). This\n  PRD's job is to bind those values to the `--kyla-*` tokens and the scale\n  accessors, and to hold the AA line where a VT pairing falls short.\n- **Resolved default values** (from\n  [`val-town-style-guide.md`](../../reference/val-town-style-guide.md) §6; all\n  AA-passing both modes). Values are Tailwind v4 steps, applied via\n  `light-dark(light, dark)`:\n  - `base` = white / **`slate-950` `#020618`** (a deliberate softening of VT's\n    true-black `#000` — see ADR-0005); `elevated` = white+shadow / `slate-900`;\n    `recessed` = `slate-100` / `slate-800`.\n  - `fg` = black / white; `fg-muted` = `gray-600` / `gray-300` (VT's literal\n    `--color-muted`; **not** slate-400, which fails AA).\n  - `line` = `slate-200` / `slate-700`; `hairline` = `slate-100` / `slate-800`.\n  - `accent` = `sky-400` / `sky-700`; `accent-fg` = **`sky-950` ink** / white\n    (never white on `sky-400` — fails at 2.18:1); `accent-ring` = `sky-500`;\n    `accent-text` = `sky-800` / `sky-200`.\n  - `danger` = `rose-300` / `rose-800`; `danger-fg` = `rose-950` / white.\n    `success` = `emerald-400` / `emerald-700`; `success-fg` = `emerald-950` /\n    white.\n  - `radius` (base) = **8px** (`rounded-lg`); spacing base = 4px; font =\n    `\"IBM Plex Sans\",\n-apple-system, sans-serif` (needs shell/Provider font\n    loading — flag for delivery).\n- **New tokens (ADR-0005):** this PRD adds `accent-ring`, `accent-text`,\n  `danger-fg`, `success`, `success-fg` to the `ColorToken` union and the token\n  stylesheet, alongside the existing set. All are structural (not part of the\n  override surface).\n- **Modules touched:** `src/theme/tokens.ts` (add scale custom properties) and\n  `src/theme/tw.ts` (add typed scale accessors alongside the existing color\n  helpers). A new pure module for the AA-contrast check (used by tests) may be\n  added under `src/theme/`.\n- **Scale tokens to define** (names fixed by this PRD; exact numeric values are\n  the design deliverable _within_ this PRD):\n  - **Spacing:** a fixed stepped scale, `--kyla-space-*`. Monotonic, small step\n    count, built on a consistent base unit.\n  - **Type:** `--kyla-text-*` steps, each carrying a size **and** a line-height,\n    plus `--kyla-font` (overridable) and weight tokens if components need them.\n  - **Radius:** keep `--kyla-radius` as the single overridable base; derive a\n    small graduated set (`--kyla-radius-sm/md/lg`) from it.\n- **Override surface (formalized):** consumer-overridable = `--kyla-accent`,\n  `--kyla-radius`, `--kyla-font` (and their direct derivations). Everything else\n  — surfaces, foreground, borders, spacing scale, type scale — is structural and\n  stays fixed. Document this split in `tokens.ts` and CONTEXT.md's Override\n  Surface note.\n- **Accessor shape:** scale accessors follow the `tw.*` pattern. Lengths need no\n  `color:` hint (per the spike finding, only colors do), so spacing/radius/type\n  accessors emit bare arbitrary-value classes (e.g. `p-[var(--kyla-space-4)]`),\n  while a typo in the step is a compile error via a TypeScript union — mirroring\n  how `ColorToken` already guards color tokens.\n- **Palette:** replace every provisional hex with the resolved VT value above\n  for both modes, keeping the `light-dark()` structure. Every _sanctioned_\n  foreground/ surface pairing (`fg` on `base`/`elevated`/`recessed`, `accent-fg`\n  on `accent`, `danger-fg` on `danger`, `success-fg` on `success`, `fg-muted` on\n  surfaces used for secondary text) must meet WCAG AA: 4.5:1 for body text, 3:1\n  for large text and UI/border affordances.\n\n## Testing Decisions\n\n- **What makes a good test here:** it asserts an _external guarantee_ of the\n  foundation, not a specific hex or pixel. Two guarantees are worth testing:\n  contrast and scale integrity.\n- **Seam (highest available):** the token stylesheet string plus a **pure\n  contrast function** over resolved color values. This is the natural seam\n  because the guarantee (\"AA holds\") is a property of the values, computable\n  without a browser.\n  - Enumerate every sanctioned fg/surface pairing and assert its computed\n    contrast ratio meets the AA threshold in **both** modes. This is the load-\n    bearing test — it's what lets a future palette edit fail loudly.\n  - Assert the spacing and type scales exist, are monotonic, and expose the\n    documented step count.\n  - Assert the override tokens (`--kyla-accent`, `--kyla-radius`, `--kyla-font`)\n    are present and that structural tokens are present.\n- **Modules tested:** `tokens.ts` (via the parsed stylesheet) and the contrast\n  helper.\n- **Prior art:** none — this PRD establishes the repo's first test harness. Keep\n  it a plain Deno test so later component PRDs can reuse the pattern.\n\n## Out of Scope\n\n- The Kumo-style **named-theme system** / multiple consumer-defined themes\n  (theming v2 — deferred by the sketch).\n- Per-component **variant → token maps** (which tones `Badge`/`Button` expose,\n  etc.) — that lives with the\n  [v1 component set PRD](../v1-component-set/PRD.md).\n- Any new components.\n- Dark-mode raster image handling.\n\n## Further Notes\n\n- This PRD front-loads a genuine design decision (the actual step counts,\n  ratios, and hex values). Those choices should be made here and encoded as the\n  token values; downstream PRDs consume them by name and must not re-decide\n  them.\n- Because scale token _names_ become load-bearing across the component set,\n  treat a rename as a breaking change under ADR-0004 once components depend on\n  them.",[],[217,465,519,458],"structural-scales-palette","7b2fe524-4925-4a4e-a498-12954c8d8c36","04-formalize-override-surface.md","7fc3a646-7990-11f1-890b-1607ee4eb77e","6838d48e-7b24-11f1-bbaa-1607ee4eb77e",135,["D",1783553172491],"# Formalize the override surface + structural-token presence test\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Structural scales & real palette](../PRD.md)\n\n## What to build\n\nSeal the foundation: make the override/structural split explicit and enforced now\nthat every token family (palette, spacing, radius, type/font) exists.\n\nEnd-to-end behavior:\n\n- **Documentation:** record the split in `tokens.ts` and in CONTEXT.md's Override\n  Surface note. Consumer-overridable = `--kyla-accent`, `--kyla-radius`,\n  `--kyla-font` (and their direct derivations); everything else — surfaces,\n  foreground, borders, spacing scale, type scale — is structural and stays fixed.\n  That fixedness is the consistency (ADR-0001, CONTEXT.md).\n- **Presence test** (reusing the harness from slice 01): assert the three override\n  tokens are present, and that the structural tokens across all families are\n  present. This encodes the stable-names contract — scale token *names* are\n  load-bearing across the component set, so a rename becomes a detectable breaking\n  change under ADR-0004.\n\nThis slice adds no new values or accessors; it documents and locks the surface the\nprior three slices produced.\n\n## Acceptance criteria\n\n- [ ] `tokens.ts` and CONTEXT.md's Override Surface note both state the override vs. structural split, listing `--kyla-accent`, `--kyla-radius`, `--kyla-font` as the overridable surface.\n- [ ] A test asserts the three override tokens are present and that the structural tokens across surfaces, foreground, borders, spacing, radius, and type are all present.\n- [ ] The presence test fails if a documented token name is removed or renamed, giving the stable-names contract teeth — passing under `deno test`.\n\n## Blocked by\n\n- [02 — Fixed spacing scale + graduated radius scale](./02-spacing-and-radius-scales.md)\n- [03 — Type scale + overridable font](./03-type-scale-and-font.md)\n\n(Depends on every token family existing so the presence test can assert the full set. Slice 01 is a transitive blocker.)\n",[],[217,465,519,465,521],"a35270a3-c79a-4b78-a9d7-a22a32ba6280","03-type-scale-and-font.md","42ee8d08-7990-11f1-824a-1607ee4eb77e",133,["D",1783553172437],"# Type scale (size + line-height) + overridable font, with loading\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Structural scales & real palette](../PRD.md)\n\n## What to build\n\nShip the fixed type scale and the overridable font, end-to-end — tokens, typed\naccessor, and the font actually loading in the running app.\n\nEnd-to-end behavior:\n\n- **Type scale:** `--kyla-text-*` steps, each carrying **both** a size and its\n  paired line-height, defined in the token stylesheet. Structural and fixed. Weight\n  tokens are added if components need them.\n- **Font:** `--kyla-font` is the overridable font-family token (default\n  `\"IBM Plex Sans\", -apple-system, sans-serif`), part of the small consumer override\n  surface. The IBM Plex Sans webfont is actually loaded via the shell/Provider so\n  the default renders as intended — this is the delivery concern the PRD flags;\n  without it the token points at a font that never arrives.\n- **Accessor:** a typed type accessor alongside the `tw.*` helpers that bundles\n  line-height with size, so an author cannot set a size without its intended leading.\n  A typo'd step is a compile error via a TypeScript union.\n- **Tests** (reusing the harness from slice 01): assert the type steps exist, are\n  monotonic by size, and that each step carries a line-height; assert `--kyla-font`\n  is present.\n\nExact steps and values come from the PRD Implementation Decisions and\n`docs/reference/val-town-style-guide.md` §4 (size/line-height pairs; weights\n400/500/600/700/800; body `text-base` 16/1.5, controls `text-sm` 14/20).\n\n## Acceptance criteria\n\n- [ ] `--kyla-text-*` steps each pair a size with a line-height in the token stylesheet; the scale is fixed/structural and monotonic by size.\n- [ ] The typed type accessor bundles size + line-height so a size cannot be set without its leading; a bad step name is a compile error.\n- [ ] `--kyla-font` is an overridable token defaulting to the IBM Plex Sans stack, and the webfont is loaded via the shell/Provider so the default actually renders.\n- [ ] Weight tokens are exposed if components need them.\n- [ ] Tests assert the type steps exist, are monotonic, each carries a line-height, and `--kyla-font` is present — passing under `deno test`.\n\n## Blocked by\n\n- [01 — Real palette + first contrast test harness](./01-real-palette-and-contrast-harness.md) (provides the test harness and the `tw.*` accessor pattern).\n",[],[217,465,519,465,530],"354b5837-b9bc-405f-8a83-caa0d765ee97","02-spacing-and-radius-scales.md","7fbc5fe4-7990-11f1-8901-1607ee4eb77e",132,["D",1783553172423],"# Fixed spacing scale + graduated radius scale, with typed accessors\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Structural scales & real palette](../PRD.md)\n\n## What to build\n\nShip the two fixed length scales — spacing and radius — as tokens plus sanctioned,\ntyped accessors, so component authors compose them from the scale instead of raw\nTwind numbers.\n\nEnd-to-end behavior:\n\n- **Spacing:** a fixed, monotonic, stepped `--kyla-space-*` scale with a small step\n  count on a consistent 4px base unit, defined in the token stylesheet. These are\n  structural (not overridable).\n- **Radius:** keep `--kyla-radius` as the single consumer-overridable base, and\n  derive a small graduated set (`--kyla-radius-sm/md/lg`) from it so rounding stays\n  proportional when a consumer changes the base radius.\n- **Accessors:** add typed scale accessors alongside the existing `tw.*` color\n  helpers. Lengths need no `color:` hint, so these emit bare arbitrary-value classes\n  (e.g. `p-[var(--kyla-space-4)]`, `rounded-[var(--kyla-radius-md)]`). A typo'd step\n  is a compile error via a TypeScript union, mirroring how `ColorToken` guards color\n  tokens. The existing single `tw.radius` accessor is superseded by the graduated\n  form.\n- **Tests** (reusing the harness from slice 01): assert the spacing and radius\n  tokens exist, are monotonic, expose the documented step count, and that the\n  graduated radii derive from the overridable base.\n\nExact step counts and numeric values come from the PRD Implementation Decisions and\n`docs/reference/val-town-style-guide.md` §2–§3 (spacing base 4px; radius scale\n2/4/6/8/12/16/24, control default 8px).\n\n## Acceptance criteria\n\n- [ ] `--kyla-space-*` is a fixed, monotonic stepped scale on a 4px base with the documented step count, defined in the token stylesheet.\n- [ ] `--kyla-radius` remains the single overridable base; `--kyla-radius-sm/md/lg` are derived from it and stay proportional when the base changes.\n- [ ] Typed spacing and radius accessors sit alongside the `tw.*` color helpers, emit bare arbitrary-value classes (no `color:` hint), and make a bad step name a compile error.\n- [ ] Tests assert both scales exist, are monotonic, expose the documented step count, and that graduated radii derive from the base — passing under `deno test`.\n\n## Blocked by\n\n- [01 — Real palette + first contrast test harness](./01-real-palette-and-contrast-harness.md) (provides the test harness and the expanded `tw.*` accessor pattern).\n",[],[217,465,519,465,538],"cb20067a-70c5-4b83-8bcc-bf699967d298","01-real-palette-and-contrast-harness.md","430d5030-7990-11f1-8131-1607ee4eb77e",153,["D",1783562311193],"# Real palette + first contrast test harness\n\nStatus: done\nLabels: done\nLanded: v152\n\n## Parent\n\n[PRD: Structural scales & real palette](../PRD.md)\n\n## What to build\n\nReplace the provisional token palette with the real, AA-verified Val Town values,\nand stand up the repo's first test harness by proving that palette meets AA\ncontrast. This is the foundational slice every later scale slice builds on.\n\nEnd-to-end behavior:\n\n- The token stylesheet resolves every semantic color token to its real VT value\n  in **both** modes via `light-dark()` (mode still flips with zero JS). Provisional\n  hexes are gone; the values conform to the VT style guide (ADR-0005), with the one\n  sanctioned deviation (dark-mode `base` = `slate-950` `#020618`, not true black).\n- The color-token vocabulary expands to cover VT's accent + status roles: the new\n  structural tokens `accent-ring`, `accent-text`, `danger-fg`, `success`,\n  `success-fg` join the existing set, in both the stylesheet and the typed\n  `ColorToken` union so `tw.*` color helpers can reference them.\n- A pure, browser-free contrast function computes the WCAG contrast ratio between\n  two resolved color values. It is the natural seam for the guarantee (\"AA holds\"),\n  computable without a DOM.\n- The repo's first Deno test parses the token stylesheet, enumerates every\n  _sanctioned_ foreground/surface pairing, and asserts each meets its AA threshold\n  in **both** modes. This is the load-bearing test — a future palette edit that\n  breaks contrast fails CI rather than shipping.\n\nResolved values and the full sanctioned-pairing list come from the PRD's\nImplementation Decisions and `docs/reference/val-town-style-guide.md` §6–§7 — bind\nthose values, do not re-decide them. Keep the harness a plain Deno test so later\nscale slices reuse the pattern.\n\n## Acceptance criteria\n\n- [x] Every semantic color token resolves to its real VT value in both modes via `light-dark()`; no provisional hexes remain, and no `dark:` variants are introduced.\n- [x] Dark-mode `base` uses the sanctioned `slate-950` softening, not true black.\n- [x] `accent-ring`, `accent-text`, `danger-fg`, `success`, `success-fg` are added to both the stylesheet and the `ColorToken` union; existing `tw.*` color helpers reach them.\n- [x] A pure contrast function returns the correct WCAG ratio for known pairs and takes no DOM/browser dependency.\n- [x] A Deno test enumerates every sanctioned fg/surface pairing and asserts AA (4.5:1 body, 3:1 large/UI) in both light and dark; it fails if any pairing regresses.\n- [x] The test suite runs with `deno test` and passes (needs `--allow-import` for the val.town types pulled by `deno.json`).\n\n## Blocked by\n\nNone - can start immediately.\n",[],[217,465,519,465,546],"e748642e-e7f7-414d-8b14-e85ecb9f1fe4",131,["D",1783553172262],[265,266,267,268],[217,465,519,465],"2c4f93b5-35b4-46eb-9524-1075f5cb6327",84,["D",1783377020429],[264,269],[217,465,519],"423e3792-fbbb-4398-8f4c-7b4ee4b23ea0","45edca42-798a-11f1-afe8-1607ee4eb77e","457d5078-798a-11f1-80ac-1607ee4eb77e",92,["D",1783377020896],"# PRD: Starter — remixable todo app\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n> Ships the **Starter** defined in [CONTEXT.md](../../../CONTEXT.md): a separate,\n> remixable demo val showing idiomatic end-to-end use of Kylä UI. It depends on\n> the [component set](../v1-component-set/PRD.md) (and ideally\n> [Dialog](../dialog-radix/PRD.md)); the Starter depends on the library, never the\n> reverse.\n\n## Problem Statement\n\nCONTEXT.md's on-ramp for a new app is \"remix the Starter, then edit.\" But the\nStarter doesn't exist. A developer who wants to build with Kylä has only the\nGallery (which shows components in isolation) and the README snippet (a single\nButton). There's no genuine, end-to-end example wiring together a real HTTP route,\npersistence, the Provider + client hydration, an app shell, and a Mode toggle —\ni.e. no honest demonstration that Kylä works as a whole for building an actual app.\n\n## Solution\n\nShip **`kyla-ui-starter`**: a small but genuine **todo app** that imports Kylä UI\nand is built entirely from its components. It has a real HTTP route, `std/sqlite`\npersistence, `KylaProvider` + client hydration, an app shell, a Mode toggle, and a\nview-source link. Remixing it and editing is the intended way to start a new Kylä\napp. Building it also dogfoods the library and surfaces gaps in the component set.\n\n## User Stories\n\n1. As a new Kylä developer, I want a remixable Starter val, so that I can begin a real app by copying a working example instead of assembling one.\n2. As a new developer, I want the Starter to be a genuine todo app (add / toggle / delete, persisted), so that it demonstrates real behavior, not a static mock.\n3. As a new developer, I want the Starter to persist todos with `std/sqlite`, so that I see the idiomatic Val Town persistence pattern.\n4. As a new developer, I want the Starter to serve a real HTTP route, so that I see how a Kylä app is served on Val Town.\n5. As a new developer, I want the Starter wrapped in `KylaProvider` with client hydration, so that I see the correct Provider + CSR wiring (Twind before first paint, tokens injected, Mode owned).\n6. As a new developer, I want the whole UI built from Kylä components, so that I learn the components by seeing them composed in a real app.\n7. As a new developer, I want a Mode toggle in the Starter, so that I see how to give an app a first-class light/dark toggle via `useKylaMode()`.\n8. As a new developer, I want a view-source link, so that I can jump from the running app to its code.\n9. As a new developer, I want the Starter pinned to a known-good Kylä Release, so that a fresh remix renders correctly and isn't broken by an in-flight library change.\n10. As a maintainer, I want the Starter to depend on the library (never the reverse), so that the dependency direction stays clean.\n11. As a maintainer, I want the Starter built from real components, so that it doubles as an integration check that the set composes into an app.\n12. As an end user of the demo, I want to add, complete, and remove todos, so that the app is actually usable.\n13. As an end user, I want my todos to persist across reloads, so that the demo behaves like a real app.\n\n## Implementation Decisions\n\n- **Separate val:** `kyla-ui-starter` (per CONTEXT.md), distinct from `kyla-ui`.\n  It **imports** Kylä UI; the library never imports it.\n- **CSR-only** (sketch/ADR-0001): an HTML shell loads Twind before first paint,\n  a client entry hydrates the app, and `KylaProvider` wraps it (owning tokens +\n  Mode). Same shell mechanics the Gallery/preview use (importmap for `npm:`\n  specifiers, `std/catch`, `serveFile`).\n- **Persistence:** `std/sqlite` (project-scoped DB) for the todo list.\n- **HTTP route:** serves the shell and handles todo mutations — list, add, toggle\n  complete, delete — round-tripping through sqlite.\n- **UI built from Kylä components:** app shell, `Card`, `Input`, `Button`,\n  `Text`/`Heading`, `Stack`, etc., plus the Mode toggle via `useKylaMode()`. Using\n  `Dialog` (e.g. a confirm-delete) is encouraged once it ships, to demonstrate the\n  own-import-path pattern.\n- **Version pinning (decided here):** the Starter **pins** its Kylä import to a\n  known-good `?v=NNN` Release, so a remix is a stable starting point rather than\n  tracking `main` mid-change (ADR-0004). Document which Release it targets; bump\n  deliberately.\n- **view-source link** to the Starter val, matching the preview/Gallery pattern.\n\n## Testing Decisions\n\n- **What makes a good test:** it drives the app's *external* HTTP behavior — the\n  todo operations round-tripping through sqlite — not the internal React tree or\n  the library's internals (those are the component PRDs' concern).\n- **Seam (HTTP, highest available for the app):** exercise the route endpoints and\n  assert the todo lifecycle: adding a todo returns/lists it, toggling flips its\n  completed state, deleting removes it, and the list reflects persisted state on a\n  fresh request. Optionally assert the served shell is a `200` HTML page that\n  boots the client entry.\n- **Modules tested:** the Starter's HTTP handler + its sqlite data access.\n- **Prior art:** Val Town `std/sqlite` HTTP-handler patterns (fetch a template via\n  the platform's skill finder); the `preview/index.tsx` handler is the reference\n  for the serve-shell-and-files structure on Val Town.\n\n## Out of Scope\n\n- Auth / multi-user / per-user todo lists.\n- Isomorphic SSR + hydration for SEO (sketch defers this; CSR-only for v1).\n- Demonstrations beyond the todo app (other example apps).\n- The **Gallery** / component docs — those live in the library\n  ([Gallery PRD](../gallery/PRD.md)), not the Starter.\n\n## Further Notes\n\n- The Starter is the honest integration test of the whole v1: if composing it into\n  a real app is awkward, that's a signal to fix the component set, not to work\n  around it in the Starter.\n- Keep it \"tiny but genuine\" — enough to be a real app, small enough to read in one\n  sitting, since developers will copy it as their baseline.\n",[],[217,465,571,458],"starter","e39dd761-bbc8-43f6-bb86-b0e5105b5366","03-todo-ui-and-mode-toggle.md","7db91958-7b2a-11f1-ac5e-1607ee4eb77e","7d76a5a0-7b2a-11f1-92f9-1607ee4eb77e",146,["D",1783555785317],"# 03 · Todo UI + Mode toggle\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Starter — remixable todo app](../PRD.md)\n\n## What to build\n\nWire the todo UI — built entirely from Kylä components — to the CRUD route, and\ngive the app a first-class light/dark toggle via the library's own Mode ownership.\nThis is where the Starter becomes usable and dogfoods the component set as a whole.\n\nEnd-to-end behavior:\n\n- The full add / toggle / delete todo UI composed from Kylä components (`Card`,\n  `Input`, `Button`, `Text`/`Heading`, `Stack`, etc.), wired to the CRUD route.\n- A Mode toggle driven by `useKylaMode()` (not a hand-rolled toggle).\n- Optional: a confirm-delete `Dialog` once it ships, to demonstrate the\n  own-import-path pattern (soft dependency — not required to land this ticket).\n\n## Acceptance criteria\n\n- [ ] An end user can add, complete, and remove todos through a UI built entirely from Kylä components.\n- [ ] A Mode toggle driven by `useKylaMode()` flips the app between light/dark.\n- [ ] The UI reflects persisted state from the CRUD route (reload shows saved todos).\n\n## Blocked by\n\n- [01 — Served, hydrated skeleton app](./01-served-hydrated-skeleton.md)\n- [02 — Todo persistence + CRUD over HTTP](./02-todo-persistence-and-crud.md)\n\nSoft dependency (not blocking): [Dialog](../../dialog-radix/issues/01-dialog-radix-component.md) enables the optional confirm-delete example.\n",[],[217,465,571,465,573],"2f2bdce0-e24e-4f54-be72-581b5dcdd67e","02-todo-persistence-and-crud.md","7db4562a-7b2a-11f1-ae17-1607ee4eb77e",145,["D",1783555785189],"# 02 · Todo persistence + CRUD over HTTP\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Starter — remixable todo app](../PRD.md)\n\n## What to build\n\nGive the Starter a real, persisted todo lifecycle behind its HTTP route, so the\ndemo behaves like an actual app and doubles as the honest integration check the PRD\ncalls for.\n\nEnd-to-end behavior:\n\n- `std/sqlite` (project-scoped DB) data access for the todo list.\n- Route handlers that list, add, toggle-complete, and delete todos, each\n  round-tripping through sqlite. The list reflects persisted state on a fresh\n  request.\n- HTTP-seam tests that drive the route's **external** behavior — not the React tree\n  or the library internals.\n\n## Acceptance criteria\n\n- [ ] The route persists todos via `std/sqlite`; adding a todo lists it, toggling flips its completed state, and deleting removes it.\n- [ ] The list reflects persisted state on a fresh request (survives reload).\n- [ ] HTTP-seam tests assert the full add/toggle/delete/list lifecycle and pass under `deno test`.\n\n## Blocked by\n\n- [01 — Served, hydrated skeleton app](./01-served-hydrated-skeleton.md) — provides the served val + HTTP route this builds on.\n",[],[217,465,571,465,582],"5f5faa37-d177-4dfe-a88a-edc3548b7c02","01-served-hydrated-skeleton.md","7dd458da-7b2a-11f1-ad10-1607ee4eb77e",148,["D",1783555785304],"# 01 · Served, hydrated skeleton app\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Starter — remixable todo app](../PRD.md)\n\n## What to build\n\nStand up the `kyla-ui-starter` val as a served, hydrated skeleton that proves the\nwhole render/hydration path end-to-end before any todo logic exists. This is the\ntracer bullet: a fresh remix boots correctly against a pinned Kylä release.\n\nEnd-to-end behavior:\n\n- A separate val, `kyla-ui-starter`, that **imports** Kylä UI (the library never\n  imports it).\n- CSR-only shell (ADR-0001): an `index.html` static file loads Twind before first\n  paint, a client entry hydrates the app, and `KylaProvider` wraps it (owning\n  tokens + Mode). Same shell mechanics the Gallery/preview use (importmap for\n  `npm:` specifiers, `std/catch`, `serveFile`).\n- A minimal screen built from Kylä components, served at the app's HTTP route,\n  with a view-source link back to the val.\n- The Kylä import is **pinned** to a known-good `?v=NNN` Release (ADR-0004);\n  document which Release it targets.\n\n## Acceptance criteria\n\n- [ ] `kyla-ui-starter` is a separate val that imports Kylä UI and is served at an HTTP route returning a `200` HTML page that boots the client entry.\n- [ ] Twind loads before first paint; `KylaProvider` wraps the hydrated app and owns tokens + Mode; the visible screen is built from Kylä components.\n- [ ] A view-source link points back to the Starter val.\n- [ ] The Kylä import is pinned to a documented known-good `?v=` Release.\n\n## Blocked by\n\n- [v1-component-set 01 — Render-to-HTML harness + Text / Heading](../../v1-component-set/issues/01-render-harness-and-typography.md)\n- [v1-component-set 02 — Layout & container primitives](../../v1-component-set/issues/02-layout-and-container-primitives.md)\n- [v1-component-set 03 — Form field primitives](../../v1-component-set/issues/03-form-field-primitives.md)\n",[],[217,465,571,465,590],"91201a67-fc1c-40a8-a94a-41a8164c29a7",139,["D",1783555784870],[259,260,261],[217,465,571,465],"70836efb-efb6-44dd-98b2-39a9303b508b",83,["D",1783377020339],[258,262],[217,465,571],"20643885-194e-499d-afcb-56081079d9aa","45e698c6-798a-11f1-95f7-1607ee4eb77e","454cee9c-798a-11f1-97fb-1607ee4eb77e",91,["D",1783377020808],"# PRD: Gallery — self-hosted docs surface\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n> Promotes the WIP `preview/` into the real **Gallery** — a first-class term in\n> [CONTEXT.md](../../../CONTEXT.md): the library's self-hosted documentation at\n> its own HTTP route, rendering every component in its variants and Modes with the\n> Mode toggle. Grows as the [component set](../v1-component-set/PRD.md) and\n> [Dialog](../dialog-radix/PRD.md) land.\n\n## Problem Statement\n\nKylä is meant to **document itself**: CONTEXT.md defines the Gallery as an HTTP\nroute on `kyla-ui` that renders every component in its variants and Modes — both\nliving docs and the in-browser proof that the whole stack (Twind + CSS-var tokens,\nProvider mode, Radix hydration) renders correctly on Val Town. Today that surface\nonly exists as `preview/`, which is explicitly labelled work-in-progress and \"not\na stable API,\" carries a 🚧 banner, and is framed as illustrative rather than\ncanonical. There is no blessed docs surface a consumer can point to.\n\n## Solution\n\nPromote `preview/` into the real **Gallery** served at `kyla-ui`'s HTTP route: it\nrenders every shipped component across its variants/sizes/tones, shows the design\ntoken swatches, and carries the Mode toggle driven by the library's own\n`useKylaMode()`. It imports the real library and never modifies it. It is the\ncanonical proof-of-render on Val Town and the seed of a fuller docs site later.\n\n## User Stories\n\n1. As a consumer evaluating Kylä, I want a live Gallery at the library's URL, so that I can see every component before importing it.\n2. As a consumer, I want each component shown in all its variants/sizes/tones, so that I can pick the right props by seeing them.\n3. As a consumer, I want a Mode toggle (light/dark/system) in the Gallery, so that I can verify how components look in each Mode.\n4. As a consumer, I want the token swatches shown, so that I can see the semantic palette the system is built on.\n5. As a consumer, I want a view-source link, so that I can read how the Gallery uses the components.\n6. As a maintainer, I want the Gallery served from `kyla-ui` itself (co-located with source), so that the library documents itself and the docs can never drift from the code they import.\n7. As a maintainer, I want the Gallery to import the real library and never modify it, so that it's an honest proof-of-render, not a mock.\n8. As a maintainer, I want the Gallery to be the in-browser proof that Twind + tokens + Provider + Radix render correctly on Val Town, so that a broken render path is visible immediately.\n9. As a maintainer, I want adding a new component to the Gallery to be a small, obvious edit, so that the docs stay current as the set grows.\n10. As a contributor, I want the Gallery to exercise the interactive components (focus rings, Dialog open/close), so that it doubles as a manual behavior check.\n11. As an end user of the docs, I want the Gallery to load without a build step, so that it works on Val Town's runtime like any consumer app.\n\n## Implementation Decisions\n\n- **Home:** served from `kyla-ui`'s HTTP route (the val documents itself). Reuse\n  the shell *mechanics* from `preview/`: Twind loaded before first paint\n  (ADR-0001), the importmap that maps `npm:` specifiers to esm.sh for the browser,\n  `std/catch` for client-error surfacing, `serveFile` for transpiled `.ts/.tsx`,\n  and the `/source` redirect. The Gallery **imports** the library from `mod.ts`\n  (and Dialog's own path) and modifies nothing — the preview's core invariant.\n- **Shell conventions (folded-in cleanup — see issue\n  [`01-preview-shell-conventions`](issues/01-preview-shell-conventions.md)):** the\n  Gallery adopts the *corrected* shell, not today's template-literal one — a real\n  `index.html` static file served via `serveFile`, and no inline `<style>` block\n  (Twind utility classes only, per project convention). This cleanup is small and\n  can land early against `preview/` before the full Gallery is built; the Gallery\n  then inherits it.\n- **Content:** one section per shipped component showing its full variant/size/\n  tone matrix, plus the token swatches and the interactive examples. The Mode\n  toggle is driven by `useKylaMode()` (not a hand-rolled toggle) — dogfooding the\n  Provider's Mode ownership.\n- **Generation approach (open question in the sketch — decided here):**\n  **hand-written** sections per component for v1. A metadata-driven generator (the\n  sketch's alternative) is deferred until the component set stabilizes; hand-\n  written is lower-risk and needs no new metadata layer.\n- **Relationship to `preview/`:** this supersedes `preview/` as the canonical\n  surface. The WIP banner and \"not a stable API\" framing are dropped once it's the\n  blessed Gallery; the corrected shell (above) is kept.\n- **Dialog:** once [Dialog](../dialog-radix/PRD.md) ships, the Gallery is where its\n  open/close/focus-trap behavior is manually verifiable in-browser (the behavior\n  backstop that PRD refers to).\n\n## Testing Decisions\n\n- **What makes a good test:** it asserts the Gallery's *external* HTTP behavior —\n  that the route serves, and that the served markup contains the expected proof —\n  not the internal React tree.\n- **Seam (HTTP, highest available for a served surface):** fetch the Gallery\n  route and assert:\n   - a `200` with an HTML content-type;\n   - each shipped component's section is present;\n   - token utility classes (e.g. `bg-[color:var(--kyla-…)]`) appear in the served\n     markup — a direct check that the render path emits the hinted classes rather\n     than silently dropping them.\n- **Behavior (browser, optional backstop):** the Mode toggle flipping the palette\n  and Dialog interactions are the higher-fidelity checks; run them in a real\n  browser against the live Gallery. Not required for the PRD's automated seam.\n- **Modules tested:** the Gallery's HTTP handler.\n- **Prior art:** the existing `preview/index.tsx` handler (shell + `serveFile` +\n  `/source`) is the working reference for serving on Val Town.\n\n## Out of Scope\n\n- **Metadata-driven Gallery generation** (deferred; hand-written for v1).\n- A fuller prose/MDX docs site (the Gallery is its seed, not its replacement).\n- The **Starter** val — [separate PRD](../starter/PRD.md).\n- Building the components themselves — [component set PRD](../v1-component-set/PRD.md).\n\n## Further Notes\n\n- The Gallery is load-bearing beyond docs: because the Twind \"missing `color:`\n  hint\" failure is *invisible*, the Gallery is the fastest place a human spots an\n  unstyled element. Keep it exercising real components in real Modes.\n",[],[217,465,615,458],"gallery","5fb4ace1-a217-47c6-be51-ed0da77893a5","03-gallery-dialog-backstop.md","7dc6339a-7b2a-11f1-914c-1607ee4eb77e","45a5c9e0-798a-11f1-80ac-1607ee4eb77e",147,["D",1783555785052],"# 03 · Wire Dialog into the Gallery as the behavior backstop\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Gallery — self-hosted docs surface](../PRD.md)\n\n## What to build\n\nAdd `Dialog` to the Gallery so its interactive behavior is manually verifiable\nin-browser — the behavior backstop the [Dialog PRD](../../dialog-radix/PRD.md)\nrefers to (open/close, focus-trap, ESC, in-portal token resolution), which the\nrender-seam test deliberately does not cover.\n\nEnd-to-end behavior:\n\n- A Gallery section that imports `Dialog` from its own path (not the barrel) and\n  renders a real, openable example exercising trigger/content/title/description/\n  close.\n- The example confirms, in a real browser against the live Gallery, that the\n  dialog opens/closes, traps focus, closes on ESC and overlay click, and that token\n  custom properties resolve correctly through the Radix portal in both Modes.\n\n## Acceptance criteria\n\n- [ ] The Gallery renders an openable `Dialog` example imported from Dialog's own path (Dialog stays out of the `mod.ts` barrel).\n- [ ] Open/close, focus-trap, ESC, and overlay-click close are manually verifiable in-browser against the live Gallery.\n- [ ] In-portal token resolution is correct in both light and dark Mode (no wrong-theme flash inside the modal).\n\n## Blocked by\n\n- [02 — Promote preview into the canonical Gallery](./02-gallery-build.md)\n- [dialog-radix 01 — Dialog behind its own import path](../../dialog-radix/issues/01-dialog-radix-component.md)\n",[],[217,465,615,465,617],"25f8b9de-febf-495c-b50c-de53d88daa15","02-gallery-build.md","7d9f80c4-7b2a-11f1-ac5e-1607ee4eb77e",143,["D",1783555785109],"# 02 · Promote preview into the canonical Gallery\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Gallery — self-hosted docs surface](../PRD.md)\n\n## What to build\n\nPromote the WIP `preview/` into the real **Gallery** served at `kyla-ui`'s HTTP\nroute: the blessed, self-hosted docs surface that renders every shipped component\nin its variants and Modes, and the in-browser proof that Twind + tokens + Provider\nrender correctly on Val Town.\n\nEnd-to-end behavior:\n\n- Served from `kyla-ui`'s HTTP route, reusing the *corrected* shell mechanics\n  (Twind before first paint, importmap for `npm:` specifiers, `std/catch`,\n  `serveFile`, `/source` redirect). The Gallery **imports** the library from\n  `mod.ts` (and Dialog's own path) and modifies nothing.\n- One **hand-written** section per shipped component showing its full\n  variant/size/tone matrix, plus the design-token swatches.\n- A Mode toggle driven by the library's own `useKylaMode()` (not a hand-rolled\n  toggle).\n- The `preview/` WIP framing is dropped — the 🚧 banner and \"not a stable API\"\n  language go away once this is the canonical Gallery.\n- An HTTP-seam test asserts the route's external behavior.\n\nDialog's in-browser behavior backstop is a follow-up ([03](./03-gallery-dialog-backstop.md)).\n\n## Acceptance criteria\n\n- [ ] The Gallery is served from `kyla-ui`'s HTTP route using the corrected shell (real `index.html`, no inline `<style>`), imports the real library, and modifies nothing.\n- [ ] Each shipped component has a hand-written section rendering its full variant/size/tone matrix; token swatches are shown.\n- [ ] A Mode toggle driven by `useKylaMode()` flips the palette across light/dark/system.\n- [ ] The `preview/` WIP banner and \"not a stable API\" framing are removed.\n- [ ] An HTTP-seam test asserts a `200` HTML response, that each shipped component's section is present, and that token utility classes (e.g. `bg-[color:var(--kyla-…)]`) appear in the served markup — passing under `deno test`.\n\n## Blocked by\n\n- [01 — Bring the preview shell in line with platform conventions](./01-preview-shell-conventions.md) — the Gallery inherits the corrected shell.\n- [v1-component-set 02 — Layout & container primitives](../../v1-component-set/issues/02-layout-and-container-primitives.md) — components to render.\n- [v1-component-set 03 — Form field primitives](../../v1-component-set/issues/03-form-field-primitives.md) — components to render.\n",[],[217,465,615,465,626],"2b988b37-5c4f-4ff7-aed7-4efa4cca8c77","01-preview-shell-conventions.md","45d4ff80-798a-11f1-950b-1607ee4eb77e",89,["D",1783377020859],"# 01 · Bring the preview shell in line with platform conventions\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\nImplementation issue under the [Gallery PRD](../PRD.md). The Gallery adopts the\ncorrected shell this issue produces, so this can land early against `preview/`\nbefore the full Gallery is built. Target: `nbbaier/kyla-ui`, file\n`preview/index.tsx`.\n\n## Context\n\n`preview/`'s route was reviewed against Val Town's documented React/HTTP\nconventions. Two deviations in the HTML shell built inside `preview/index.tsx`:\n\n1. **HTML shell is a template-literal string, not a real file.** The full\n   `<!doctype html>` document is built as a JS template literal and returned via\n   `new Response(html, ...)`. Val Town's own `templates/react-hono-starter` ships a\n   real `frontend/index.html` static file served via `serveFile()`, satisfying the\n   same \"Twind must load before first paint\" requirement (ADR-0001) with a\n   `<script>` tag in that static file. Template-literal HTML gets no syntax\n   highlighting, linting, or type checking.\n2. **Inline `<style>` block in the shell.** The template literal includes a\n   `<style>` tag (body margin reset + the `#root:empty::before` \"Loading preview…\"\n   placeholder). Project convention is Twind/Tailwind utility classes only — no\n   inline `<style>` tags or hand-written CSS.\n\n## Proposed fix\n\n- Extract the shell markup into a real `preview/index.html` file, keeping the\n  Twind `<script>` tag, the importmap (for the `npm:clsx` / `npm:tailwind-merge`\n  specifiers), and the `std/catch` error-reporting script exactly as they are\n  today.\n- Update `preview/index.tsx` to serve that file via\n  `serveFile(\"/preview/index.html\", import.meta.url)` instead of the inline\n  template string. Keep the existing `/source` redirect and the `.ts/.tsx`\n  passthrough (for `client.tsx`, `app.tsx`, `../mod.ts`, etc.) unchanged.\n- Replace the inline `<style>` block with Twind utility classes. The\n  `#root:empty::before` loading-placeholder trick has no direct Tailwind\n  equivalent for `:empty` — either keep one minimal, clearly-commented `<style>`\n  rule just for that, or (preferred, if simple) render an explicit loading\n  placeholder element inside `#root` in the HTML so Twind classes style it\n  directly and the `<style>` tag can be dropped entirely.\n\n## Acceptance criteria\n\n- `preview/index.tsx` no longer contains a template-literal HTML string.\n- No inline `<style>` tag remains, or the one narrow exception is commented with\n  why Twind can't express it.\n- Twind script, `catch` script, importmap, and `/source` redirect all still\n  present and working.\n- `preview/` route verified via `fetch_val_endpoint` after the change — the page\n  still renders the Button / token / mode-switcher showcase with no console errors\n  (check `get_logs`).\n\n## Out of scope\n\n- Kylä UI's Button variant names (`primary`/`subtle`/`ghost`/`danger`) and size\n  scale (`sm`/`md`/`lg`) intentionally differ from `val.town/_ui`'s own\n  vocabulary — a deliberate design choice (modeled on Cloudflare Kumo per\n  CONTEXT.md), not a bug to fix.\n",[],[217,465,615,465,634],"92a7eda9-25fb-4409-9008-b01d2d410386",85,["D",1783377020590],[253,254,255],[217,465,615,465],"217cca91-a478-4fc0-b891-d1f7c65035ee",81,["D",1783377020017],[252,256],[217,465,615],"37cb5ba6-3feb-4612-9d7e-cbefa96b482d","45ccb3ca-798a-11f1-8ef5-1607ee4eb77e","453bae52-798a-11f1-97fb-1607ee4eb77e",88,["D",1783377020818],"# PRD: Dialog (Radix-backed)\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n> Brings the first Radix-backed component into the library, exercising the\n> hybrid-headless split (ADR-0002) and the version-pinned distribution contract\n> (ADR-0004) in real code — not just the throwaway spike. Depends on the\n> [v1 component set](../v1-component-set/PRD.md) for surrounding styled pieces\n> and on the [scales & palette](../structural-scales-palette/PRD.md) for tokens.\n\n## Problem Statement\n\nKylä's architecture bets on a **hybrid foundation**: hand-roll simple visual\ncomponents with zero dependencies, and build the hard interactive ones on a\nheadless library (ADR-0002). That bet is currently proven only in a separate\nthrowaway val (`nbbaier/kyla-ui-spike`). No hard interactive component ships in\nthe library, so the load-bearing mechanics — Radix imported behind its own import\npath, kept out of the barrel so it only loads when used, with the React-18.2.0\n`?deps=` pin propagated through Radix's transitive graph — are unexercised in the\nreal codebase.\n\n## Solution\n\nBring **`Dialog`** into the library as the first Radix-backed component. It lives\nbehind its own import path (a root re-export, e.g. `dialog.tsx`) kept **out** of\nthe `mod.ts` barrel, so consumers who never use it never load Radix. It is styled\nentirely from the token system like every other component; its behavior and\naccessibility (focus trap, ESC, `aria-*`, portal) are delegated to Radix. The\npublic surface stays styling-only — Radix primitives remain internal so a later\nRadix→Base UI swap isn't an API break.\n\n## User Stories\n\n1. As a consumer, I want a `Dialog` component styled on-system, so that modals match the rest of my Kylä app.\n2. As a consumer, I want to import `Dialog` from its own path, so that apps that don't use it never pay Radix's download/parse cost.\n3. As a consumer, I want the `Dialog` to trap focus and close on ESC and overlay click, so that it's accessible without me wiring ARIA by hand.\n4. As a consumer, I want `Dialog` to compose the way I'd expect (trigger, content, title, description, close), so that I can build real modals.\n5. As a consumer, I want the token theme (surfaces, accent, radius) to apply inside the modal, including through the portal, so that light/dark mode is correct everywhere.\n6. As a consumer, I want to override the content's `className`, so that I can size or position a specific dialog without forking.\n7. As a consumer pinning a version, I want `Dialog` to work under the pinned React 18.2.0, so that Radix's transitive deps don't hit the `useState` null mismatch.\n8. As a component author, I want Radix primitives kept internal to the Dialog module, so that swapping to Base UI later doesn't change the public API.\n9. As a maintainer, I want `Dialog` excluded from the `mod.ts` barrel, so that the zero-dep core stays zero-dep.\n10.   As a maintainer, I want the React-version pin applied at Radix's import, so that the spike's mismatch finding is encoded in shipping code.\n11.   As an end user, I want a modal that manages focus and keyboard correctly, so that I can use it with assistive tech.\n12.   As an end user, I want the dialog's colors to match my OS light/dark preference, so that it doesn't flash the wrong theme.\n\n## Implementation Decisions\n\n- **Modules built:** `src/components/dialog.tsx` (styled composition over Radix)\n  plus a root re-export path (e.g. `dialog.tsx` at the repo root) that is the\n  consumer's import URL. **Not** added to `mod.ts` (ADR-0002/0004).\n- **React pin (spike finding, load-bearing):** import Radix with\n  `?deps=react@18.2.0,react-dom@18.2.0` so the pin propagates through Radix's\n  whole transitive graph and defuses the React-mismatch `useState` null error.\n- **Public API is styling-only:** expose a composed, token-styled Dialog surface\n  (root/trigger/content/overlay/title/description/close). Radix's own primitives\n  are an internal implementation detail and are not re-exported, so a later\n  Radix→Base UI variant is not an API break.\n- **Tokens through the portal:** content uses the `elevated` surface, overlay a\n  scrim, focus ring from tokens; verify token custom properties resolve inside\n  the Radix portal (the spike confirmed `light-dark()` resolves in-portal).\n- **Radix first** (proven on VT); a Base-UI-backed variant stays deferred.\n- **Twind hint discipline still applies** inside the portal — all colors go\n  through the `tw` helpers (ADR-0001), no bare `[var(--…)]` color utilities.\n\n## Testing Decisions\n\n- **What makes a good test:** it verifies **our** contribution — that we mounted\n  Radix with the right props and token styling — and does **not** re-test Radix's\n  own guarantees. Testing that Radix traps focus is testing Radix, not Kylä.\n- **Two-level seam:**\n   - **Primary (server-render, uniform with the component set):** render the\n     Dialog's trigger/closed surface (and the content in an open-by-default\n     configuration where feasible) to an HTML string and assert our wiring — token\n     utility classes present on overlay/content, `className` override wins, title/\n     description associated, close affordance present. This catches the silent\n     Twind hint failure the same way as the rest of the set.\n   - **Behavior backstop (browser):** open/close, focus-trap, ESC, and\n     in-portal token resolution are interaction guarantees best confirmed in a\n     real browser — via the [Gallery](../gallery/PRD.md) once Dialog is listed\n     there. Treat this as the higher-fidelity seam for _behavior_, not a unit\n     test of Radix internals.\n- **Modules tested:** `src/components/dialog.tsx` (render seam).\n- **Prior art:** the render-to-HTML harness from the\n  [v1 component set](../v1-component-set/PRD.md); the spike val is the reference\n  for the working Radix + React-pin + portal configuration.\n\n## Out of Scope\n\n- Other Radix-backed components (`Popover`, `Menu`, `Tabs`, `Tooltip`,\n  `Combobox`, `Toast`) — v1.1+.\n- The **Base UI** variant (deferred until Radix proves the path).\n- Adding `Dialog` to the barrel (deliberately excluded).\n\n## Further Notes\n\n- This PRD is the real-code payoff of the spike. If anything in the spike's Radix\n  configuration proves brittle in the library, capture it as an ADR update rather\n  than a local workaround.\n- Because `Dialog` defines the _pattern_ for every future Radix-backed component,\n  keep the internal/exposed boundary crisp — it's what protects the Radix→Base UI\n  option.\n",[],[217,465,659,458],"dialog-radix","42b4d585-0722-4794-95eb-53db3eb73d1d","01-dialog-radix-component.md","7d915dc8-7b2a-11f1-801b-1607ee4eb77e","7d421ede-7b2a-11f1-914c-1607ee4eb77e",141,["D",1783555785051],"# 01 · Dialog behind its own import path (Radix + React pin + token styling)\n\nStatus: ready-for-agent\nLabels: ready-for-agent\n\n## Parent\n\n[PRD: Dialog (Radix-backed)](../PRD.md)\n\n## What to build\n\nBring `Dialog` into the library as the first Radix-backed component, encoding the\nhybrid-headless split (ADR-0002) and the version-pinned distribution contract\n(ADR-0004) in shipping code. This ticket defines the pattern every future\nRadix-backed component follows, so keep the internal/exposed boundary crisp.\n\nEnd-to-end behavior:\n\n- A token-styled `Dialog` composition over Radix\n  (root/trigger/content/overlay/title/description/close), styled entirely from the\n  token system; behavior and accessibility (focus trap, ESC, `aria-*`, portal)\n  delegated to Radix.\n- Served from its **own root re-export path** (e.g. `dialog.tsx`) and kept **out**\n  of the `mod.ts` barrel, so consumers who never use it never load Radix.\n- Radix imported with `?deps=react@18.2.0,react-dom@18.2.0` so the pin propagates\n  through Radix's transitive graph and defuses the React-mismatch `useState` null\n  error found in the spike.\n- Public surface is styling-only — Radix primitives stay internal (not re-exported)\n  so a later Radix→Base UI swap is not an API break. Content uses the `elevated`\n  surface, overlay a scrim, focus ring from tokens; token custom properties resolve\n  inside the portal. All colors go through the `tw` helpers (ADR-0001).\n- A render-seam test asserts **our** wiring — token utility classes on\n  overlay/content, `className` override wins, title/description associated, close\n  affordance present — and does not re-test Radix's own guarantees.\n\nThe in-browser behavior backstop (open/close, focus-trap, ESC, in-portal token\nresolution) is verified via the [Gallery](../../gallery/PRD.md), not here.\n\n## Acceptance criteria\n\n- [ ] `Dialog` renders a token-styled composition over Radix; overlay/content carry token utility classes via the `tw` helpers (no bare `[var(--…)]` color utilities).\n- [ ] `Dialog` is importable from its own root re-export path and is **not** exported from `mod.ts`.\n- [ ] Radix is imported with the `?deps=react@18.2.0,react-dom@18.2.0` pin; the dialog renders under the pinned React without the `useState` null mismatch.\n- [ ] Radix primitives are not re-exported; the public surface is styling-only.\n- [ ] A render-seam test asserts token classes on overlay/content, `className` override wins, title/description association, and close affordance — passing under `deno test`.\n\n## Blocked by\n\n- [v1-component-set 01 — Render-to-HTML harness + Text / Heading](../../v1-component-set/issues/01-render-harness-and-typography.md) — provides the render-seam harness the test reuses.\n- [v1-component-set 03 — Form field primitives](../../v1-component-set/issues/03-form-field-primitives.md) — provides the surrounding styled pieces real modals compose with.\n- [Real palette + first contrast test harness](../../structural-scales-palette/issues/01-real-palette-and-contrast-harness.md) — provides the surface/scrim/focus tokens resolved through the portal.\n",[],[217,465,659,465,661],"e62921aa-e61c-4a6c-b9b5-cc98353408fb",137,["D",1783555784543],[249],[217,465,659,465],"5eec4490-fa6a-4d69-a14b-b33255dd6e81",80,["D",1783377019910],[248,250],[217,465,659],"a2c9ad46-23a8-460e-94fa-f026945b61c3",79,["D",1783377019794],[247,251,257,263,270],[217,465],"77ad0601-a1d3-41a5-b58e-81ba37ac5b0a","2026-06-18-design-and-foundation.md","cde8b7ca-6b54-11f1-b7ac-1607ee4eb77e","cdcfbd74-6b54-11f1-bde2-1607ee4eb77e",60,["D",1781814740095],"# Handoff — Kylä UI design + foundation (2026-06-18)\n\nPicking up the `nbbaier/kyla-ui` component library for Val Town. This thread did the\ndesign grilling, proved the runtime substrate, and built the styling foundation + the\nfirst component (`Button`). This doc is a pointer map + \"what's next\", not a re-spec —\nthe real content lives in the artifacts referenced below.\n\n## Read these first (don't duplicate them)\n\n- [`CONTEXT.md`](../../CONTEXT.md) — glossary / shared language.\n- [`docs/v1-design-sketch.md`](../v1-design-sketch.md) — the design hub, **Implementation\n  status** section, open spikes (all ✅), and the \"Deliberately deferred\" list.\n- [`docs/adr/0001..0004`](../adr/) — the load-bearing decisions and *why*.\n- [`README.md`](../../README.md) — consumer-facing quick start.\n\n## State of the world\n\n- **Two vals.** `nbbaier/kyla-ui` (the library; locally synced to this working dir via\n  `vt`). `nbbaier/kyla-ui-spike` (throwaway substrate proof — all 4 spikes green\n  in-browser; keep it around as a live sandbox).\n- **Foundation built & verified on the runtime:** `mod.ts` barrel + `src/utils/`\n  (`cn`, `variants`), `src/theme/` (`tokens`, `tw`, `provider`), `src/components/`\n  (`button`). Layout rationale is in the sketch's Implementation status.\n- **`Button`** ships with `variant` × `size`, token focus ring, ref forwarding,\n  escape-hatch `className`. Verified by server-render (`renderToStaticMarkup`).\n- Everything is pushed; `vt status` was clean at handoff time.\n\n## Gotchas that will bite you if forgotten\n\n1. **The `color:` hint is mandatory** for token color utilities — `bg-[color:var(--…)]`,\n   never `bg-[var(--…)]` (the latter silently renders nothing; no error). Always go\n   through the `tw.*` builders in `src/theme/tw.ts`, which bake it in. (ADR-0001.)\n2. **Twind lives in the HTML shell**, not the Provider (must load before first paint).\n   The Provider injects only the token stylesheet. (ADR-0001.)\n3. **Pin React to 18.2.0 everywhere**, including Radix via\n   `?deps=react@18.2.0,react-dom@18.2.0`, or you hit the `useState` null error. (ADR-0002.)\n4. **`cn(componentClasses, className)` call order** is the contract — caller's\n   `className` must come last to win.\n5. **Token values in `src/theme/tokens.ts` are provisional** — not the real palette yet.\n\n## Suggested next steps (roughly in order)\n\n1. **See `Button` live** — add a showcase row to `kyla-ui-spike`'s `App.tsx` to eyeball\n   all variant/size combos + hover/focus in a browser. (Quick loop-closer.)\n2. **Real palette + structural scales** — replace provisional tokens with AA-checked\n   surface/fg/border ramps + spacing/radius/type scales. Highest-leverage deferred item.\n3. **More components** — `Card`, `Text`/`Heading`, `Input`, `Textarea`, `Label`, `Badge`,\n   `Stack`, `Box`, `Divider`, then native-styled `Select`. Reuse the Button pattern.\n4. **`Dialog` (Radix)** — first component behind its own import path: `src/components/dialog.tsx`\n   + a root `dialog.ts` re-export, kept OUT of `mod.ts` (ADR-0002). Exercises the split.\n5. **Gallery** — the library's self-hosted docs HTTP route (CONTEXT.md → \"Gallery\").\n6. **Starter** — `kyla-ui-starter`: a tiny todo app (CONTEXT.md → \"Starter\").\n\n## How to work in this repo\n\n- Edit locally, then `vt push` (and `vt pull` first if needed). `vt status` shows drift.\n- **Smoke-test pattern that works without a browser:** create a throwaway\n  `src/_smoke.ts(x)` in the val, `run_file` it (use `renderToStaticMarkup` from\n  `react-dom@18.2.0/server` to render components to a class string), then `delete_file`\n  it. Used twice this thread; clean and fast.\n- For anything UI/platform-specific on Val Town, pull the official skill via the valtown\n  MCP `find_val_town_skills` tool rather than working from memory.\n\n## Suggested skills for the next session\n\n- **valtown:react-ui** — the canonical conventions (Twind, React pin, view-source) for\n  any component or Gallery work.\n- **grill-with-docs** — if revisiting design decisions (palette, theming v2, new\n  components' APIs); it updates `CONTEXT.md` / ADRs inline.\n- **valtown:sqlite-storage** + **valtown:http-endpoints** — when building the Starter\n  todo app and/or the Gallery route.\n- **rams** (or **impeccable**) — accessibility / visual-design review once there are\n  enough components and the real palette to evaluate.\n",[],[217,693,685],"handoffs","a7030e21-e7a7-4098-b3a8-8ab22885d8dc",59,["D",1781814739944],[245],[217,693],"2f0b95ab-6e0e-43f8-ba59-02b6dfc199b7","triage-labels.md","a548ab54-775c-11f1-8e89-1607ee4eb77e","a519c118-775c-11f1-8e89-1607ee4eb77e",180,["D",1784058609807],"# Triage Labels\n\nThe skills speak in terms of five canonical triage roles. This file maps those\nroles to the actual label strings used in this repo's issue tracker.\n\n| Label in mattpocock/skills | Label in our tracker | Meaning                                  |\n| -------------------------- | -------------------- | ---------------------------------------- |\n| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |\n| `needs-info`               | `needs-info`         | Waiting on reporter for more information |\n| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |\n| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |\n| `wontfix`                  | `wontfix`            | Will not be actioned                     |\n\nWhen a skill mentions a role (e.g. \"apply the AFK-ready triage label\"), use the\ncorresponding label string from this table.\n\nEdit the right-hand column to match whatever vocabulary you actually use.\n\n## Completion\n\nThe five roles above are _triage_ states — none marks work as finished. This\nrepo adds one local completion label beyond that vocabulary:\n\n| Label  | Meaning                                                                  |\n| ------ | ------------------------------------------------------------------------ |\n| `done` | Work merged to `main` and shipped in a Release (see `issue-tracker.md`). |\n",[],[217,708,700],"agents","1580c35d-8057-47e4-a83d-b03ae3fa2342","issue-tracker.md","a560b8ac-775c-11f1-88a1-1607ee4eb77e",181,["D",1784058609890],"# Issue tracker: Local Markdown\n\nIssues and PRDs for this repo live as markdown files in `docs/issues/`.\n\n## Conventions\n\n- One feature per directory: `docs/issues/<feature-slug>/`\n- The PRD is `docs/issues/<feature-slug>/PRD.md`\n- Implementation issues are `docs/issues/<feature-slug>/issues/<NN>-<slug>.md`,\n  numbered from `01`\n- Triage state is recorded as a `Status:` line near the top of each issue file\n  (see `triage-labels.md` for the role strings)\n- A ticket is **done** when its work merges to `main` (which cuts a Release per\n  ADR-0004): set `Status: done` and add a `Landed: v<NNN>` line recording the\n  Release version\n- Comments and conversation history append to the bottom of the file under a\n  `## Comments` heading\n\n## When a skill says \"publish to the issue tracker\"\n\nCreate a new file under `docs/issues/<feature-slug>/` (creating the directory if\nneeded).\n\n## When a skill says \"fetch the relevant ticket\"\n\nRead the file at the referenced path. The user will normally pass the path or\nthe issue number directly.\n\n## Wayfinding operations\n\nUsed by `/wayfinder`. The **map** is a file with one **child** file per ticket.\n\n- **Map**: `docs/issues/<effort>/map.md` — the Notes / Decisions-so-far / Fog\n  body.\n- **Child ticket**: `docs/issues/<effort>/issues/NN-<slug>.md`, numbered from\n  `01`, with the question in the body. A `Type:` line records the ticket type\n  (`research`/`prototype`/`grilling`/`task`); a `Status:` line records\n  `claimed`/`resolved`.\n- **Blocking**: a `Blocked by: NN, NN` line near the top. A ticket is unblocked\n  when every file it lists is `resolved`.\n- **Frontier**: scan `docs/issues/<effort>/issues/` for files that are open,\n  unblocked, and unclaimed; first by number wins.\n- **Claim**: set `Status: claimed` and save before any work.\n- **Resolve**: append the answer under an `## Answer` heading, set\n  `Status: resolved`, then append a context pointer (gist + link) to the map's\n  Decisions-so-far in `map.md`.\n",[],[217,708,710],"bdce4b08-1b12-451b-8c91-9c569f1be5c3","domain.md","a52e4908-775c-11f1-a7d7-1607ee4eb77e",179,["D",1784058609790],"# Domain Docs\n\nHow the engineering skills should consume this repo's domain documentation when\nexploring the codebase.\n\n## Before exploring, read these\n\n- **`CONTEXT.md`** at the repo root, or\n- **`CONTEXT-MAP.md`** at the repo root if it exists — it points at one\n  `CONTEXT.md` per context. Read each one relevant to the topic.\n- **`docs/adr/`** — read ADRs that touch the area you're about to work in. In\n  multi-context repos, also check `src/<context>/docs/adr/` for context-scoped\n  decisions.\n\nIf any of these files don't exist, **proceed silently**. Don't flag their\nabsence; don't suggest creating them upfront. The `/domain-modeling` skill\n(reached via `/grill-with-docs` and `/improve-codebase-architecture`) creates\nthem lazily when terms or decisions actually get resolved.\n\n## File structure\n\nSingle-context repo (most repos):\n\n```\n/\n├── CONTEXT.md\n├── docs/adr/\n│   ├── 0001-event-sourced-orders.md\n│   └── 0002-postgres-for-write-model.md\n└── src/\n```\n\nMulti-context repo (presence of `CONTEXT-MAP.md` at the root):\n\n```\n/\n├── CONTEXT-MAP.md\n├── docs/adr/                          ← system-wide decisions\n└── src/\n    ├── ordering/\n    │   ├── CONTEXT.md\n    │   └── docs/adr/                  ← context-specific decisions\n    └── billing/\n        ├── CONTEXT.md\n        └── docs/adr/\n```\n\n## Use the glossary's vocabulary\n\nWhen your output names a domain concept (in an issue title, a refactor proposal,\na hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift\nto synonyms the glossary explicitly avoids.\n\nIf the concept you need isn't in the glossary yet, that's a signal — either\nyou're inventing language the project doesn't use (reconsider) or there's a real\ngap (note it for `/domain-modeling`).\n\n## Flag ADR conflicts\n\nIf your output contradicts an existing ADR, surface it explicitly rather than\nsilently overriding:\n\n> _Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_\n",[],[217,708,718],"e1da9f80-ef2b-4841-92f9-45fc459f2a2d",63,["D",1783137521569],[241,242,243],[217,708],"5ff5efb0-bcca-44c6-9bc3-abec2da1ffbb","0005-val-town-visual-language-default-theme.md","c7b195b4-798e-11f1-aabb-1607ee4eb77e","bc9c5da4-6b46-11f1-aeb1-1607ee4eb77e",178,["D",1784058609606],"# Default theme adopts the Val Town visual language\n\nKylä UI ships **one opinionated default theme** (CONTEXT.md → Theme; ADR-0001).\nUntil now its palette and scales were provisional placeholders, implicitly\nderived from our Cloudflare Kumo lineage. We decide that the default theme's\n**values** — color palette (light + dark), the spacing / radius / type scales,\nand the component-level styling those map to — **conform to the Val Town UI\nstyle guide** (`val.town/_ui`), so that an app built with Kylä looks native to\nVal Town rather than like a foreign design system dropped onto the platform.\n\nThis is a decision about **values, not architecture and not API**. It changes\nwhat the `--kyla-*` tokens resolve to; it does not change how the system is\nbuilt or how consumers call it:\n\n- **Architecture stays Kumo-modeled.** Semantic tokens as CSS custom properties\n  (ADR-0001), the hybrid headless foundation (ADR-0002), primitives + components\n  — all unchanged. The token indirection is precisely what lets us retarget the\n  look without touching components.\n- **API vocabulary stays Kylä's own.** Kylä keeps its Kumo-style variant model —\n  `Button` `variant` = `primary | subtle | ghost | danger`, `size` =\n  `sm | md | lg`, etc. — which deliberately differs from `val.town/_ui`'s own\n  class vocabulary. Adopting VT's _values_ does not rename Kylä's _props_. (This\n  is consistent with the note in the Gallery's preview-shell issue: the\n  divergence recorded there was about **names**, not **palette**.)\n- **Positioning (ADR-0003) is reinforced, not changed.** \"Lead with consistency\"\n  now means consistency _with the surrounding Val Town platform_, not just\n  internal self-consistency.\n\n## Source of truth for the values\n\nThe values are extracted from Val Town's own style guide and captured in\n`docs/reference/val-town-style-guide.md`, so downstream PRDs consume concrete\nnumbers rather than \"conform to VT\" prose. Primary sources (Val Town's site is\nRemix, server-rendered, so the component markup and its compiled token CSS are\nfetchable over plain HTTPS):\n\n- `https://www.val.town/_ui/*` — the live style-guide pages (button, callout,\n  card, dropdown, input, select, textarea, forms, privacy-badge); SSR markup\n  gives each component's verbatim utility classes.\n- `https://static2.esm.town/assets/tailwind-*.css` — the compiled Tailwind v4\n  stylesheet the pages link: the `@theme` token scale (`--color-*` oklch ramp,\n  `--spacing`, `--radius-*`, `--text-*`, fonts, weights) and VT's semantic\n  aliases split across `:root`/`.dark`.\n- `https://www.val.town/x/dcm31/townie-mobile/code/frontend/style.css` — a\n  hand-distilled token artifact billed by its author as Val Town's style guide\n  (\"gave Fable our style guide\"); used as a corroborating cross-check (it is\n  Tailwind v3, so the live `_ui` v4 values are treated as source of truth).\n\n## Considered Options\n\n- **Invent an opinionated palette/scale (Kumo-flavored)** — rejected: arbitrary,\n  and it forfeits the chance to make Kylä apps look like they belong on their\n  host platform. A bespoke look is a liability, not a feature, for this\n  audience.\n- **Adopt VT's values _and_ its class vocabulary** — rejected/deferred:\n  API-breaking, and Kylä's typed variant model is more expressive than raw\n  utility classes. Revisit only if there's a concrete reason to mirror VT's prop\n  names; it is explicitly **not** part of this decision.\n- **Adopt VT's values as the default theme; keep Kylä's architecture and API** —\n  **chosen.**\n\n## Consequences\n\n- The `structural-scales-palette` PRD is reframed: instead of _designing_ a\n  palette + scales, it **ports** the Val Town style guide's palette and scales\n  into the token stylesheet, sourced from the reference doc above. This is why\n  the decision must be recorded before that PRD is implemented.\n- **Coverage parity is the bar, not just palette adoption.** The\n  `v1-component-set` PRD uses `val.town/_ui` as the styling reference for its\n  per-component variant→token maps (button sizing/radius, input styling, badge\n  tones) — but \"conforms to VT\" means matching the _set_ of variants, states,\n  and techniques VT ships per component (color variants, icon-only sizing,\n  hover/active/disabled states, mode-adaptive techniques like `blend`'s\n  `mix-blend-mode`), not only porting palette hex/oklch values onto whatever\n  variant list a component already happens to have. Kylä's prop _names_ stay its\n  own (previous bullet); the _coverage_ those names collectively provide must\n  match VT's per-component surface, checked against\n  `docs/reference/val-town-style-guide.md`. This applies retroactively: a\n  component the roadmap already marks \"Built\" (e.g. `Button`, shipped with 4 of\n  VT's 7 button variants) is still subject to this bar and gets a revision\n  slice, not a pass.\n- **AA contrast (ADR-0003) remains the stricter constraint.** Every sanctioned\n  foreground/surface pairing must meet WCAG AA in both modes. If VT's guide has\n  a pairing that falls short, Kylä's AA guarantee wins and that token value is\n  adjusted; the contrast test enforces this regardless of source.\n- **Kylä keeps its own surface hierarchy.** The extraction\n  (`docs/reference/val-town-style-guide.md`) found VT's _semantic_ layer is\n  thinner than Kylä's — VT names only\n  `background / text / border / muted / shadow` and elevates by shadow over a\n  single surface. Kylä retains its structural `base` → `elevated` → `recessed`\n  hierarchy and `hairline` (CONTEXT.md); where VT has no named token, those\n  values are sourced from VT's slate component fills. So the default theme is\n  **VT's palette under Kylä's structure**, not a strict subset of VT's tokens.\n- **The token vocabulary expands to cover VT's accent + status roles.** VT uses\n  accent in three roles a single `accent`/`accent-fg` can't hold (fill,\n  focus-ring, accent-text-on-surface), and ships a success tone. The canonical\n  `--kyla-*` vocabulary therefore gains `accent-ring`, `accent-text`,\n  `danger-fg`, and a `success`/`success-fg` tone (updating CONTEXT.md's token\n  list and the `ColorToken` union). These are **structural** additions — the\n  consumer override surface stays small.\n- **One deliberate deviation from VT:** the dark-mode `base` uses `slate-950`\n  (`#020618`), a considered softening of VT's literal true-black (`#000`, 21:1)\n  to reduce large-surface glare. Recorded here so it reads as a choice, not an\n  extraction error; every other default tracks VT.\n- The consumer **override surface** (`--kyla-accent`, `--kyla-radius`, font) is\n  unchanged; its _defaults_ become the VT values, and a consumer can still\n  rebrand within that small surface.\n- If Val Town revises its style guide, Kylä tracks it by re-running the\n  extraction and retuning token values — a values change under the existing\n  Release contract (ADR-0004), not an API change.\n",[],[217,739,731],"adr","e212033c-6c56-41c7-af04-c89fa2adbb32","0004-version-pinned-upgrade-contract.md","bcb00034-6b46-11f1-9b3f-1607ee4eb77e",16,["D",1781808698266],"# Upgrade contract: main-as-release-line, version pinning\n\nKylä UI is consumed by importing its val from esm.town, where an unpinned import (`.../kyla-ui/mod.ts`) auto-redirects to the val's latest version and a consumer can freeze onto a specific version with `?v=NNN`. esm.town does **not** offer branch-name import URLs, so the intuitive \"consumers track a long-lived `stable` branch\" model is not available.\n\nWe therefore make **`main` the stable/release line**: all development happens on feature/dev branches, and a **Release is a merge into `main`.** Because raw work never lands on `main`, HEAD-of-`main` is always a Release. Consumers then have two contracts:\n\n- **Track latest** — import the unpinned URL; always get the newest Release, so fixes auto-propagate (the upside of consumption-by-import).\n- **Freeze** — pin `?v=NNN` from the README's release table; upgrade deliberately by changing the number.\n\n## Considered Options\n\n- **Long-lived `stable` branch consumers import** — rejected: esm.town has no documented branch-import URL, so it isn't realizable.\n- **Live HEAD with raw development on the imported line** — rejected: any work-in-progress push would reach unpinned consumers; keeping development off `main` is what makes the unpinned URL safe.\n\n## Consequences\n\n- Unpinned consumers receive a new Release the instant a branch merges — *including a breaking one*. The release table plus brief per-release notes are how a consumer decides whether to pin. There is no staging window between merge and propagation.\n- Every merge to `main` mints a new `?v=NNN`; the README maps human release names to those version numbers.\n- For v1 (sole consumer is the maintainer) this can be operated loosely, but the convention costs nothing now and makes external consumption safe later.\n",[],[217,739,741],"b6c16ec9-cf60-4046-8c73-1a4b361711e4","0003-consistency-first-bounded-accessibility.md","bcc6125c-6b46-11f1-9996-1607ee4eb77e",176,["D",1784058609135],"# Consistency-first positioning, bounded accessibility\n\nKylä UI is modeled on Cloudflare Kumo, whose headline value is accessibility. We\ndeliberately invert the emphasis: **Kylä leads with visual consistency** — the\nfelt pain for the Val Town audience (people shipping apps fast without a\ndesigner) is that hand-assembled UIs look inconsistent, not that they fail an\naudit. Accessibility remains a real but _quiet_ guarantee underneath, with a\ndeliberately bounded scope for v1.\n\nThe accessibility commitment is exactly: **correct semantic HTML** (native\n`<button>`, real `<label htmlFor>`/`<input id>` association, `<h1–h6>`\nheadings), **token-based visible focus**, **not breaking native keyboard\nbehavior**, and **WCAG-AA contrast on the default theme** (a property of the\nTheme, set once). Anything requiring custom ARIA roles/state is _not_\nhand-rolled — it is built on a Headless Primitive (Radix), which is the dividing\nline of ADR-0002.\n\n## Why record this\n\nA contributor seeing the Kumo lineage will reasonably assume accessibility is\nthe headline and try to chase full WCAG-AA across the hand-rolled zero-dep\ncomponents. That is a deliberate non-goal for v1, not an oversight: the bounded\npromise is one we can actually keep, and \"needs more than semantic HTML\" is\nprecisely the signal a component belongs in the Radix tier. Full WCAG auditing\nis additive and can be revisited later; it should not silently expand v1 scope.\n",[],[217,739,749],"ba183b72-0b8a-428d-b307-0cfb2c364632","0002-hybrid-headless-foundation.md","bcb42b28-6b46-11f1-8453-1607ee4eb77e",177,["D",1784058609622],"# Hybrid headless foundation, Radix-first\n\nKumo builds every component on Base UI headless primitives for accessibility. On\nVal Town a headless library is an unvetted heavy ESM dependency loaded from a\nCDN at runtime, so we take it selectively: **simple visual components (Button,\nCard, Stack, Text, Input, Badge) are hand-rolled with zero dependencies**, and\n**only the genuinely hard interactive components (Dialog, Popover, Menu, Tabs)\nbuild on a third-party headless library.** This keeps the common case\ndependency-free and fast on Val Town while still inheriting accessibility where\nit is expensive to get right.\n\nThe library is **Radix first** — chosen over the maintainer's preferred Base UI\npurely because Radix has a longer track record loading from CDNs — used to prove\nthe pattern works on Val Town. A Base-UI-backed variant is a likely later step\nonce viability is demonstrated.\n\n## Consequences\n\n- Open validation task before committing: confirm a Radix primitive (e.g.\n  Dialog) imports via esm.sh with React pinned to 18.2.0 and hydrates cleanly on\n  Val Town's CSR setup.\n- Swapping the headless library later is contained per-component, not a global\n  rewrite — which is what makes \"Radix now, Base UI later\" affordable.\n",[],[217,739,757],"64148f51-d4d1-4308-b92b-872e98462b3a","0001-no-build-styling-architecture.md","bcbd4aa0-6b46-11f1-9db1-1607ee4eb77e",175,["D",1784058609426],"# No-build styling architecture\n\nKylä UI targets Val Town, which has no build step or bundler. Cloudflare Kumo —\nour model — achieves visual consistency with Tailwind v4 semantic tokens\ncompiled at build time, which we cannot use. We therefore deliver consistency at\nruntime: **semantic design values are defined as CSS custom properties** (a\ntoken stylesheet served by the `kyla-ui` val, using `light-dark()` for automatic\ndark mode), and **components apply them via runtime Twind arbitrary-value\nutilities** (e.g. `bg-[var(--kyla-base)]`). Styles are delivered with a\ndeliberate split (confirmed by the `kyla-ui-spike`): the **Twind script lives in\nthe HTML shell** (it must load before first paint or utilities FOUC, so it\ncannot be React-injected), while the **token stylesheet is injected by the\nProvider at runtime** (idempotently). The Starter ships the shell tag; the\nProvider guarantees the tokens — so \"styles are present\" is a guarantee, not a\nsetup checklist (a manual two-tag `<head>` setup is the documented escape\nhatch).\n\n## Considered Options\n\n- **Tailwind v4 + build step (the Kumo way)** — rejected: requires a\n  bundler/PostCSS, which Val Town does not provide.\n- **Twind with a named-token theme config** (`bg-kyla-base`) — rejected: every\n  consumer app would have to load an identical Twind runtime config or\n  components render wrong; that coupling is a sharp, silent failure mode.\n- **Pure CSS component classes** (`.kyla-button`) — rejected: self-contained but\n  abandons Tailwind/Twind ergonomics and composable variants, and strays from\n  the Val Town idiom.\n\n## Consequences\n\n- Arbitrary-value Twind syntax is noisier, but it lives inside library source;\n  consumers only write `<Button>`.\n- Components only render correctly where Twind is running and the token\n  stylesheet is loaded — hence the Provider (see ADR-0002's sibling delivery\n  decision) is load-bearing.\n- The `light-dark()` CSS function handles dark mode without `dark:` variants,\n  keeping component source theme-agnostic.\n- **Authoring rule (proven by the spike):** semantic-color utilities must carry\n  the `color:` type hint — `bg-[color:var(--kyla-base)]`,\n  `text-[color:var(--kyla-fg)]`, `border-[color:var(--kyla-line)]`. A bare\n  `bg-[var(--…)]` is type-ambiguous and Twind silently emits nothing (the\n  failure is invisible — no error, just an unstyled element). Lengths are\n  unambiguous, so `rounded-[var(--kyla-radius)]` needs no hint. Because the\n  omission fails silently, component authors must not hand-write these strings;\n  the `cn()`/variant layer should emit token utilities through a tiny helper so\n  the hint can never be forgotten.\n",[],[217,739,765],"5952a1d0-5e01-4609-a8ae-f86b41871f4b",15,["D",1781808698135],[235,236,237,238,239],[217,739],["D",1781808698019],[234,240,244,246,277,279],[217],["D",1781804868537],["D",1789701064442],{"_98":97,"_105":101},{"_98":97,"_99":-5,"_100":101,"_18":55,"_102":103,"_104":25},{"_13":87,"_32":88,"_43":42,"_89":44,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":45,"_96":97},"ctx",{"_80":-5,"_126":818,"_819":820,"_821":822,"_823":25,"_824":25,"_825":25,"_826":124,"_827":-5,"_828":-7,"_829":-7,"_830":61,"_831":25,"_832":25,"_833":-5,"_834":25,"_835":25,"_836":25,"_837":-5},"ENV",{"_789":790,"_791":792,"_793":88,"_794":795,"_796":797,"_798":799,"_800":801,"_802":803,"_804":805,"_806":807,"_808":809,"_810":811,"_812":813,"_814":815,"_816":817},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","71c1b20804b3232a7e513be260cfffc1932a9e97","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]
</article></body></html>

Diff · v182