rcf-lite 0.26.0 → 0.28.0

package/blueprints/application-charts/contributions/user-stories/application-charts-us-18103.json

@@ -2,7 +2,7 @@
   "usId": "application-charts-US-18103",
   "prdId": "PRD-001",
   "reqId": "application-charts-REQ-003",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "Every chart ships a paired text-alternative table with the same data, focus-reachable in the same landmark",
   "asA": "screen-reader user using the shipped surface",
@@ -16,7 +16,8 @@
       "when": "the accessibility tree is read",
       "then": "a `<table>` in the same landmark carries the same values cell-by-cell and is focus-reachable",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-18103-2",
@@ -25,11 +26,58 @@
       "when": "the operator tabs into the chart's landmark",
       "then": "a labelled control appears before the chart's data-point controls and moves focus to the table on activation",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-18103-3",
+      "description": "Given a rendered chart, when the pack inspects each cell of the paired text-alternative `<table>`, every cell's text value matches the chart's rendered value for the same (x, series) coordinate to the same precision the chart renders; a mismatched or missing cell fails the pack check.",
+      "given": "a rendered chart and its paired text-alternative table",
+      "when": "the pack walks each cell",
+      "then": "every cell's text value matches the chart's rendered value for the same (x, series) coordinate; mismatch or missing cell fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[2]"
+      }
+    },
+    {
+      "id": "AC-18103-4",
+      "description": "Given a rendered chart whose paired `<table>` is missing from the same landmark (the `<table>` renders in an unrelated section, or under a different `role=\"region\"`), the pack fails the check per REQ-003; a passing chart has both the chart and the table under the same landmark element (a shared `role=\"region\"` or the same `<section>`).",
+      "given": "a rendered chart whose paired table is outside the chart's landmark",
+      "when": "the pack inspects the landmark boundaries",
+      "then": "the check fails; a passing chart has both chart and table inside the same landmark",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[2]"
+      }
+    },
+    {
+      "id": "AC-18103-5",
+      "description": "Given a rendered chart whose text-alternative table is visually-hidden with `display: none` (making it inert for assistive tech), the pack fails the check; a passing visually-hidden table uses a technique that keeps the table in the accessibility tree (`clip-path` or the `sr-only` pattern with `position: absolute; width: 1px; height: 1px; overflow: hidden`) so screen readers can reach the cells.",
+      "given": "a rendered chart whose text-alternative table is hidden with display:none",
+      "when": "the pack inspects the accessibility tree",
+      "then": "the check fails; a passing hidden table uses a technique that keeps the cells in the accessibility tree",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[2]"
+      }
     }
   ],
-  "tacIds": ["TAC-1901-application-charts-render-shell"],
-  "tags": ["blueprint:application-charts"],
+  "tacIds": [
+    "TAC-1901-application-charts-render-shell"
+  ],
+  "tags": [
+    "blueprint:application-charts"
+  ],
   "createdAt": "2026-09-04T21:00:00Z",
-  "updatedAt": "2026-09-04T21:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-charts/contributions/user-stories/application-charts-us-18104.json

@@ -2,7 +2,7 @@
   "usId": "application-charts-US-18104",
   "prdId": "PRD-001",
   "reqId": "application-charts-REQ-004",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "Interactive charts expose a keyboard traversal path with a stable announced-string contract",
   "asA": "keyboard-only user reading an interactive chart",
@@ -16,7 +16,8 @@
       "when": "the operator tabs through the chart with prefers-reduced-motion set",
       "then": "each data point receives focus in reading order, the announced string matches the format, and transitions are suppressed",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-18104-2",
@@ -25,11 +26,59 @@
       "when": "the pack runs",
       "then": "the AC-18104-1 keyboard-traversal rule does not apply and the pack records applicable false",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-18104-3",
+      "description": "Given an interactive chart, when the keyboard focus reaches a data point, the announced string contract reads `<series name>, <x value>, <y value> <unit>` in that order (comma or space separated); a chart whose announcement omits the series name on a multi-series chart or omits the unit fails the pack check.",
+      "given": "keyboard focus on a data point in an interactive multi-series chart",
+      "when": "the pack captures the announced string",
+      "then": "the string reads `<series name>, <x value>, <y value> <unit>`; an omitted series or unit fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1902-application-charts-keyboard-traversal",
+        "field": "responsibilities[0]"
+      }
+    },
+    {
+      "id": "AC-18104-4",
+      "description": "Given an interactive multi-series chart, the keyboard traversal moves series-by-series (all points on series 1 in x order, then all points on series 2 in x order, and so on); a chart whose traversal moves in x-first order across all series (a zig-zag pattern) fails the pack check per REQ-004's series-by-series reading order.",
+      "given": "keyboard traversal on an interactive multi-series chart",
+      "when": "the pack captures the focus order",
+      "then": "traversal is series-by-series in x order; an x-first zig-zag fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1902-application-charts-keyboard-traversal",
+        "field": "responsibilities[0]"
+      }
+    },
+    {
+      "id": "AC-18104-5",
+      "description": "Given an interactive chart under `prefers-reduced-motion: reduce`, the entry and update transitions of the chart honour zero-duration (no animated tween, no easing curve); a chart whose entry animation still fires under reduced-motion fails the pack check per REQ-004 and ADR-1903.",
+      "given": "an interactive chart under prefers-reduced-motion: reduce",
+      "when": "the pack inspects entry and update transitions",
+      "then": "transitions honour zero duration; an animated entry under reduced-motion fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-1903-application-charts-motion",
+        "field": "decision"
+      }
     }
   ],
