rcf-lite 0.26.0 → 0.28.0

package/blueprints/application-dashboard/contributions/probes/shell-five-regions.mjs

@@ -0,0 +1,93 @@
+// shell-five-regions probe for application-dashboard v1.0.9.
+//
+// AC-19101-1: the DOM carries five labelled role="region" elements.
+// The fixture accepts a startServer({ regions: [...] }) override, so
+// the probe DRIVES two distinct region sets and asserts the
+// rendered DOM follows each input (derived, not
+// fixed inventory).
+//
+// anchorAcId: application-dashboard-AC-19101-1.
+
+import { startFixture, evidenceFromResponse } from './probe-utils.mjs';
+
+const FULL_SET = ['tile-row', 'chart-region', 'filter-chrome', 'timeframe-picker', 'export-handle'];
+const REDUCED_SET = ['tile-row', 'timeframe-picker', 'export-handle'];
+
+function scrapeRegions(body) {
+ const sectionRe = /<section\b([^>]*)>/g;
+ const regions = [];
+ let match;
+ while ((match = sectionRe.exec(body)) !== null) {
+ const attrs = match[1];
+ if (!/role="region"/.test(attrs)) continue;
+ const labelMatch = attrs.match(/aria-label="([^"]+)"/);
+ const dataRegionMatch = attrs.match(/data-region="([^"]+)"/);
+ regions.push({
+ ariaLabel: labelMatch ? labelMatch[1] : null,
+ dataRegion: dataRegionMatch ? dataRegionMatch[1] : null,
+ });
+ }
+ return regions;
+}
+
+async function driveOne(startServer, regionsInput, expected) {
+ const fixture = await new Promise((resolve, reject) => {
+ startServer({ port: 0, regions: regionsInput }).then((started) => {
+ resolve({ server: started.server, port: started.port, baseUrl: `http://127.0.0.1:${started.port}`, close: () => new Promise((r, rj) => started.server.close((e) => (e ? rj(e) : r()))) });
+ }).catch(reject);
+ });
+ try {
+ const res = await fetch(`${fixture.baseUrl}/`);
+ const body = await res.text();
+ const regions = scrapeRegions(body);
+ const dataRegionsFound = regions.map((r) => r.dataRegion).filter(Boolean);
+ // Only count REAL known-content regions (skip shell-root wrapper if present).
+ const contentRegions = dataRegionsFound.filter((r) => r !== 'shell-root');
+ const matchesInput = contentRegions.length === expected.length
+ && expected.every((r) => contentRegions.includes(r))
+ && contentRegions.every((r) => expected.includes(r));
+ return { res, body, regions, dataRegionsFound, contentRegions, matchesInput, fixture };
+ } finally {
+ await fixture.close();
+ }
+}
+
+export const anchorReqId = 'application-dashboard-REQ-001';
+export const accountBound = false;
+
+export default async function runProbe() {
+ const { startServer } = await import('../../../../packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js');
+
+ const results = [];
+ const runFull = await driveOne(startServer, FULL_SET, FULL_SET);
+ const runReduced = await driveOne(startServer, REDUCED_SET, REDUCED_SET);
+ const derivedFromInput = runFull.matchesInput && runReduced.matchesInput
+ && JSON.stringify(runFull.contentRegions) !== JSON.stringify(runReduced.contentRegions);
+ const labelsUniqueFull = new Set(runFull.regions.map((r) => r.ariaLabel).filter(Boolean)).size === runFull.regions.length;
+ const allLabelledFull = runFull.regions.every((r) => typeof r.ariaLabel === 'string' && r.ariaLabel.length > 0);
+ const pass = runFull.res.status === 200 && runReduced.res.status === 200
+ && derivedFromInput && labelsUniqueFull && allLabelledFull && runFull.contentRegions.length === 5;
+
+ results.push({
+ anchorAcId: 'application-dashboard-AC-19101-1',
+ verdict: pass ? 'pass' : 'fail',
+ detail: `Given a rendered dashboard surface, the DOM carries - drove two distinct region sets: full=[${runFull.contentRegions.join(',')}] reduced=[${runReduced.contentRegions.join(',')}]; regions follow the input (${derivedFromInput}); five labels unique in the full run (${labelsUniqueFull})`,
+ evidence: evidenceFromResponse({
+ route: '/',
+ response: runFull.res,
+ bodyText: runFull.body,
+ extraFields: {
+ input: { runFull: FULL_SET, runReduced: REDUCED_SET },
+ derived: {
+ fullContentRegions: runFull.contentRegions,
+ reducedContentRegions: runReduced.contentRegions,
+ derivedFromInput,
+ fullLabelsUnique: labelsUniqueFull,
+ fullAllLabelled: allLabelledFull,
+ },
+ altBodyExcerpt: runReduced.body.slice(0, 240),
+ },
+ }),
+ });
+ return { results };
+}

