@livx.cc/bare-v3 0.1.0-alpha.113 → 0.1.0-alpha.115

package/README.md

@@ -13,7 +13,7 @@ bun lab compare     # comparison UI on localhost:4314
 bun lab replay <run-id> # verifies saved app hashes, then serves its isolated preview
 ```
 
-The comparison UI needs the fixture server for example links. Model outputs replay on separate local origins. Replay refuses missing or mismatched artifact hashes. `bun lab verify-evidence evidence.json protocol.json` checks recorded measurements against the protocol viewport and verifies the referenced PNG file, size, and hash. For matched captures, declare `viewport.expectedPresentation` with `theme`, `rootFontSize` and `direction`; the browser probe records these values and missing or mismatched values fail validation. The theme measurement uses the explicit bare-v3 root attribute; other strategy adapters must map their own theme mechanism rather than guess. The probe also records `emptyActions`: buttons/links without visible text or a graphic candidate require review even when they have an accessible name. Fresh evidence must include this measurement; keep older captures unchanged. CSS-drawn affordances need adjudication, and a graphic candidate does not prove visible pixels or adequate contrast. It does not judge visual quality or declare release qualification. Run artifacts and judgments live under ignored `artifacts/`; retain that directory when sharing evidence. Browser/model tooling is development-only and excluded from the packed consumer.
+The comparison UI needs the fixture server for example links. Model outputs replay on separate local origins. Replay refuses missing or mismatched artifact hashes at startup and rechecks each served file against the recorded snapshot. Changed files return 409; unrecorded files are not served. Response headers `X-Bare-Artifact-Sha256` and `X-Bare-File-Sha256` identify the snapshot and exact served bytes without exposing run/strategy names. Run `bun scripts/capture-replay.ts <run-root> <run-id> <new-output-dir> [width height]` through the authorized browser driver to capture these network receipts, diagnostics and screenshot together. The output directory must be new and outside the original run. This initial-load capture leaves task/persistence unverified and does not certify later lazy-loaded resources; repair preparation must still validate the recorded binding against its intended parent. DOM content alone does not establish this binding. `bun lab verify-evidence evidence.json protocol.json` checks recorded measurements against the protocol viewport and verifies the referenced PNG file, size, and hash. For matched captures, declare `viewport.expectedPresentation` with `theme`, `rootFontSize` and `direction`; the browser probe records these values and missing or mismatched values fail validation. The theme measurement uses the explicit bare-v3 root attribute; other strategy adapters must map their own theme mechanism rather than guess. The probe also records `emptyActions`: buttons/links without visible text or a graphic candidate require review even when they have an accessible name. Fresh evidence must include this measurement; keep older captures unchanged. CSS-drawn affordances need adjudication, and a graphic candidate does not prove visible pixels or adequate contrast. Use `bun lab feedback evidence.json protocol.json` to emit a compact repair report with evidence/protocol fingerprints, screenshot verification and bounded findings. Like verification, it exits nonzero for unresolved findings or missing evidence; redirect stdout to retain the report. This is review-only and offline: it does not establish which app revision was captured, mutate artifacts, qualify the app, or start a paid edit run. For replay captures, append `--parent-run <run-directory>` to feedback or verify-evidence. This checks recorded document/resource receipts against the current parent files and manifest. It establishes consistency, not authenticity of an independently edited evidence file, and does not qualify the task. It does not judge visual quality or declare release qualification. Run artifacts and judgments live under ignored `artifacts/`; retain that directory when sharing evidence. Browser/model tooling is development-only and excluded from the packed consumer.
 
 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`.
 

package/dist/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.0-alpha.113",
+  "version": "0.1.0-alpha.115",
   "cssSha256": "706663ecb2662ba13acab825643e939c4100b76db1dc72ecd52f2ec079acef90",
   "classes": [
     "b3-accordion",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@livx.cc/bare-v3",
-  "version": "0.1.0-alpha.113",
+  "version": "0.1.0-alpha.115",
   "type": "module",
   "thirdPartyNotices": "./dist/third-party.json",
   "files": [