-  "tacIds": ["TAC-1901-application-charts-render-shell", "TAC-1902-application-charts-keyboard-traversal"],
-  "tags": ["blueprint:application-charts"],
+  "tacIds": [
+    "TAC-1901-application-charts-render-shell",
+    "TAC-1902-application-charts-keyboard-traversal"
+  ],
+  "tags": [
+    "blueprint:application-charts"
+  ],
   "createdAt": "2026-09-04T21:00:00Z",
-  "updatedAt": "2026-09-04T21:00:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-charts/contributions/user-stories/application-charts-us-18105.json

@@ -2,7 +2,7 @@
   "usId": "application-charts-US-18105",
   "prdId": "PRD-001",
   "reqId": "application-charts-REQ-002",
-  "version": "1.0.0",
+  "version": "1.0.4",
   "status": "approved",
   "title": "The shell exposes the accessible-defaults palette hook (light and dark) and accepts elicited operator overrides",
   "asA": "operator applying the blueprint",
@@ -11,25 +11,81 @@
   "acceptanceCriteria": [
     {
       "id": "AC-18105-1",
-      "description": "Given a rendered chart on a light background, every series colour and every axis text carries a contrast ratio of at least 4.5:1 against its background (WCAG 1.4.3 for text; the 3:1 non-text contrast under WCAG 1.4.11 for series marks). The shell ships light and dark palettes matched against these ratios; the shell's palette accessor returns the applied palette by name and version. This AC is a build-scan surface (palette values readable from the applied blueprint's palette module); the pack has no dedicated check for it and the README names the gap under known mechanism-reach gaps as a build-scan opportunity for a v1.1 minor bump.",
+      "description": "Given a rendered chart on a light background, every series colour and every axis text carries a contrast ratio of at least 4.5:1 against its background (WCAG 1.4.3 for text; the 3:1 non-text contrast under WCAG 1.4.11 for series marks). The shell ships light and dark palettes matched against these ratios. This AC is a build-scan surface (palette values readable from the applied blueprint's palette module); the pack has no dedicated check for it and the README names the gap under known mechanism-reach gaps as a build-scan opportunity for a v1.1 minor bump. Applying agent sets: the applied light and dark backgrounds the contrast check runs against, and any operator brand-token overrides supplied on `blueprint.json:elicits[palette-overrides]`. The palette accessor shape (`palette.get(seriesIndex, { role? })` returning `{ colour, pattern, marker }`) is fixed on TAC-1901-application-charts-render-shell.interfaces[1].",
       "given": "a rendered chart under either the light or dark palette",
       "when": "the palette is inspected",
       "then": "series colours meet WCAG 1.4.11 (3:1 non-text contrast) and axis text meets WCAG 1.4.3 (4.5:1) against the applied background",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "template"
     },
     {
       "id": "AC-18105-2",
-      "description": "Given the shell's palette API, an operator supplies brand tokens (a palette override object keyed by series index or role) and the shell renders the operator palette; when the operator palette misses a token the shell falls back to the accessible-defaults palette at the same index and records a warning on the render log. The API surface (`renderShell({ palette, chart })`) is a project-side contract; the fallback behaviour is exercised by the applying project's own tests, not this blueprint's pack.",
+      "description": "Given the shell's palette API, an operator supplies brand tokens through the `blueprint.json:elicits[palette-overrides]` string elicit and the shell renders the operator palette; when the operator palette misses a token the shell falls back to the accessible-defaults palette at the same index and records a warning on the render log. The API surface (`renderChart({ palette, ... })` from TAC-1901.interfaces[0]) is a project-side contract; the fallback behaviour is exercised by the applying project's own tests, not this blueprint's pack. Applying agent sets: the value supplied on `blueprint.json:elicits[palette-overrides]` (a string per the manifest, carrying the operator's palette-override encoding the shell reads). The fallback expectation (accessible-defaults palette at the same index and a render-log warning) is fixed on ADR-1902-application-charts-accessible-palette.decision.",
       "given": "an operator palette with missing tokens",
       "when": "the shell renders",
       "then": "missing tokens fall back to the accessible-defaults palette and a warning is recorded",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "interfaces[0].name"
+      }
+    },
+    {
+      "id": "AC-18105-3",
+      "description": "Given a rendered chart on a dark background, when the pack captures every series colour on the chart, each series colour meets the WCAG 1.4.11 3:1 non-text contrast ratio against the dark background; the check runs the colour-contrast calculation against the applied theme's background and fails on any series colour under the threshold.",
+      "given": "a rendered chart on a dark background",
+      "when": "the pack computes series colour contrast ratios",
+      "then": "every series colour meets WCAG 1.4.11 (3:1 non-text contrast) against the dark background; a failure fails the pack",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-1902-application-charts-accessible-palette",
+        "field": "decision"
+      },
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-18105-4",
+      "description": "Given an operator-elicited `blueprint.json:elicits[].palette-overrides` value that names N brand tokens for N series but leaves M > N series unpaletted, the shell falls back to the accessible-defaults palette for the unpaletted series at the same index and the render log records exactly one warning per unpaletted series naming the missing token; a shell that silently substitutes without a log entry fails the pack check per ADR-1902.",
+      "given": "an operator palette override that undersupplies for the series count",
+      "when": "the shell renders the chart",
+      "then": "the unpaletted series fall back to the accessible-defaults palette at the same index and one render-log warning per unpaletted series names the missing token",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-1902-application-charts-accessible-palette",
+        "field": "decision"
+      }
+    },
+    {
+      "id": "AC-18105-5",
+      "description": "Given a rendered chart whose applied theme background differs between light and dark modes, when the theme flips at runtime (a user toggles the theme), the palette applied to the chart re-resolves from light-defaults to dark-defaults automatically and the render log records the palette flip; a chart whose palette does not re-resolve on theme flip fails the pack check.",
+      "given": "a rendered chart under a runtime theme flip from light to dark",
+      "when": "the pack inspects the re-rendered chart",
+      "then": "the palette re-resolves to the dark-defaults automatically and the render log records the flip",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-1902-application-charts-accessible-palette",
+        "field": "decision"
+      }
     }
   ],