package/blueprints/application-dashboard/contributions/requirements/application-dashboard-req-001.json

@@ -7,9 +7,16 @@
   "domain": "application",
   "priority": "must",
   "rationale": "A dashboard is a compound surface: the tile row, the chart region and the filter chrome each need their own AC coverage. Naming the five regions on the shell is what lets every subsequent REQ, TAC and pack check anchor onto a stable, inspectable structure rather than a floating layout convention.",
-  "tags": ["blueprint:application-dashboard", "category:01-shell-composition"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-dashboard",
+    "category:01-shell-composition"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-04T22:10:00Z",
+  "deliveredBy": {
+    "tacId": "TAC-2001-application-dashboard-tile-grid",
+    "field": "responsibilities"
+  }
 }

package/blueprints/application-dashboard/contributions/requirements/application-dashboard-req-002.json

@@ -2,14 +2,21 @@
   "reqId": "application-dashboard-REQ-002",
   "prdId": "PRD-001",
   "title": "The primary KPI tile sits top-left in DOM order and in CSS Grid position across the ratified breakpoints",
-  "description": "The tile row's primary KPI carries a top-left placement the reader reaches first, on the NN/g F-scan of the surface, at every ratified breakpoint (1440, 1024, 360). At 1440 and 1024 the primary KPI is the first tile in DOM order and its computed CSS Grid column-start is 1 and row-start is 1; at 360 the tile row reflows to one column and the primary KPI is the first tile in DOM order and its row-start is 1. The tile carries a `data-tile-role=\"primary-kpi\"` attribute and a `data-kpi-kind` attribute whose value is one of the ADR-2001 enum values (revenue, active-users, error-rate, throughput, custom). A dashboard that ships no primary KPI tile fails this REQ at project-side review; a dashboard whose primary KPI is not top-left at any of the three breakpoints fails the pack check AC-19102-1.",
+  "description": "The tile row's primary KPI carries a top-left placement the reader reaches first, on the NN/g F-scan of the surface, at every shipped breakpoint (1440, 1024, 360). At 1440 and 1024 the primary KPI is the first tile in DOM order and its computed CSS Grid column-start is 1 and row-start is 1; at 360 the tile row reflows to one column and the primary KPI is the first tile in DOM order and its row-start is 1. The tile carries a `data-tile-role=\"primary-kpi\"` attribute and a `data-kpi-kind` attribute whose value is one of the ADR-2001 enum values (revenue, active-users, error-rate, throughput, custom). A dashboard that ships no primary KPI tile fails this REQ at project-side check; a dashboard whose primary KPI is not top-left at any of the three breakpoints fails the pack check AC-19102-1. When the elicited `primary-kpi-kind` is `custom` the tile also carries a `data-kpi-name` attribute whose value is the operator-elicited `primary-kpi-custom-name` short name.",
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "The primary KPI is the reader's anchor on a dashboard glance; the F-scan reading pattern (NN/g dashboard design research) puts the top-left tile at the reader's first fixation. Codifying the placement as a runtime-observable CSS Grid position at the three ratified breakpoints turns a design convention into a check a Playwright probe can drive.",
-  "tags": ["blueprint:application-dashboard", "category:02-primary-kpi-hierarchy"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-dashboard",
+    "category:02-primary-kpi-hierarchy"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z",
+  "deliveredBy": {
+    "tacId": "TAC-2001-application-dashboard-tile-grid",
+    "field": "responsibilities"
+  }
 }

package/blueprints/application-dashboard/contributions/requirements/application-dashboard-req-003.json

@@ -2,14 +2,21 @@
   "reqId": "application-dashboard-REQ-003",
   "prdId": "PRD-001",
   "title": "Every tile honours a four-state contract with distinct visuals, role region, aria-live polite, and non-colour distinction",
