@livx.cc/bare-v3 0.1.0-alpha.8 → 0.1.0-alpha.80

package/README.md

@@ -1,6 +1,6 @@
 # bare-v3
 
-Experimental semantic styling and a standalone design evaluation lab for Composer. **No strategy winner has been established.** An opt-in, source-pinned Blank integration experiment is underway; release readiness and default-strategy selection still require qualification.
+Experimental semantic styling and a standalone design evaluation lab for Composer. **No strategy winner has been established.** Blank currently uses v3 for new apps in an observation rollout, with released versions pinned for existing apps. Long-term readiness, native-device quality and comparative model efficiency still require qualification.
 
 ```sh
 bun install --frozen-lockfile
@@ -17,23 +17,25 @@ The comparison UI needs the fixture server for example links. Model outputs repl
 
 Install the published alpha with `bun add @livx.cc/bare-v3@alpha`; use `bun pm pack` for an unpublished local build. Import CSS from `@livx.cc/bare-v3/css` or `/css/min`. Put `class="b3-root"` on html and set `data-b3-theme="dark"` explicitly for dark mode. Component references are exported under `/references/*.md`; start with `/references/start.md`. Place generic link defaults in `@layer bare.reset` so they do not override button/navigation colors. Unlayered consumer CSS overrides library layers: scope custom palette colors to each theme rather than applying light-only colors unconditionally to `:root`.
 
-`bun lab plan config.json` creates a seeded, capped development job plan. `bun lab prepare run.json` prepares one isolated workspace and manifest without invoking a model. The [visual playground](http://127.0.0.1:4313/fixtures/playground.html) demonstrates the current component contracts and shows the bare-v2 coverage audit. Composed apps include Signal (system performance), Elsewhere (local discovery/booking), Daylight (iOS/Android web studies), Relay, Gather setup and sign-in, Counter, Margin, Still, Fieldnotes, Interval, and the Forma project workspace. New components are an implemented subset, not full bare-v2 parity or a qualified release. Optional interactions are exported from `@livx.cc/bare-v3/ui`; call `mount(document)` once and use its returned cleanup on teardown.
+`bun lab plan config.json` creates a seeded, capped development job plan. `bun lab prepare run.json` prepares one isolated workspace and manifest without invoking a model. The [visual playground](http://127.0.0.1:4313/fixtures/playground.html) demonstrates the current component contracts and shows the bare-v2 coverage audit. Composed apps include Signal (system performance), Elsewhere (local discovery/booking), Daylight (iOS/Android web studies), Relay, Gather setup and sign-in, Counter, Margin, Still, Fieldnotes, Interval, and the Forma project workspace. New components are an implemented subset, not full bare-v2 parity or a qualified release. Two public layers ship: `/css` (CSS only) and `/components` — light-DOM custom elements (`<b3-tabs>`, `<b3-reel>`, `<b3-dropdown>`, `<b3-dialog>`, `<b3-sheet>`, `<b3-command>`, `<b3-toast-region>`, `<b3-toc>`) that enhance native markup, plus the document-wide `data-b3-confirm` guard and the `motion`/`layout`/`sequence`/`settle` helpers. Loading the entry (ESM, or re-bundled as a classic script) registers everything; there is no setup call or cleanup, and loading twice is a no-op. Heavier components are opt-in subpaths: `/components/board` (`<b3-board>`), `/components/date-picker` and `/components/image-viewer`. They are separate files rather than one bundle because of weight: the core is ~20 KB minified (~7 KB gzip), the board alone ~117 KB (~36 KB gzip, it bundles a reactive template runtime privately — one that needs no `'unsafe-eval'` under a Content-Security-Policy and loads only when a board first renders), so a single bundle would multiply every page's always-loaded cost by ~5x for a component most pages never show. `/markdown-stream` is a plain module (`MarkdownStream`, a class, not a tag) for streaming LLM markdown into bare-v3 components. Every entry ships `.d.ts` typings. Read `recipes/board.md`, `recipes/image-viewer.md`, `recipes/date-picker.md` or `recipes/markdown-stream.md` for markup and lifecycle; `fixtures/elements/markdown-stream.html` demos the stream; `bun run chat` serves it as a live chat against a real model (needs `OPENROUTER_API_KEY` or `OPENAI_API_KEY`; offline it replays canned replies). The plain/React/Vue demos in `fixtures/elements/` exercise the image viewer; run `bun scripts/verify-image-viewer.ts` through the authorized AgentX browser workflow to verify measured transforms. `bun scripts/verify-components.ts`, `verify-reel.ts` and `verify-confirm.ts` drive headless Chrome against `fixtures/checks/` and re-run every check against a control build without the code.
 
 Playground previews accept shareable app/width links, for example [Signal at 390px](http://127.0.0.1:4313/fixtures/playground.html?demo=metrics&width=390#demos). The controls keep these query parameters in sync; unknown values fall back to the authored defaults. This is an iframe layout preview, not mobile-device qualification.
 
-Source organization: `src/bare.css` is the ordered CSS entry; `src/styles/` groups foundations, layouts, and component families. Base rules and later state rules stay separate to preserve cascade order. `src/ui.js` mounts the focused modules in `src/interactions/`. Each app lives in `fixtures/demos/<name>/{index.html,styles.css,app.js}`. The playground shell and behavior live in `fixtures/playground/`, with individual HTML specimens in `specimens/`. Edit those sources, then run `bun run build`; the build assembles the ignored `fixtures/*.html` pages at their existing URLs. Package consumers still receive bundled CSS and one optional ESM interaction entry. This organization supports focused reads and changes; model context-efficiency gains remain to be measured.
+Source organization: `src/bare.css` is the ordered CSS entry; `src/styles/` groups foundations, layouts, and component families. Base rules and later state rules stay separate to preserve cascade order. `src/` is TypeScript: `src/components.ts` defines the core elements over the focused, unexported modules in `src/interactions/`; opt-in components live in `src/components/`, and `src/components/runtime.ts` is the only module that knows the template framework. Each app lives in `fixtures/demos/<name>/{index.html,styles.css,app.js}`. The playground shell and behavior live in `fixtures/playground/`, with individual HTML specimens in `specimens/`. Edit those sources, then run `bun run build`; the build assembles the ignored `fixtures/*.html` pages at their existing URLs. Package consumers receive bundled CSS and self-contained ESM component entries with typings. This organization supports focused reads and changes; model context-efficiency gains remain to be measured.
 
 External TypeScript entrypoints use `<script type="module" src="app.ts">`. Assembly bundles local imports into a separate rendered artifact, preserves the original source, and rejects imports outside the workspace. Replay serves the rendered artifact. Inline TypeScript and package imports are not supported.
 
-Standalone matched app generation remains pending: the worker now invokes the pinned agentx CLI; verify configuration isolation and its complete bounded execution path live before qualification. Composer use is authorized through agentx, with app generation sequenced after the requested visual review. Browser verification already uses Composer through agentx. No live app-generation batch has run.
+Standalone matched comparisons remain pending. The worker uses the pinned AgentX SDK with explicit settings, Composer 2.5 and brokered OS isolation. A live creation and feature-edit pilot passed phone/desktop browser checks; this does not establish comparative design quality or total model cost. See [compact authoring](docs/llm-authoring.md) for protocol, evidence and the lab-only Pug candidate. Browser verification also runs through Composer/AgentX.
 
 The 24 briefs are provisional. Authored fixtures are implementation probes, not blind model evidence. Browser checks cover selected journeys across the authored apps, including themes, persistence, forms, command keyboard behavior, outlines, and narrow viewport emulation. The current evidence and remaining gaps are tracked in the implementation plan. A dedicated mobile-app track now requires matched iOS/Android routines flows, discovery/booking and mobile conversation, with separate native-look and actual-device gates. Actual iOS/Android, full accessibility, populated comparisons in the browser, and held-out qualification remain pending.
 
-See the [working task board](tasks.md), [implementation plan](docs/plan.md) and [experiment ledger](lab/experiments/ledger.json). The source repository is private. Public npm alpha.5 is published and installed in the [production Offscript experiment](https://blank.bodify.bod.ee/a/a-offscript-v3). See tasks.md for qualification status; source may advance to the next unpublished prerelease.
+See the [working task board](tasks.md), [implementation plan](docs/plan.md) and [experiment ledger](lab/experiments/ledger.json). The source repository is private; npm releases are public. The [production Offscript experiment](https://blank.bodify.bod.ee/a/a-offscript-v3) uses a pinned release. See tasks.md for integration and qualification status; source may advance beyond the published prerelease.
 
 Playground work: edit one specimen in `fixtures/playground/specimens/`, its focused controller in `controllers/`, or a demo’s own folder. `app.js` only assembles controllers. Code/model guidance opens beside the relevant specimen. The expanded reference-page experiment is archived in `archive/reference-2026-09-08/` and excluded from normal builds.
 
 
 [Icon explorer](http://127.0.0.1:4313/fixtures/playground.html#icons): full pinned Lucide family, semantic search, paged results, SVG preview/copy and attribution. Generated from the dev-only lucide-static package by scripts/icons.ts; no sibling checkout or CDN is required. Blank has a smaller supported host catalog: copied SVG remains portable, but host calls must use names Blank actually supplies.
 
-[Motion & delight](http://127.0.0.1:4313/fixtures/playground.html#motion): six composed motion studies plus collapsed functional feedback recipes, reduced-motion preview and contextual usage. The optional UI export includes semantic motion intents, `layout`, `sequence` and `settle`; update real state first and use motion to explain it. Dialog entry/exit/drag remains owned by the mounted overlay helper. These examples do not replace full app, device, accessibility or quality evaluation.
+[Motion & delight](http://127.0.0.1:4313/fixtures/playground.html#motion): six composed motion studies plus collapsed functional feedback recipes, reduced-motion preview and contextual usage. The components export includes semantic motion intents, `layout`, `sequence` and `settle`; update real state first and use motion to explain it. Dialog entry/exit/drag remains owned by `<b3-dialog>`/`<b3-sheet>`. These examples do not replace full app, device, accessibility or quality evaluation.
+
+Input/action groups preserve an editable area and wrap a direct `b3-button` below when space is tight; keep the input label and native tab order. Use `b3-title`/`b3-heading` for wrapping protection and `b3-definition` for responsive label/value lists. These contracts are included in the on-demand reference packs.