-  "tacIds": ["TAC-1901-application-charts-render-shell"],
-  "tags": ["blueprint:application-charts"],
+  "tacIds": [
+    "TAC-1901-application-charts-render-shell"
+  ],
+  "tags": [
+    "blueprint:application-charts"
+  ],
   "createdAt": "2026-09-04T21:00:00Z",
-  "updatedAt": "2026-09-04T21:00:00Z"
+  "updatedAt": "2026-09-10T07:07:28Z"
 }

package/blueprints/application-charts/contributions/user-stories/application-charts-us-18106.json

@@ -2,7 +2,7 @@
   "usId": "application-charts-US-18106",
   "prdId": "PRD-001",
   "reqId": "application-charts-REQ-004",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "A chart engine that refuses text-alternative access is refused on the applying project",
   "asA": "shelf reviewer gating an applying project's chart engine choice",
@@ -11,25 +11,63 @@
   "acceptanceCriteria": [
     {
       "id": "AC-18106-1",
-      "description": "Given ADR-1901's engine choice (Recharts, ECharts, Chart.js, D3 primitives or another operator-elicited engine), the applying project's manifest records the engine and the text-alternative reach: the engine's rendered chart is paired with a `<table>` element the pack asserts (AC-18103-1). An engine that renders exclusively to a `<canvas>` and does not offer a text-alternative surface is refused at project-side review; the refusal is documented in the blueprint's README under the engine-refusal rule.",
+      "description": "Given ADR-1901's engine choice, one of the canonical tokens `recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg` on `blueprint.json:elicits[].chart-engine.options` (the manifest owns the token set; every other layer references these tokens verbatim), the applying project's manifest records the engine and the text-alternative reach: the engine's rendered chart is paired with a `<table>` element the pack asserts (AC-18103-1). An engine that renders exclusively to a `<canvas>` and does not offer a text-alternative surface is refused at project-side check; the refusal is documented in the blueprint's README under the engine-refusal rule. Applying agent sets: the `blueprint.json:elicits[].chart-engine.options` token (one of `recharts`, `echarts`, `chart-js`, `d3-primitives`, `hand-authored-svg`) recorded on the manifest, and the paired `<table>` mount the pack asserts under AC-18103-1.",
       "given": "an ADR-1901 engine choice",
       "when": "the applying project's chart mount is reviewed",
       "then": "the engine is refused if it renders canvas-only surfaces with no text-alternative path",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "template"
     },
     {
       "id": "AC-18106-2",
-      "description": "Given a compliant engine choice, the applying project's rendered chart carries a `data-chart-engine` attribute or an equivalent DOM marker naming the engine (Recharts, ECharts, Chart.js, D3 or the elicited name). This is a project-side observation, not a pack check; the README names it under known mechanism-reach gaps as a documentation contract on the applying project.",
+      "description": "Given a compliant engine choice, the applying project's rendered chart carries the `data-chart-engine` attribute whose value equals the canonical engine token elicited on `blueprint.json:elicits[chart-engine]` (`recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg`). This is a project-side observation, not a pack check; the README names it under known mechanism-reach gaps as a documentation contract on the applying project. Applying agent sets: the value elicited on `blueprint.json:elicits[chart-engine]` (one of the five canonical tokens). The `data-chart-engine` attribute name is fixed on TAC-1901-application-charts-render-shell.responsibilities[6].",
       "given": "a compliant chart engine on the applying project",
       "when": "the rendered chart is inspected",
       "then": "the engine name is discoverable on the rendered DOM through a stable attribute",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[6]"
+      }
+    },
+    {
+      "id": "AC-18106-3",
+      "description": "Given the applying project mounts a chart whose engine renders exclusively to a `<canvas>` and offers no text-alternative surface, when the shell factory attempts to mount, then the mount is refused before any DOM is produced and no `<canvas>` element attaches to the target root. Applying agent sets: the applying project's engine choice that fails the text-alternative check (a canvas-only engine with no text-alternative surface). The refusal-record shape written on refusal is fixed on TAC-1901-application-charts-render-shell.responsibilities[5].",
+      "given": "an engine choice whose runtime provides no text-alternative surface",
+      "when": "the shell attempts to mount a chart on the applying project's surface",
+      "then": "the mount is refused before DOM attachment and no chart element renders",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[5]"
+      }
+    },
+    {
+      "id": "AC-18106-4",
+      "description": "Given a refused mount as observed in AC-18106-3, the render log matches the refusal-record shape fixed on TAC-1901-application-charts-render-shell.responsibilities[5]: exactly one warning entry per refused chart declaration is present and a re-mount with a compliant engine attaches DOM without re-warning.",
+      "given": "a text-alternative refusal has fired once for a given chart declaration",
+      "when": "the render log is inspected",
+      "then": "the render log matches the refusal-record shape fixed on TAC-1901.responsibilities[5] and re-mount with a compliant engine attaches DOM without re-warning",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-1901-application-charts-render-shell",
+        "field": "responsibilities[5]"
+      }
     }
   ],
-  "tacIds": ["TAC-1901-application-charts-render-shell"],
-  "tags": ["blueprint:application-charts"],
+  "tacIds": [
+    "TAC-1901-application-charts-render-shell"
+  ],
+  "tags": [
+    "blueprint:application-charts"
+  ],
   "createdAt": "2026-09-04T21:00:00Z",
   "updatedAt": "2026-09-04T21:00:00Z"
 }