-  "description": "Every tile on the shell renders one of four states at any moment: loading, empty, error, populated. Each state carries a distinct visual (a skeleton stripe or spinner for loading, a labelled empty-state block for empty, a labelled error block with the recorded reason for error, and the actual metric for populated). Each tile wraps its content in `role=\"region\"` with an `aria-live=\"polite\"` announcer that reads the state transition on change. The state distinction combines a visual cue and a text label (non-colour distinction, WCAG 1.4.1): the state's visual is not colour-only, and the state's accessible name reads `<tile title>, <state>` on entry. A tile that renders no visible state (a blank tile) fails REQ-003 at project-side review; a tile that carries state-only through colour fails the pack check AC-19103-1.",
+  "description": "Every tile on the shell renders one of four states at any moment: loading, empty, error, populated. Each state carries a distinct visual (a skeleton stripe or spinner for loading, a labelled empty-state block for empty, a labelled error block with the recorded reason for error, and the actual metric for populated). Each tile wraps its content in `role=\"region\"` with an `aria-live=\"polite\"` announcer that reads the state transition on change. The state distinction combines a visual cue and a text label (non-colour distinction, WCAG 1.4.1): the state's visual is not colour-only, and the state's accessible name reads `<tile title>, <state>` on entry. A tile that renders no visible state (a blank tile) fails REQ-003 at project-side check; a tile that carries state-only through colour fails the pack check AC-19103-1.",
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "The four-state contract is the shelf's most-repeated data-region pattern (see application-datatable REQ-005 for the same shape on the table shell); giving the dashboard tile its own explicit ACs is what stops the state contract from silently drifting between the two surfaces. The aria-live announcer is what makes a tile's state change reachable to a screen-reader user; the non-colour distinction is what makes the state legible to a colour-blind reader.",
-  "tags": ["blueprint:application-dashboard", "category:03-tile-four-state"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-dashboard",
+    "category:03-tile-four-state"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-04T22:10:00Z",
+  "deliveredBy": {
+    "tacId": "TAC-2001-application-dashboard-tile-grid",
+    "field": "responsibilities"
+  }
 }

package/blueprints/application-dashboard/contributions/requirements/application-dashboard-req-004.json

@@ -2,14 +2,21 @@
   "reqId": "application-dashboard-REQ-004",
   "prdId": "PRD-001",
   "title": "The timeframe picker and the filter chrome refetch every tile and chart with the same boundary and update the as-of stamp",
-  "description": "A timeframe preset change (from the operator-elicited set: last-7-days, last-30-days, quarter-to-date or an elicited override) issues one refetch per tile and one refetch per rendered chart, and every fetch carries the same `from` and `to` boundary and the same `preset` name. A filter chrome change (operator toggles a filter chip, types into a filter input) issues the same refetch fan-out with the same boundary. Once every fetch has returned (or the timeout has elapsed) the shell updates one `as of <ISO-8601>` stamp on the shell, and every rendered tile carries the same stamp. A shell whose fetches drift boundaries (one tile refetches with the new boundary, another with the old) fails the pack check AC-19104-1; a shell whose as-of stamp does not match every tile's rendered stamp fails the same check.",
+  "description": "A timeframe preset change (from the operator-elicited set: last-7-days, last-30-days, quarter-to-date or an elicited override) issues one refetch per tile and one refetch per rendered chart, and every fetch carries the same `from` and `to` boundary and the same `preset` name. A filter chrome change (operator toggles a filter chip, types into a filter input) issues the same refetch fan-out with the same boundary. Once every fetch has returned (or the timeout has elapsed) the shell updates one `as of <ISO-8601>` stamp on the shell, and every rendered tile carries the same stamp. A shell whose fetches drift boundaries (one tile refetches with the new boundary, another with the old) fails the pack check AC-19104-1; a shell whose as-of stamp does not match every tile's rendered stamp fails the same check. Auto-refresh is off by default: `data-auto-refresh` on the shell root reads `off` unless the operator elicits an `auto-refresh-interval-seconds` positive integer; a positive value sets `data-auto-refresh` to the elicited seconds and the shell refetches on the same fan-out contract at that interval (ADR-2002).",
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "The fan-out contract is what stops a dashboard from lying to the reader: two tiles at different boundaries render numbers the reader compares as if they were the same period, and the comparison is silently wrong. Codifying the same-boundary rule and pinning it to a single as-of stamp is the runtime check that makes the fan-out contract inspectable.",
-  "tags": ["blueprint:application-dashboard", "category:04-fanout-contract"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-dashboard",
+    "category:04-fanout-contract"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z",
+  "deliveredBy": {
+    "tacId": "TAC-2001-application-dashboard-tile-grid",
+    "field": "responsibilities"
+  }
 }

package/blueprints/application-dashboard/contributions/requirements/application-dashboard-req-005.json

@@ -2,14 +2,21 @@
   "reqId": "application-dashboard-REQ-005",
   "prdId": "PRD-001",
   "title": "The export handle exposes an accessible format list and delegates PNG-of-chart to the application-charts render shell",
-  "description": "The export handle is a labelled `<button>` on the shell that opens an operator-navigable list of export formats: CSV of the currently rendered data, PDF of the shipped dashboard surface, and PNG of a specific rendered chart. The list is keyboard-reachable in reading order and closes on Escape without losing focus. PNG-of-chart delegates to the application-charts render shell (TAC-1901): the export handle names the chart the operator picked from the chart region and the charts shell owns the PNG generation. Formats outside the shipped set (SVG, XLSX) are the elicited-override path (ADR-2003) and follow the same accessible-list contract.",
+  "description": "The export handle is a labelled `<button>` on the shell that opens an operator-navigable list of export formats: CSV of the currently rendered data, PDF of the shipped dashboard surface, and PNG of a specific rendered chart. The list is keyboard-reachable in reading order and closes on Escape without losing focus. PNG-of-chart delegates to the application-charts render shell (TAC-1901): the export handle names the chart the operator picked from the chart region and the charts shell owns the PNG generation. Formats outside the shipped set (SVG, XLSX) are the elicited-override path (ADR-2003) and follow the same accessible-list contract. The shipped format tokens are `csv`, `pdf` and `png-chart`; an elicited `export-formats` list appends operator-authored tokens to the shipped set per ADR-2003.",
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "Export is one of the shelf's most-requested affordances and one of the most under-reviewed for accessibility: a hover-only dropdown or a mouse-only download button is common. Naming the accessible-list contract explicitly and delegating PNG-of-chart to the charts blueprint is what keeps the export handle honest and prevents a duplicate PNG generator inside the dashboard shell.",
-  "tags": ["blueprint:application-dashboard", "category:05-export-handle"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-dashboard",
+    "category:05-export-handle"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z",
+  "deliveredBy": {
+    "tacId": "TAC-2001-application-dashboard-tile-grid",
+    "field": "responsibilities"
+  }
 }

package/blueprints/application-dashboard/contributions/tacs/tac-2001-application-dashboard-tile-grid.json

@@ -2,7 +2,7 @@
   "tacId": "TAC-2001-application-dashboard-tile-grid",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Dashboard tile grid, primary KPI placement, and breakpoint reflow",
   "purpose": "Owns the dashboard shell's tile row and tile grid: the CSS Grid definition every tile lives on, the primary KPI placement top-left, the four-state region contract on every tile, and the breakpoint reflow to one column at 360. The shell mounts the chart region through the application-charts render shell (TAC-1901's dependency here) and delegates chart rendering to that shell; the tile grid is the substitutable interface the pack asserts on.",

package/blueprints/application-dashboard/contributions/tacs/tac-2002-application-dashboard-filter-chrome.json