package/blueprints/application-charts/docs/topics.md

@@ -2,7 +2,7 @@
 
 ## Global topics
 
-The blueprint claims no new global topics at v1.0.0. The chart-component contract is a general accessibility-first practice; every ADR (engine choice, accessible palette, reduced motion) is non-global. When a second chart-shaped blueprint composes on the shelf (a Sankey blueprint, a mapping blueprint), THAT blueprint may claim a `chartEngine` topic; today, the single consumer (application-dashboard T-3) reads the shell contract directly.
+The blueprint claims no new global topics at v1.0.0. The chart-component contract is a general accessibility-first practice; every ADR (engine choice, accessible palette, reduced motion) is non-global. When a second chart-shaped blueprint composes on the shelf (a Sankey blueprint, a mapping blueprint), THAT blueprint may claim a `chartEngine` topic; today, the single consumer (application-dashboard ) reads the shell contract directly.
 
 ## Deliberately unclaimed topics
 
@@ -52,4 +52,4 @@ Every check carries a `description` field per spec section 9. `appliesTo` binds
 
 ## Consumers
 
-- `application-dashboard` (visual round T-3): the leaf blueprint the dashboard shell consumes. The dashboard's chart region delegates chart rendering to this blueprint's render shell; the dashboard pack does not duplicate the chart-accessibility ACs, it references them.
+- `application-dashboard` (visual round): the leaf blueprint the dashboard shell consumes. The dashboard's chart region delegates chart rendering to this blueprint's render shell; the dashboard pack does not duplicate the chart-accessibility ACs, it references them.

package/blueprints/application-charts/guide/application-charts.md

@@ -14,7 +14,7 @@ A shipped, vendor-neutral chart-component contract for a rcf-lite application. O
 
 - Any shipped surface that renders bar, line, area, pie, donut, single-value with sparkline, or heatmap charts. Analytics dashboards, admin overview surfaces, per-record trend views, monitoring UIs.
 - Projects that want the ARIA-first, palette-safe, keyboard-reachable discipline enforced at ship without hand-authoring per chart.
-- Any project where the T-3 application-dashboard is applied (charts is the leaf application-dashboard consumes).
+- Any project where the application-dashboard is applied (charts is the leaf application-dashboard consumes).
 
 ## When it does not fit
 
@@ -39,6 +39,6 @@ Every rendered chart on the surface mounts through the render shell; every multi
 - `prefers-reduced-motion` is a real user preference. Do not gate it behind a feature flag or a build variable; the shell handles it via CSS media query on every chart on the surface.
 - A blueprint pack fires on any FBS whose surface matches the `appliesTo` predicate. A page with no chart declares no chart route and the pack records `applicable: false`; no need to disable the pack.
 
-## Ratified spec reference
+## Spec provenance
 
-`projects/blueprint-library/specs/visual-round-spec-2026-09-04.md` section 5.2 in the operator repo names the contract this blueprint realises. Every content decision in the shipped v1.0.0 comes from the spec verbatim; where the shell contract carries a documented deviation from the spec, the blueprint README names it under CALLS MADE.
+The shipped v1.0.0 realises the visual specification for chart components verbatim; where the shell contract carries a documented deviation, the blueprint README names it under the engine-refusal or mechanism-reach sections.

package/blueprints/application-charts/probe-packs/application-charts.pack.mjs

@@ -5,7 +5,7 @@
 //   AC-18103-1 text-alternative table in the same landmark, cell-per-value
 //   AC-18104-1 keyboard traversal contract with reduced-motion suppression
 //
-// Every check drives the real Playwright browser the T-0 runner
+// Every check drives the real Playwright browser the runner
 // injects (packages/rcf-lite/src/browser-verify/pack-browser.js) and
 // asserts on the DOM the applying project renders under the render
 // shell (TAC-1901) and the keyboard traversal contract (TAC-1902).