@@ -2,13 +2,13 @@
   "tacId": "TAC-2002-application-dashboard-filter-chrome",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Timeframe picker and filter chrome with refetch fan-out contract",
   "purpose": "Owns the shell's timeframe picker and filter chrome, and the refetch fan-out contract: a preset change or a filter change issues one refetch per tile and one per rendered chart, every fetch carrying the same boundary and the same preset name, and once the batch has returned the shell updates one `data-as-of` attribute the tiles inherit. The fan-out contract is the substitutable interface the pack asserts on (AC-19104-1).",
   "responsibilities": [
     "Render the timeframe picker as an accessible list of presets (labelled `<button>` elements or a `<select>`) with a keyboard-reachable default from ADR-2002 (`last-7-days` unless elicited) (AC-19104-1).",
-    "Render filter chrome as labelled interactive elements (chips, dropdowns, text inputs) keyboard-reachable in reading order before the tile row; a hover-only control is refused at project-side review (AC-19105-1).",
+    "Render filter chrome as labelled interactive elements (chips, dropdowns, text inputs) keyboard-reachable in reading order before the tile row; a hover-only control is refused at project-side check (AC-19105-1).",
     "On a preset change or a filter change, issue one refetch per tile and one per rendered chart; every fetch carries the same `from` and `to` boundary, the same `preset` name and the same active-filters set (AC-19104-1, AC-19105-2).",
     "Update one `data-as-of` attribute on the shell root once every fetch has returned (or the timeout has elapsed) and propagate the same value to every tile's `data-as-of` attribute (AC-19104-1).",
     "Expose a request log on `window.__dashboardFetches` (an append-only array of `{ from, to, preset, filters, tileId, chartId, at }` records) so the pack can read every fetch after each preset change (AC-19104-1)."

package/blueprints/application-dashboard/contributions/tacs/tac-2003-application-dashboard-export-handle.json

@@ -2,7 +2,7 @@
   "tacId": "TAC-2003-application-dashboard-export-handle",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Export handle with format list and delegation to the charts render shell",
   "purpose": "Owns the shell's export handle: a labelled `<button>` that on activation opens an accessible list of formats (CSV, PDF, PNG-of-chart by default; ADR-2003 elicits overrides), and delegates PNG-of-chart generation to the application-charts render shell (TAC-1901). The handle is the substitutable interface the shell exposes to export tooling; the PNG-of-chart delegation stops the dashboard shell from carrying its own PNG generator.",
@@ -28,8 +28,8 @@
       "description": "PNG-of-chart export generation delegates to the charts shell; the dashboard export handle carries no PNG generator of its own."
     }
   ],
-  "tradeoffs": "The three shipped formats (CSV, PDF, PNG-of-chart) cover the common dashboard export cases; ADR-2003's elicited override handles SVG, XLSX and any operator-specific format. The delegation to the charts shell means a project that ships a bespoke chart engine outside the render shell needs a PNG output path of its own; the export handle names the residual under project-side review.",
-  "notes": "Known mechanism-reach gap: the pack browser has no download-capture seam today, so AC-19106-2 (PNG delegation) is proven at project-side review, not through the shipped pack. The README names it individually.",
+  "tradeoffs": "The three shipped formats (CSV, PDF, PNG-of-chart) cover the common dashboard export cases; ADR-2003's elicited override handles SVG, XLSX and any operator-specific format. The delegation to the charts shell means a project that ships a bespoke chart engine outside the render shell needs a PNG output path of its own; the export handle names the residual under project-side check.",
+  "notes": "Known mechanism-reach gap: the pack browser has no download-capture seam today, so AC-19106-2 (PNG delegation) is proven at project-side check, not through the shipped pack. The README names it individually.",
   "createdAt": "2026-09-04T22:10:00Z",
   "updatedAt": "2026-09-04T22:10:00Z"
 }

package/blueprints/application-dashboard/contributions/user-stories/application-dashboard-us-19101.json

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19101",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-001",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "The dashboard shell renders the five required regions on every shipped surface",
   "asA": "product owner responsible for the shipped dashboard surface",
@@ -16,20 +16,68 @@
       "when": "the accessibility tree is read",
       "then": "five labelled regions cover the tile row, the chart region, the filter chrome, the timeframe picker and the export handle",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19101-2",
-      "description": "Given the shell's chart region, the rendered chart mounts through the application-charts render shell (TAC-1901): the chart region contains at least one `section.chartRegion[role=\"region\"]` element carrying the shape the application-charts pack asserts on (an `svg.chartSvg` and a paired `<table>` element in the same landmark). A chart region that renders a chart outside the render shell fails project-side review.",
+      "description": "Given the shell's chart region, the rendered chart mounts through the application-charts render shell (TAC-1901): the chart region contains at least one `section.chartRegion[role=\"region\"]` element carrying the shape the application-charts pack asserts on (an `svg.chartSvg` and a paired `<table>` element in the same landmark). A chart region that renders a chart outside the render shell fails project-side check.",
       "given": "the rendered chart region",
       "when": "the mount seam is inspected",
       "then": "the chart mounts through the application-charts render shell",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-19101-3",
+      "description": "Given a rendered dashboard surface, when a required region is omitted from the DOM (no export handle, no filter chrome, no timeframe picker), the surface either supersedes REQ-001 with a project-authored REQ documenting the omission (the pack looks up the sidecar `rcf/blueprints/application-dashboard.applied.json` for a `supersedes` entry) or renders the region as an empty labelled `role=\"region\"` element the pack can inspect; a silent omission fails project-side check.",
+      "given": "a rendered dashboard surface with a missing region and no documented supersedes entry",
+      "when": "the pack inspects the shell",
+      "then": "the surface fails the region-count check; the applying project must either supersede REQ-001 with a documented reason or render the region as an empty labelled role=region element",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "purpose"
+      }
+    },
+    {
+      "id": "AC-19101-4",
+      "description": "Given the five labelled regions, each region's accessible name is unique on the surface (a screen reader announces five distinct region names when navigating landmarks); duplicate `aria-label` values on two regions fail the pack check because the reader cannot distinguish them.",
+      "given": "the five labelled regions on the shell",
+      "when": "assistive-tech landmark navigation reads them",
+      "then": "each region carries a unique accessible name; duplicates fail the pack check",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "purpose"
+      }
+    },
+    {
+      "id": "AC-19101-5",
+      "description": "Given a rendered dashboard whose chart region contains NO chart (the applying project has no charts to show), the region still renders with its `role=\"region\"` wrapper and an accessible-name announcement; the pack accepts an empty labelled chart region and does not require a chart mount.",
+      "given": "a dashboard surface whose chart region contains no chart",
+      "when": "the pack inspects the chart region",
+      "then": "the empty region still renders with its role=region wrapper and accessible name; the pack does not require a chart mount",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "purpose"
+      }
     }
   ],
-  "tacIds": ["TAC-2001-application-dashboard-tile-grid"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2001-application-dashboard-tile-grid"
+  ],
+  "tags": [
+    "blueprint:application-dashboard"
+  ],
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-dashboard/contributions/user-stories/application-dashboard-us-19102.json

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19102",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-002",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "The primary KPI tile sits top-left in DOM order and in CSS Grid position across the ratified breakpoints",
   "asA": "reader glancing at the shipped dashboard on a laptop, a tablet and a phone",
@@ -16,20 +16,68 @@
       "when": "the DOM order and the computed CSS Grid position are read",
       "then": "the primary KPI tile is first in DOM order and top-left in CSS Grid at each of the three widths",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19102-2",
-      "description": "Given a rendered dashboard surface with no primary KPI tile, the surface either supersedes REQ-002 with a project-authored REQ documenting the omission or fails project-side review. This case is a documentation-and-review contract; the pack asserts the primary KPI tile exists (AC-19102-1) but does not itself enforce the fallback path.",
+      "description": "Given a rendered dashboard surface with no primary KPI tile, the surface either supersedes REQ-002 with a project-authored REQ documenting the omission or fails project-side check. This case is a documentation contract; the pack asserts the primary KPI tile exists (AC-19102-1) but does not itself enforce the fallback path.",
       "given": "a rendered dashboard with no primary KPI tile",
       "when": "the surface is reviewed",
-      "then": "the surface supersedes REQ-002 with a project-authored REQ or fails review",
+      "then": "the surface supersedes REQ-002 with a project-authored REQ or fails the check",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-19102-3",
+      "description": "Given a rendered dashboard at the 360 breakpoint, when the tile row reflows to one column, the primary KPI tile carries `row-start: 1` in its computed CSS Grid position; a secondary tile whose row-start is 1 at 360 (competing for the top-left slot) fails the pack check.",
+      "given": "a rendered dashboard at 360 with the tile row reflowed to one column",
+      "when": "the pack inspects computed CSS Grid positions",
+      "then": "the primary KPI tile has row-start: 1 and no secondary tile shares that row-start",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "responsibilities[0]"
+      }
+    },
+    {
+      "id": "AC-19102-4",
+      "description": "Given the operator elicited `primary-kpi-kind=custom`, the primary tile carries `data-kpi-kind=\"custom\"` AND a `data-kpi-name` attribute whose value is the operator-elicited `primary-kpi-custom-name`; a `custom` kind without a `data-kpi-name` fails the pack check. Applying agent sets: the custom short name.",
+      "given": "a rendered dashboard whose primary-kpi-kind is elicited as `custom`",
+      "when": "the pack inspects the primary tile attributes",
+      "then": "the tile carries both `data-kpi-kind=\"custom\"` and a non-empty `data-kpi-name` matching the elicited short name",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template",
+      "ownerRef": {
+        "adrId": "ADR-2001-application-dashboard-primary-kpi-enum",
+        "field": "decision"
+      }
+    },
+    {
+      "id": "AC-19102-5",
+      "description": "Given a rendered dashboard whose primary tile carries a `data-kpi-kind` value outside the ADR-2001 enum (a typo, an operator override that did not follow the elicit), the pack fails the check naming the invalid value; the check reads the attribute value and asserts membership in {revenue, active-users, error-rate, throughput, custom}.",
+      "given": "a primary tile with a data-kpi-kind value outside the ADR-2001 enum",
+      "when": "the pack inspects the attribute",
+      "then": "the check fails naming the invalid value and asserting the required enum membership",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-2001-application-dashboard-primary-kpi-enum",
+        "field": "decision"
+      }
     }
   ],