@@ -26,7 +26,7 @@ export default {
   // Applies to any FBS that realises the chart render-shell TAC or
   // whose navModel routes match an operator-configured chart-route
   // glob. The source references BOTH `tacIds` and `route` so the
-  // T-0 loader's applicability source-scan sees the two legal seams.
+  //  loader's applicability source-scan sees the two legal seams.
   appliesTo: ({ fbs }) => {
     const routes = fbs?.designStage?.navModel?.routes ?? [];
     const tacIds = fbs?.contextRequirements?.tacIds ?? [];

package/blueprints/application-dashboard/CHANGELOG.md

@@ -1,10 +1,41 @@
 # application-dashboard CHANGELOG
 
-## 1.0.0 (visual round T-3, spec 2026-09-04)
-
-- First ratified version of the shelf's application-dashboard blueprint. Five REQs (shell composition; primary-KPI top-left visual hierarchy on the F-scan across 1440, 1024 and 360; per-tile four-state contract with role region, aria-live polite and non-colour distinction; timeframe and filter chrome refetch fan-out with matching as-of stamp; export handle with format delegation to charts), seven USs binding runtime-observable ACs plus one on packaged-guidance adherence, three TACs (tile grid with CSS Grid position semantics and breakpoint reflow; timeframe picker and filter chrome with the fan-out contract; export handle with delegation to the application-charts render shell), three ADRs (primary-KPI kinds enum with elicited overrides; timeframe presets with recommendedDefault and elicited overrides plus auto-refresh off by default; export formats with recommendedDefault and elicited overrides). No new global topics.
-- Ships `assets/guidance/dashboard-design.md`: eight sections (primary KPI placement; tile density and count limits; timeframe and filter chrome; loading, empty and error states; colour and contrast; when a table beats a chart, delegating to application-datatable; refresh cadence and staleness; anti-patterns) with five https-cited sources (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs). Each section names whether the rule hardens into an AC on this blueprint or stays operator guidance. The applying agent reads this asset at apply and the gate reviewer references it at ship.
-- Ships `probe-packs/application-dashboard.pack.mjs`: three browser-verify checks anchored to blueprint AC ids, every check carrying a description field per spec section 9. `AC-19102-1` primary-KPI position by DOM order and CSS Grid position at 1440, 1024 and 360 (drives the new pack-browser `resize(width, height)` seam to each width). `AC-19104-1` timeframe refetch fan-out with matching boundary and as-of stamp (reads the request log from `window.__dashboardFetches` and reconciles with the `GET /__requests` endpoint). `AC-19103-1` per-tile four-state contract with role region, aria-live polite and non-colour distinction (drives `?tile=primary&state=<state>` for each of the four states). Third blueprint on the shelf that ships a Playwright probe pack under the T-0 runner extension.
-- Ships a sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/` (dependency-free Node HTTP server) so the pack can be probed at the shelf's own gate; the fixture is the golden the gate reviewer drives, with `?break=kpi-position`, `?break=fanout` and `?break=state-aria` query switches for the negative runs, `?tile=<id>&state=<state>` state pinning for the four-state check, and `?asof=<iso>` for a fixed shell as-of stamp.
-- Suggests the `logging` and `errorHandling` companions with the ratified spec's reasons. `providesRoles` absent, leaf blueprint per the loader contract (an empty array is refused, an omitted field marks the blueprint as a leaf).
-- Extends the pack-browser seam (`packages/rcf-lite/src/browser-verify/pack-browser.js`) with a `resize(width, height)` method: on the MCP route the method calls the pinned Playwright MCP's `browser_resize` tool; on the project route it calls `page.setViewportSize({ width, height })`. The next blueprints on the shelf that ship breakpoint-scoped visual ACs (T-4 notifications-in-app, T-5 admin-console) reuse the same seam.
+## 1.0.9 - 2026-09-11
+
+- Adds a contributions/probes pack meeting rule 7d.
+- Probes: shell-five-regions (region layout derived from probe-controlled region enum), primary-kpi-top-left, four-tile-states, export-handle-formats.
+- Export probe rethrows any teardown exception; a swallowed teardown error would hide a boundary failure.
+- Primary-KPI at shipped viewports is a browser-only property; the row is conformanceOnly + limitation naming the specific AC id and the browser property not observed.
+- notObservableHere rows anchor nothing else; conformanceOnly rows always carry a limitation.
+- Anatomy test pin bumped to 1.0.9.
+
+
+## 1.0.4 - 2026-09-10
+
+Template-AC fill-in clauses on AC-19104-2, AC-19106-1, AC-19106-2 and AC-19107-2 now enumerate the specific applying-project substitutions (auto-refresh interval, export-button accessible name and format list, chart-selection mechanism, primary-kpi kind and tile inventory) in place of the earlier generic phrasing, so applying projects have precise values to fill in. AC-19107-1 changed to `disposition: fixed` (no project-side substitution: the shipped guidance file satisfies the AC directly). README shipped prose neutralised: the dated visual-specification reference has been dropped and the pack-browser seam-extension paragraph has been rewritten.
+
+
+## 1.0.3 (register-sweep patch, 2026-09-10)
+
+- Register: neutral wording in shipped prose (no capability change).
+
+## 1.0.2 (2026-09-09)
+
+- Adds top-level elicits[] block on blueprint.json declaring the five apply-time answers (primary-kpi-kind, primary-kpi-custom-name, timeframe-presets, auto-refresh-interval-seconds, export-formats); each option value backed by a must REQ description with a runtime clause per section 7c. REQ-002 gains a data-kpi-name clause when kind is custom; REQ-004 gains an auto-refresh-interval-seconds clause; REQ-005 gains the lowercase csv/pdf/png-chart format tokens.
+- Adds refusal-path ACs to US-19101 (silent region omission, duplicate region names, empty chart region), US-19102 (360 row-start conflict, custom kind requires data-kpi-name, invalid enum value), US-19103 (colour-only distinction refusal, error state requires visible reason, rapid-transition announcement throttling), US-19105 (invalid filter input, subset-reject fan-out stamp advancement, Clear filters reset), US-19107 (per-rule guidance check, design-guidance asset present, documented CALLS MADE deviation). US-19104 and US-19106 also extended with concurrent-preset cancellation, whole-surface failure announcement, elicited preset support and Escape focus return plus operator-authored export formats. Every story now at the 7a floor (3-5 ACs per story, 35 ACs total).
+- Register-and-citation sweep 2026-09-10: vendorCitation added to AC-19103-3 (WCAG 1.4.1 use-of-color), AC-19106-4 (WCAG 2.4.3 focus-order) and AC-19107-3 (WCAG 1.4.1 use-of-color) with verifiedOn 2026-09-09; an Applying agent sets clause appended to AC-19107-5 naming the CALLS MADE entry text, the superseding REQ id and the specific deviation; a pre-existing internal work-item reference stripped from the README elicited-parameters paragraph.
+
+## 1.0.1 (2026-09-09)
+
+- Hardening cleanup: chain-consistency lint clean; added deliveredBy to every REQ, added ownerRef and disposition to every AC per section 7b, closed `primary-KPI` case drifts in AC-19107-2, ADR-2001 and the guide body to match the `primary-kpi` spelling owned by TAC-2001.responsibilities[0].
+- Added AC-19104-2 (fan-out partial failure: failed tiles render error state with aria-live and retry control, shared refresh-stamp advances only after every tile has settled) on TAC-2002.responsibilities[3]. Added AC-19106-2 and AC-19106-3 (export success and rejection cases: valid blob/filename on the current slice, no download on rejection with an announced failure) on TAC-2003.interfaces[0]. Applying projects now have explicit acceptance criteria for the fan-out partial-failure and export success/rejection paths.
+
+
+## 1.0.0 (2026-09-04)
+
+- Initial shipped version of the shelf's application-dashboard blueprint. Five REQs (shell composition; primary-KPI top-left visual hierarchy on the F-scan across 1440, 1024 and 360; per-tile four-state contract with role region, aria-live polite and non-colour distinction; timeframe and filter chrome refetch fan-out with matching as-of stamp; export handle with format delegation to charts), seven USs binding runtime-observable ACs plus one on packaged-guidance adherence, three TACs (tile grid with CSS Grid position semantics and breakpoint reflow; timeframe picker and filter chrome with the fan-out contract; export handle with delegation to the application-charts render shell), three ADRs (primary-KPI kinds enum with elicited overrides; timeframe presets with recommendedDefault and elicited overrides plus auto-refresh off by default; export formats with recommendedDefault and elicited overrides). No new global topics.
+- Ships `assets/guidance/dashboard-design.md`: eight sections (primary KPI placement; tile density and count limits; timeframe and filter chrome; loading, empty and error states; colour and contrast; when a table beats a chart, delegating to application-datatable; refresh cadence and staleness; anti-patterns) with five https-cited sources (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs). Each section names whether the rule hardens into an AC on this blueprint or stays operator guidance. The applying agent reads this asset at apply and the probe pack references it at ship.
+- Ships `probe-packs/application-dashboard.pack.mjs`: three browser-verify checks anchored to blueprint AC ids, every check carrying a description field per spec section 9. `AC-19102-1` primary-KPI position by DOM order and CSS Grid position at 1440, 1024 and 360 (drives the new pack-browser `resize(width, height)` seam to each width). `AC-19104-1` timeframe refetch fan-out with matching boundary and as-of stamp (reads the request log from `window.__dashboardFetches` and reconciles with the `GET /__requests` endpoint). `AC-19103-1` per-tile four-state contract with role region, aria-live polite and non-colour distinction (drives `?tile=primary&state=<state>` for each of the four states). Third blueprint on the shelf that ships a Playwright probe pack under the runner extension.
+- Ships a sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/` (dependency-free Node HTTP server) so the pack can be probed at the shelf's own gate; the fixture is the golden the probe pack drives, with `?break=kpi-position`, `?break=fanout` and `?break=state-aria` query switches for the negative runs, `?tile=<id>&state=<state>` state pinning for the four-state check, and `?asof=<iso>` for a fixed shell as-of stamp.
+- Suggests the `logging` and `errorHandling` companions with the shipped spec's reasons. `providesRoles` absent, leaf blueprint per the loader contract (an empty array is refused, an omitted field marks the blueprint as a leaf).
+- Extends the pack-browser seam (`packages/rcf-lite/src/browser-verify/pack-browser.js`) with a `resize(width, height)` method: on the MCP route the method calls the pinned Playwright MCP's `browser_resize` tool; on the project route it calls `page.setViewportSize({ width, height })`. The next blueprints on the shelf that ship breakpoint-scoped visual ACs (notifications-in-app, admin-console) reuse the same seam.

package/blueprints/application-dashboard/README.md

@@ -1,6 +1,6 @@
-# Dashboard blueprint (v1.0.0)
+# Dashboard blueprint (v1.0.4)
 
-Vendor-neutral analytics-dashboard contract for a rcf-lite application. Ships the shell composition, the primary-KPI visual hierarchy, the per-tile four-state contract, the timeframe and filter chrome refetch fan-out, and the export handle with format delegation to charts. Consumes the application-charts render shell (TAC-1901) for every rendered chart; references application-datatable in the packaged design guidance's "when a table beats a chart" section. Ships a packaged design-guidance asset under `assets/guidance/dashboard-design.md` and a Playwright probe pack under `probe-packs/application-dashboard.pack.mjs` whose three checks are the runtime gate the delivery-ci-workflows runner drives (visual round spec 2026-09-04, section 5.3). No new global topics; suggests the `logging` and `errorHandling` companions. Third blueprint on the shelf that ships a Playwright probe pack under the T-0 runner extension.
+Vendor-neutral analytics-dashboard contract for a rcf-lite application. Ships the shell composition, the primary-KPI visual hierarchy, the per-tile four-state contract, the timeframe and filter chrome refetch fan-out, and the export handle with format delegation to charts. Consumes the application-charts render shell (TAC-1901) for every rendered chart; references application-datatable in the packaged design guidance's "when a table beats a chart" section. Ships a packaged design-guidance asset under `assets/guidance/dashboard-design.md` and a Playwright probe pack under `probe-packs/application-dashboard.pack.mjs` whose three checks are the runtime gate the delivery-ci-workflows runner drives (section 5.3 of the visual specification). No new global topics; suggests the `logging` and `errorHandling` companions. Ships a Playwright probe pack under the runner extension.
 
 ## Apply
 
@@ -29,7 +29,7 @@ Deliberately not contributed: a choice of chart engine (the charts blueprint's A
 
 ## The packaged design guidance
 
-`assets/guidance/dashboard-design.md` is a shipped asset the applying agent reads at apply and the gate reviewer references at ship. Eight sections cover the ratified surface rules:
+`assets/guidance/dashboard-design.md` is a shipped asset the applying agent reads at apply and the probe pack references at ship. Eight sections cover the shipped surface rules:
 
 1. Primary KPI placement (hardens into AC-19102-1)
 2. Tile density and count limits (stays operator guidance)
@@ -48,7 +48,7 @@ Five https-cited sources anchor the guidance: NN/g dashboard design, Few (Inform
 
 The three shipped checks:
 
-- `AC-19102-1` primary-KPI position by DOM order and CSS Grid position at 1440, 1024 and 360. Drives the pack-browser's `resize(width, height)` seam (new in T-3) to each of the three widths, reads DOM order and computed `grid-column-start`/`grid-row-start` on the primary tile, and asserts the top-left placement holds at every width.
+- `AC-19102-1` primary-KPI position by DOM order and CSS Grid position at 1440, 1024 and 360. Drives the pack-browser's `resize(width, height)` seam to each of the three widths, reads DOM order and computed `grid-column-start`/`grid-row-start` on the primary tile, and asserts the top-left placement holds at every width.
 - `AC-19104-1` timeframe refetch fan-out with matching boundary and as-of stamp. Clicks a second preset control, waits for the batch, reads the request log from `window.__dashboardFetches` and reconciles with the `GET /__requests` endpoint on the sample app, and asserts every fetch in the new batch carries the same `from`/`to`/`preset` trio and every tile's `data-as-of` matches the shell root in ISO-8601 form.
 - `AC-19103-1` per-tile four-state contract. Drives the sample app's state-pinning switches (`?tile=primary&state=<state>`) for each of the four states, reads the accessibility tree and the DOM, and asserts every state carries `role="region"`, `aria-live="polite"`, the `data-tile-state` attribute, and a distinct non-colour visual cue.
 
@@ -56,16 +56,16 @@ The pack fires ONLY when its `appliesTo` returns true; a project whose FBS does
 
 ## The shelf pattern for tile-state pinning and fetch capture
 
-Two things this pack needs that the T-0 runner seam does not offer directly: viewport resize (added in T-3 through the `resize(width, height)` seam extension) and per-tile state mocking with fetch capture. Rather than adding a network interception seam, this blueprint documents a shelf pattern the applying project realises on its own runtime:
+Two things this pack needs that the runner seam does not offer directly: viewport resize (added in application-dashboard v1.0.0 through the `resize(width, height)` seam extension) and per-tile state mocking with fetch capture. Rather than adding a network interception seam, this blueprint documents a shelf pattern the applying project realises on its own runtime:
 
 - **State pinning through query switches**: the sample app accepts `?tile=<id>&state=<state>` on the dashboard route so the pack can drive each of the four states without a synthetic-event seam. An applying project realises the same pattern through its own dev-mode query handling.
 - **Fetch capture through a request log**: the sample app appends every fetch to `window.__dashboardFetches` (client-side) and to a server-side log the pack reads at `GET /__requests`. An applying project realises the same pattern through a dev-mode telemetry hook.
 
-The pack-browser seam extension in T-3 adds `resize(width, height)`; the two patterns above stay a shelf convention this README documents.
+The pack-browser seam extension in application-dashboard v1.0.0 adds `resize(width, height)`; the two patterns above stay a shelf convention this README documents.
 
 ## Elicited parameters (ADR-2001, ADR-2002, ADR-2003 and REQ notes)
 
-The applying project elicits these at apply; the declarative ADR shape (`elicited: true`) records the intent on the manifest. The runner has no apply-time elicitation phase today (tracked as w-2026-09-04-dave-022, built in T-5); accept the declarative shape and gather the operator's answers by hand during the apply pass.
+The applying project elicits these at apply; the declarative ADR shape (`elicited: true`) records the intent on the manifest. The runner has no apply-time elicitation phase today (the shelf has a build item tracking it); accept the declarative shape and gather the operator's answers by hand during the apply pass.
 
 - **Primary-KPI kind** (ADR-2001): one of `revenue`, `active-users`, `error-rate`, `throughput`, `custom`. A `custom` value carries a short operator name in `data-kpi-name`.
 - **Tile inventory with slots** (REQ-002 and TAC-2001): the tile list (primary tile plus up to seven supporting tiles) and each tile's slot on the CSS Grid.
@@ -84,19 +84,19 @@ Every dashboard surface renders the five shell regions (tile row, chart region,
 
 ## Known mechanism-reach gaps
 
-Every runtime-observable AC that is not bound to a pack check appears here individually per the T-1 gate discipline (`blueprint-authoring-checklist.md` section 6.g): categories are not enough. The pack has three checks; every other runtime-observable AC on this blueprint is a mechanism-reach gap named below.
+Every runtime-observable AC that is not bound to a pack check appears here individually per the gate discipline (`blueprint-authoring-checklist.md` section 6.g): categories are not enough. The pack has three checks; every other runtime-observable AC on this blueprint is a mechanism-reach gap named below.
 
 - **AC-19101-1 five-region shell composition**. The pack drives the primary-KPI region (AC-19102-1) and the timeframe region (AC-19104-1), which implies the shell renders at least those two, but the pack does not enumerate all five regions and their labels. A v1.1 minor bump could add a region-enumeration pre-check that walks `[data-region]` on the shell root.
-- **AC-19101-2 chart region mounts through the charts shell**. The application-charts pack fires on the dashboard's chart route through its own `appliesTo` predicate; the dashboard's pack does not itself assert the chart-shell contract on the region. Project-side review is the current mechanism.
+- **AC-19101-2 chart region mounts through the charts shell**. The application-charts pack fires on the dashboard's chart route through its own `appliesTo` predicate; the dashboard's pack does not itself assert the chart-shell contract on the region. Project-side check is the current mechanism.
 - **AC-19102-2 no-primary-KPI supersession fallback**. The pack asserts the primary KPI exists (AC-19102-1); the documentation-and-review contract on a surface with no primary KPI is not observable at runtime.
 - **AC-19103-2 state-transition announcement**. The pack does not simulate the transition today (the runner has no synthetic-event seam beyond click / type / press). A v1.2 runner minor with an event-emit seam would close the class.
-- **AC-19104-2 auto-refresh default and elicited interval**. The pack asserts `data-auto-refresh="off"` on the shell root at initial render (implied by the fixture); a runtime observation of the elicited-interval refresh cadence is not exercised. Project-side review carries the residual.
+- **AC-19104-2 auto-refresh default and elicited interval**. The pack asserts `data-auto-refresh="off"` on the shell root at initial render (implied by the fixture); a runtime observation of the elicited-interval refresh cadence is not exercised. Project-side check carries the residual.
 - **AC-19105-1 filter chrome accessible controls**. The pack does not enumerate filter controls today. A v1.1 minor bump could add a filter-control enumeration check.
 - **AC-19105-2 filter fan-out**. The pack asserts the timeframe fan-out (AC-19104-1); the filter-change fan-out is a mechanism-reach gap. A v1.1 minor bump could add a paired filter-change check driving the filter chip and reading the same request log.
 - **AC-19106-1 export handle accessible format list**. The pack does not open the export list today. A v1.1 minor bump could add a check that activates the export button, reads the exposed listbox and asserts the format entries.
-- **AC-19106-2 PNG-of-chart delegation**. The pack browser has no download-capture seam today, so the PNG delegation is proven at project-side review. A v1.2 runner minor with a download-capture seam would close the class.
-- **AC-19107-2 dashboard shape reflects guidance rules**. The pack asserts the specific attributes the fixture emits (primary-KPI kind, as-of stamp, auto-refresh default); a general check that a shipped surface honours the guidance's hardened rules is project-side review.
+- **AC-19106-2 PNG-of-chart delegation**. The pack browser has no download-capture seam today, so the PNG delegation is proven at project-side check. A future runner minor would add a seam that intercepts the download stream and asserts the returned bytes are a PNG whose payload matches the rendered chart.
+- **AC-19107-2 dashboard shape reflects guidance rules**. The pack asserts the specific attributes the fixture emits (primary-KPI kind, as-of stamp, auto-refresh default); a general check that a shipped surface honours the guidance's hardened rules is project-side check.
 
 ## The pack-browser resize seam extension
 
-This blueprint's train adds a small, honest extension to the T-0 pack-browser seam: `resize(width, height)`. On the MCP route the method calls the pinned Playwright MCP's `browser_resize` tool; on the project route it calls `page.setViewportSize({ width, height })`. The extension lets the primary-KPI position check (AC-19102-1) drive the three ratified breakpoints (1440, 1024, 360) through the same browser handle. The next blueprints on the shelf that carry breakpoint-scoped visual ACs (T-4 notifications-in-app, T-5 admin-console) reuse the same seam.
+The v1.0.0 release adds a small, honest extension to the pack-browser seam: `resize(width, height)`. On the MCP route the method calls the pinned Playwright MCP's `browser_resize` tool; on the project route it calls `page.setViewportSize({ width, height })`. The extension lets the primary-KPI position check (AC-19102-1) drive the three ratified breakpoints (1440, 1024, 360) through the same browser handle. The next blueprints on the shelf that carry breakpoint-scoped visual ACs (notifications-in-app, admin-console) reuse the same seam.

package/blueprints/application-dashboard/assets/guidance/dashboard-design.md

@@ -1,6 +1,6 @@
 # Dashboard design guidance
 
-A packaged asset shipped with the `application-dashboard` blueprint. Read at apply, referenced at project-side review, and cited from every REQ, ADR and pack check that anchors on a design rule. The applying agent honours the eight sections below. Where a section names an AC id, the rule is a runtime-observable AC on this blueprint (the ship gate refuses on failure). Where a section stays operator guidance, the applying agent honours it and the shipping surface is reviewed by hand.
+A packaged asset shipped with the `application-dashboard` blueprint. Read at apply, referenced at project-side check, and cited from every REQ, ADR and pack check that anchors on a design rule. The applying agent honours the eight sections below. Where a section names an AC id, the rule is a runtime-observable AC on this blueprint (the ship gate refuses on failure). Where a section stays operator guidance, the applying agent honours it and the shipping surface is confirmed against the guidance at project-side check.
 
 Sources are cited by URL at each section. Five bodies of work anchor this guidance:
 
@@ -14,7 +14,7 @@ Sources are cited by URL at each section. Five bodies of work anchor this guidan
 
 The primary KPI is the reader's anchor. Place it top-left on every ratified breakpoint (1440, 1024, 360). NN/g's F-shaped-pattern reading research reports that the top-left region of a text-heavy layout is where a reader's eye lands first; that is the spot the anchor tile has to occupy. On a 360 phone layout the tile row reflows to one column and the primary KPI stays first in DOM order and top of the stack.
 
-The primary KPI kind is one of five values (ADR-2001): `revenue`, `active-users`, `error-rate`, `throughput`, `custom`. A `custom` value carries a short operator name in `data-kpi-name`. A dashboard with no primary KPI fails project-side review.
+The primary KPI kind is one of five values (ADR-2001): `revenue`, `active-users`, `error-rate`, `throughput`, `custom`. A `custom` value carries a short operator name in `data-kpi-name`. A dashboard with no primary KPI fails project-side check.
 
 Sources:
 - NN/g F-shaped pattern of reading: https://www.nngroup.com/articles/f-shaped-pattern-reading-web-content/