-  "tacIds": ["TAC-2001-application-dashboard-tile-grid"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2001-application-dashboard-tile-grid"
+  ],
+  "tags": [
+    "blueprint:application-dashboard"
+  ],
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-09T00:00:00Z"
 }

package/blueprints/application-dashboard/contributions/user-stories/application-dashboard-us-19103.json

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19103",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-003",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "Every tile honours the four-state contract with distinct visuals, role region, aria-live polite and non-colour distinction",
   "asA": "screen-reader user and colour-blind reader on the shipped dashboard",
@@ -16,20 +16,72 @@
       "when": "the DOM and the accessibility tree are read",
       "then": "each state carries role region, aria-live polite, data-tile-state, a non-colour visual cue and the announced name",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19103-2",
-      "description": "Given a tile transitioning between states (loading to populated, populated to error) at runtime, the tile's `aria-live=\"polite\"` region announces the new state's accessible name to the assistive tech; the announcement text reads `<tile title>, <new state>` and the visual cue changes in the same paint. This AC is a runtime-observable behaviour on state transition; the pack does not simulate the transition today (the runner has no synthetic-event seam beyond click/type/press), so the AC is proven at project-side review and the README names the transition-observation gap under known mechanism-reach gaps.",
+      "description": "Given a tile transitioning between states (loading to populated, populated to error) at runtime, the tile's `aria-live=\"polite\"` region announces the new state's accessible name to the assistive tech; the announcement text reads `<tile title>, <new state>` and the visual cue changes in the same paint. This AC is a runtime-observable behaviour on state transition; the pack does not simulate the transition today (the runner has no synthetic-event seam beyond click/type/press), so the AC is proven at project-side check and the README names the transition-observation gap under known mechanism-reach gaps.",
       "given": "a tile transitioning between states",
       "when": "the transition renders",
       "then": "the aria-live polite region announces the new state's accessible name and the visual cue changes",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-19103-3",
+      "description": "Given a rendered tile whose state is conveyed only through colour (a red border for error, a grey wash for loading, no text label or role), the pack fails the check per WCAG 1.4.1; a passing tile combines a non-colour visual cue (a shape, a text label, a spinner motion) and the accessible name reads `<tile title>, <state>`.",
+      "given": "a rendered tile whose state distinction is colour-only",
+      "when": "the pack inspects the tile's visual and accessible name",
+      "then": "the check fails; a passing tile combines a non-colour visual cue with a labelled state announcement",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "responsibilities[2]"
+      },
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-19103-4",
+      "description": "Given a rendered tile in the `error` state, the tile carries the recorded reason (an error record's `code` or a short message) visible in the DOM within the tile's region; a tile in the error state with no visible reason (an empty error block, an icon-only error indicator) fails the check.",
+      "given": "a rendered tile in the error state",
+      "when": "the pack inspects the tile's region content",
+      "then": "the tile carries a visible reason (error code or short message); an empty or icon-only error tile fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "responsibilities[2]"
+      }
+    },
+    {
+      "id": "AC-19103-5",
+      "description": "Given a tile transitioning rapidly across states (loading -> error -> loading -> populated within a 250ms window during a retry loop), the aria-live polite announcer coalesces or throttles announcements so assistive tech does not read four transitions in that window; the pack drives the fixture that fires the transitions and inspects the announcer's queued text at settle.",
+      "given": "a tile transitioning across four states within a 250ms window",
+      "when": "the aria-live polite announcer queues the transition text",
+      "then": "announcements are coalesced or throttled so the reader hears the settled state, not every intermediate flip",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "responsibilities[2]"
+      }
     }
   ],
-  "tacIds": ["TAC-2001-application-dashboard-tile-grid"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2001-application-dashboard-tile-grid"
+  ],
+  "tags": [
+    "blueprint:application-dashboard"
+  ],
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-10T07:07:28Z"
 }