rcf-lite 0.26.0 → 0.27.0

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,7 +16,8 @@
       "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",
@@ -25,11 +26,58 @@
       "when": "the surface is reviewed",
       "then": "the surface supersedes REQ-002 with a project-authored REQ or fails review",
       "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,7 +16,8 @@
       "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",
@@ -25,11 +26,62 @@
       "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"
 }

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

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19104",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-004",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "A timeframe preset change refetches every tile and chart with the same boundary and updates the as-of stamp",
   "asA": "operator changing the dashboard timeframe from last-7-days to last-30-days",
@@ -16,20 +16,68 @@
       "when": "the request log and the DOM are read",
       "then": "every refetch carries the same from/to/preset and every tile's data-as-of matches the shell root",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19104-2",
-      "description": "Given a rendered dashboard with an operator-elicited auto-refresh interval (ADR-2002), the shell refetches on the same fan-out contract at the interval: every tile refetches with the same from/to/preset, the as-of stamp updates on the shell root and every tile. When no auto-refresh interval is elicited, the shell does not refresh unattended (a dashboard that refreshes every ten seconds without an operator opt-in is a defect). The pack asserts the initial default is auto-refresh off through a `data-auto-refresh` attribute on the shell root; a fixture whose default is on fails project-side review.",
+      "description": "Given a rendered dashboard with an operator-elicited auto-refresh interval (ADR-2002), the shell refetches on the same fan-out contract at the interval: every tile refetches with the same from/to/preset, the as-of stamp updates on the shell root and every tile. When no auto-refresh interval is elicited, the shell does not refresh unattended (a dashboard that refreshes every ten seconds without an operator opt-in is a defect). The pack asserts the initial default is auto-refresh off through a `data-auto-refresh` attribute on the shell root; a fixture whose default is on fails project-side review. Applying agent sets: the elicited auto-refresh interval value in seconds (ADR-2002) or the explicit off default, recorded on the manifest and reflected on the shell root as `data-auto-refresh`.",
       "given": "a rendered dashboard with or without an elicited auto-refresh interval",
       "when": "the shell renders",
       "then": "auto-refresh is off unless the interval is elicited; refreshes follow the same fan-out contract",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-19104-3",
+      "description": "Given a rendered dashboard mid-refetch (a preset change fired 200ms ago; some tile fetches have returned, others are pending), when the operator activates a SECOND preset change, the shell cancels the in-flight fetches for the first preset and issues a fresh fan-out for the second preset; the pack asserts no tile renders data from the abandoned preset alongside data from the new one.",
+      "given": "an operator activating a second preset change while the first fan-out is still in flight",
+      "when": "the shell handles the second change",
+      "then": "the in-flight first-preset fetches are cancelled and a fresh fan-out issues for the second preset; no mixed-preset data appears on tiles",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2002-application-dashboard-filter-chrome",
+        "field": "responsibilities[1]"
+      }
+    },
+    {
+      "id": "AC-19104-4",
+      "description": "Given a preset change that fires a fan-out and every tile's fetch rejects (a network partition, a downstream outage), when every fetch has settled as a failure, then the shared `as of <ISO-8601>` stamp still advances (settled includes failed), every tile enters the error state carrying the shared stamp, and one aria-live polite announcement names the whole-surface failure so the operator hears the state change.",
+      "given": "a preset change fan-out where every tile fetch rejects",
+      "when": "every fetch has settled as a failure",
+      "then": "the shared as-of stamp advances, every tile is in the error state carrying the shared stamp, and one aria-live announcement names the whole-surface failure",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2002-application-dashboard-filter-chrome",
+        "field": "responsibilities[1]"
+      }
+    },
+    {
+      "id": "AC-19104-5",
+      "description": "Given a rendered dashboard whose elicited timeframe presets include an operator-authored addition (per the elicited `timeframe-presets`), when the operator activates the elicited preset, the fan-out contract fires unchanged (same from/to/preset boundary on every fetch); a preset that fails to fire the fan-out because the shell does not recognise the elicited name fails the pack check. Applying agent sets: the elicited preset tokens.",
+      "given": "an operator-elicited additional timeframe preset activated on the dashboard",
+      "when": "the shell handles the change",
+      "then": "the fan-out fires with the elicited preset name unchanged; a shell that ignores the elicited preset fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template",
+      "ownerRef": {
+        "adrId": "ADR-2002-application-dashboard-timeframe-presets",
+        "field": "decision"
+      }
     }
   ],
-  "tacIds": ["TAC-2002-application-dashboard-filter-chrome"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2002-application-dashboard-filter-chrome"
+  ],
+  "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-19105.json

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19105",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-004",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "status": "approved",
   "title": "The filter chrome exposes accessible controls and refetches every tile with the same boundary",
   "asA": "operator narrowing the dashboard with a filter chip or a filter input",
@@ -16,7 +16,8 @@
       "when": "the accessibility tree is read",
       "then": "every filter control is a labelled interactive element keyboard-reachable in reading order",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19105-2",
@@ -25,11 +26,58 @@
       "when": "the request log is read",
       "then": "every refetch carries the same active-filters set and the shell attribute updates",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-19105-3",
+      "description": "Given a rendered dashboard with a filter input, when the operator types a value that violates the input's `pattern` or exceeds its `maxlength`, the shell does NOT fire a refetch; the filter chrome surfaces an accessible inline validation message (`aria-describedby` on the input pointing at the message region) and the tile grid retains its last successful state.",
+      "given": "an operator typing an invalid value into a filter input (pattern/maxlength violation)",
+      "when": "the shell validates the input",
+      "then": "no refetch fires, an accessible inline validation message announces the failure, and the tile grid retains its last successful state",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2002-application-dashboard-filter-chrome",
+        "field": "responsibilities[0]"
+      }
+    },
+    {
+      "id": "AC-19105-4",
+      "description": "Given a filter change that fires a fan-out refetch and a subset of tile fetches reject (2 of 6 return 5xx or time out), the shared `as of <ISO-8601>` stamp advances after every tile has SETTLED (succeeded or failed) and the failed tiles enter the error state with the shared stamp; a shell whose stamp advances only after successful tiles fails the pack check.",
+      "given": "a filter change fan-out where a subset of tile fetches reject",
+      "when": "every fetch has settled",
+      "then": "the shared as-of stamp advances after every tile has settled and the failed tiles are in the error state carrying the shared stamp",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2002-application-dashboard-filter-chrome",
+        "field": "responsibilities[1]"
+      }
+    },
+    {
+      "id": "AC-19105-5",
+      "description": "Given a filter reset action (a `Clear filters` control on the chrome), when the operator activates it, every filter control reverts to its default value, one refetch fires per tile and per chart with no filter parameters, and the tile grid re-renders on the response; the reset action is keyboard-reachable and carries an accessible name matching `Clear filters` or an equivalent.",
+      "given": "an operator activating the Clear filters control",
+      "when": "the shell handles the reset",
+      "then": "every filter control reverts to default, one refetch fires per tile and per chart without filter parameters, and the reset control is keyboard-reachable with an accessible name",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2002-application-dashboard-filter-chrome",
+        "field": "responsibilities[0]"
+      }
     }
   ],
-  "tacIds": ["TAC-2002-application-dashboard-filter-chrome"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2002-application-dashboard-filter-chrome"
+  ],
+  "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-19106.json

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19106",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-005",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "title": "The export handle exposes an accessible format list and delegates PNG-of-chart to the application-charts render shell",
   "asA": "operator downloading the current dashboard slice",
@@ -11,25 +11,77 @@
   "acceptanceCriteria": [
     {
       "id": "AC-19106-1",
-      "description": "Given a rendered dashboard surface, the export handle region contains one labelled `<button>` (accessible name reads `Export` or an operator-configured equivalent) that on activation exposes a keyboard-reachable list of formats (a menu, a listbox or a set of `<button>` elements). The rendered format list carries at least the three shipped formats (CSV, PDF, PNG-of-chart) unless ADR-2003's elicited override replaces the set; every format entry carries a `data-export-format` attribute whose value is one of `csv`, `pdf`, `png-chart` or the elicited value. Escape closes the list and returns focus to the export button. Hover-only export dropdowns fail project-side review.",
+      "description": "Given a rendered dashboard surface, the export handle region contains one labelled `<button>` (accessible name reads `Export` or an operator-configured equivalent) that on activation exposes a keyboard-reachable list of formats (a menu, a listbox or a set of `<button>` elements). The rendered format list carries at least the three shipped formats (CSV, PDF, PNG-of-chart) unless ADR-2003's elicited override replaces the set; every format entry carries a `data-export-format` attribute whose value is one of `csv`, `pdf`, `png-chart` or the elicited value. Escape closes the list and returns focus to the export button. Hover-only export dropdowns fail project-side review. Applying agent sets: the export-button accessible name (default `Export` or the operator-configured equivalent), the export-format list (default `csv`, `pdf`, `png-chart` or the ADR-2003 elicited override) and the `data-export-format` values the format entries carry.",
       "given": "a rendered dashboard with an export handle",
       "when": "the operator activates the export button",
       "then": "an accessible format list opens with the shipped formats, keyboard-reachable, closable on Escape",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
     },
     {
       "id": "AC-19106-2",
-      "description": "Given a PNG-of-chart export selection, the export handle delegates the PNG generation to the application-charts render shell (TAC-1901): the handle names the chart the operator picked from the chart region (a `data-chart-id` reference on the format entry, or a runtime prompt asking which chart) and the charts shell owns the PNG output. A dashboard shell that ships its own PNG generator inside the dashboard code fails project-side review. This AC is a project-side contract; the pack does not exercise the PNG generation today (no download-capture seam on the pack browser), and the README names the delegation-observation gap under known mechanism-reach gaps.",
+      "description": "Given a PNG-of-chart export selection, the export handle delegates the PNG generation to the application-charts render shell (TAC-1901): the handle names the chart the operator picked from the chart region (a `data-chart-id` reference on the format entry, or a runtime prompt asking which chart) and the charts shell owns the PNG output. A dashboard shell that ships its own PNG generator inside the dashboard code fails project-side review. This AC is a project-side contract; the pack does not exercise the PNG generation today (no download-capture seam on the pack browser), and the README names the delegation-observation gap under known mechanism-reach gaps. Applying agent sets: the chart-selection mechanism the export handle uses for PNG-of-chart (the `data-chart-id` reference on the format entry, or a runtime prompt naming the chart the operator picked) and the application-charts render-shell mount point the shell delegates to.",
       "given": "a PNG-of-chart export selection",
       "when": "the export handle activates",
       "then": "PNG generation delegates to the application-charts render shell",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-19106-3",
+      "description": "Given `onExportRequest` rejects (for example because the slice is empty, the format is unsupported, or a downstream service refuses), when the operator invokes export, then no download or blob is delivered, an accessible failure message is announced via an `aria-live` region naming the rejection reason, and the surface's control returns to its idle state.",
+      "given": "an export handle whose promise rejects on the requested slice",
+      "when": "the operator triggers export",
+      "then": "no blob is produced, an announced failure names the reason, and the control returns to idle",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2003-application-dashboard-export-handle",
+        "field": "interfaces[0].name"
+      }
+    },
+    {
+      "id": "AC-19106-4",
+      "description": "Given the export handle's format list is open, when the operator presses Escape, the list closes and focus returns to the labelled `<button>` that opened it (not to the document body); a list that returns focus elsewhere fails the pack check per WCAG 2.4.3 focus return.",
+      "given": "the export format list open and the operator pressing Escape",
+      "when": "the list closes",
+      "then": "focus returns to the labelled button that opened the list; a focus return to elsewhere fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2003-application-dashboard-export-handle",
+        "field": "purpose"
+      },
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-19106-5",
+      "description": "Given an elicited `export-formats` list that adds an operator-authored format token (an XLSX, an SVG), when the operator opens the export list, the operator-authored formats append AFTER the shipped set (csv, pdf, png-chart) in the accessible list; each carries an operator-supplied `label` and the `data-export-format` value the operator elicited. Applying agent sets: the elicited format tokens and their labels.",
+      "given": "an elicited export-formats list adding operator-authored tokens",
+      "when": "the pack inspects the export list DOM",
+      "then": "operator-authored formats appear after the shipped set, each carrying an operator label and data-export-format value",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template",
+      "ownerRef": {
+        "adrId": "ADR-2003-application-dashboard-export-formats",
+        "field": "decision"
+      }
     }
   ],
-  "tacIds": ["TAC-2003-application-dashboard-export-handle"],
-  "tags": ["blueprint:application-dashboard"],
+  "tacIds": [
+    "TAC-2003-application-dashboard-export-handle"
+  ],
+  "tags": [
+    "blueprint:application-dashboard"
+  ],
   "createdAt": "2026-09-04T22:10:00Z",
-  "updatedAt": "2026-09-04T22:10:00Z"
+  "updatedAt": "2026-09-10T07:07:28Z"
 }

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

@@ -2,7 +2,7 @@
   "usId": "application-dashboard-US-19107",
   "prdId": "PRD-001",
   "reqId": "application-dashboard-REQ-002",
-  "version": "1.0.0",
+  "version": "1.0.4",
   "status": "approved",
   "title": "The applying agent reads the packaged design-guidance asset and honours its ratified surface rules",
   "asA": "agent applying the application-dashboard blueprint on a shipped surface",
@@ -11,25 +11,73 @@
   "acceptanceCriteria": [
     {
       "id": "AC-19107-1",
-      "description": "The blueprint ships an operator-and-agent-readable design-guidance file at `assets/guidance/dashboard-design.md` covering the eight sections named in spec 5.3.1 (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). Each section names whether the rule hardens into an AC on this blueprint (the section names the AC id) or stays operator guidance the applying agent honours at project-side review. The file cites at least five https:// sources from the five named source families (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs).",
+      "description": "The blueprint ships an operator-and-agent-readable design-guidance file at `assets/guidance/dashboard-design.md` covering the eight sections named in spec 5.3.1 (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). Each section names whether the rule hardens into an AC on this blueprint (the section names the AC id) or stays operator guidance the applying agent honours at project-side review. The file cites at least five https:// sources from the five named source families (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs). The applying agent confirms the file is present on the applied blueprint source path recorded on `manifest.blueprints[].source` and takes no substitution at project apply time.",
       "given": "the shipped blueprint",
       "when": "the applying agent reads assets/guidance/dashboard-design.md",
       "then": "the eight sections and the five https citations are present and each section names AC or guidance",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed"
     },
     {
       "id": "AC-19107-2",
-      "description": "The dashboard shell's runtime shape reflects the rules the guidance hardens into ACs: the primary-KPI kind is one of the ADR-2001 enum values (asserted through `data-kpi-kind` on the primary tile; guidance section 1 hardens into AC-19102-1); the shell renders an `as of <ISO-8601>` stamp (guidance section 7 hardens into AC-19104-1); auto-refresh is off unless the elicited interval is set (guidance section 7 hardens into AC-19104-2). A shipped surface that violates any of these rules fails the corresponding pack check or project-side review.",
+      "description": "The dashboard shell's runtime shape reflects the rules the guidance hardens into ACs: the primary-kpi kind is one of the ADR-2001 enum values (asserted through `data-kpi-kind` on the primary tile; guidance section 1 hardens into AC-19102-1); the shell renders an `as of <ISO-8601>` stamp (guidance section 7 hardens into AC-19104-1); auto-refresh is off unless the elicited interval is set (guidance section 7 hardens into AC-19104-2). A shipped surface that violates any of these rules fails the corresponding pack check or project-side review. Applying agent sets: the primary-kpi kind value from the ADR-2001 enum (`revenue`, `active-users`, `error-rate`, `throughput`, or `custom` with a `data-kpi-name`), the auto-refresh interval or the off default, and the tile-inventory slot mapping the shell renders.",
       "given": "a rendered dashboard shell",
       "when": "the shell is inspected against the guidance's hardened rules",
-      "then": "the shape honours the primary-KPI kind, the as-of stamp and the auto-refresh default",
+      "then": "the shape honours the primary-kpi kind, the as-of stamp and the auto-refresh default",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-19107-3",
+      "description": "Given the applying project's rendered dashboard, when the pack inspects the surface against every rule the packaged guidance ratifies (primary-kpi top-left placement, tile density under the guidance's cap, one-of-four state visibility, timeframe presets from the elicited set, fan-out share of the as-of stamp, export handle presence, WCAG 1.4.1 non-colour distinction on tile state), a rule violation fails the pack check naming the guidance section that ratified the rule.",
+      "given": "an applying project's rendered dashboard checked against the packaged guidance rules",
+      "when": "the pack inspects each ratified rule",
+      "then": "a violation fails naming the guidance section responsible",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "purpose"
+      },
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-19107-4",
+      "description": "Given the design-guidance asset shipped at `assets/guidance/dashboard-design.md`, when the applying agent's pack inspects the manifest, the file is present, non-empty, and carries H2 headings for the eight sections named in spec 5.3.1; a missing file, an empty file or a file missing any of the eight sections fails the pack check.",
+      "given": "the packaged design-guidance asset",
+      "when": "the pack inspects the asset",
+      "then": "the file is present, non-empty and carries H2 headings for the eight ratified sections; a missing or short-of-sections file fails",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2001-application-dashboard-tile-grid",
+        "field": "purpose"
+      }
+    },
+    {
+      "id": "AC-19107-5",
+      "description": "Given an applying project that ships a surface deviating from a ratified rule (a primary KPI placed top-right for cultural reasons, a tile density above the guidance cap), the deviation is documented on the project's own README under CALLS MADE with the guidance section quoted verbatim and the project's reason; a deviation without a documented CALLS MADE entry fails project-side review. Applying agent sets: the CALLS MADE entry text (the ratified guidance section quoted verbatim and the project's reason for deviating), the project's superseding REQ id, and the specific deviation named (for example the primary-kpi placement or the tile-density limit).",
+      "given": "an applying project surface deviating from a ratified guidance rule",
+      "when": "the review inspects the project's CALLS MADE section",
+      "then": "the deviation is documented with the guidance section quoted verbatim and the project's reason; an undocumented deviation fails review",
+      "testable": true,
+      "scope": "unclassified",
+      "disposition": "template"
     }
   ],
-  "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"
 }

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

@@ -56,6 +56,6 @@ Every check carries a `description` field per spec section 9. `appliesTo` binds
 
 ## Consumers and dependencies
 
-- Consumes `application-charts` (visual round T-2): the chart region on every dashboard surface mounts through the application-charts render shell (TAC-1901). The dashboard pack does not duplicate the chart-accessibility ACs; the charts pack fires on the dashboard's chart route through its own applicability predicate.
-- References `application-datatable` (visual round T-1) in the packaged design guidance's section 6 ("when a table beats a chart"). A dashboard whose data really wants a records table applies the datatable blueprint instead of overloading the tile row.
-- Extends the T-0 pack-browser seam with a `resize(width, height)` method; every blueprint after this one that ships a breakpoint-scoped visual AC reuses the seam.
+- Consumes `application-charts` (visual round): the chart region on every dashboard surface mounts through the application-charts render shell (TAC-1901). The dashboard pack does not duplicate the chart-accessibility ACs; the charts pack fires on the dashboard's chart route through its own applicability predicate.
+- References `application-datatable` (visual round) in the packaged design guidance's section 6 ("when a table beats a chart"). A dashboard whose data really wants a records table applies the datatable blueprint instead of overloading the tile row.
+- Extends the pack-browser seam with a `resize(width, height)` method; every blueprint after this one that ships a breakpoint-scoped visual AC reuses the seam.

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

@@ -2,7 +2,7 @@
 
 ## What it is
 
-A shipped, vendor-neutral analytics-dashboard contract for a rcf-lite application. One tile grid with primary-KPI hierarchy at the ratified breakpoints (TAC-2001), one timeframe picker and filter chrome with a refetch fan-out contract (TAC-2002), one export handle with format delegation to charts (TAC-2003), a packaged design-guidance asset the applying agent reads at apply, and a shipped Playwright probe pack that gates ship on the three runtime-observable surfaces the shelf assures: the primary KPI sits top-left at every ratified breakpoint, a timeframe change refetches every tile with the same boundary and one as-of stamp, and every tile honours the four-state contract with role region, aria-live polite and non-colour distinction.
+A shipped, vendor-neutral analytics-dashboard contract for a rcf-lite application. One tile grid with primary-kpi hierarchy at the ratified breakpoints (TAC-2001), one timeframe picker and filter chrome with a refetch fan-out contract (TAC-2002), one export handle with format delegation to charts (TAC-2003), a packaged design-guidance asset the applying agent reads at apply, and a shipped Playwright probe pack that gates ship on the three runtime-observable surfaces the shelf assures: the primary KPI sits top-left at every ratified breakpoint, a timeframe change refetches every tile with the same boundary and one as-of stamp, and every tile honours the four-state contract with role region, aria-live polite and non-colour distinction.
 
 ## What it deliberately is not
 
@@ -14,7 +14,7 @@ A shipped, vendor-neutral analytics-dashboard contract for a rcf-lite applicatio
 ## When to reach for it
 
 - Any shipped surface that renders a mix of stat tiles and one or more charts with a shared timeframe control. Analytics dashboards, admin overview surfaces, per-organisation summary views, ops screens.
-- Projects that want the primary-KPI-hierarchy discipline enforced at ship without hand-authoring per surface.
+- Projects that want the primary-kpi-hierarchy discipline enforced at ship without hand-authoring per surface.
 - Any project that already applies application-charts and needs the composed dashboard shape on top.
 
 ## When it does not fit
@@ -29,7 +29,7 @@ Every dashboard surface renders the five labelled regions. The primary KPI tile
 
 ## The operator decisions that remain open
 
-- **Primary-KPI kind** (ADR-2001). One of revenue, active-users, error-rate, throughput, custom. A `custom` value carries a short operator name.
+- **primary-kpi kind** (ADR-2001). One of revenue, active-users, error-rate, throughput, custom. A `custom` value carries a short operator name.
 - **Timeframe presets and auto-refresh** (ADR-2002). Three presets by recommendedDefault; operator elicits an override. Auto-refresh off unless the operator elicits an interval.
 - **Export formats** (ADR-2003). Three formats by recommendedDefault (CSV, PDF, PNG-of-chart); operator elicits an override.
 - **Tile inventory and slots**. The full tile list and each tile's CSS Grid slot.

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

@@ -5,7 +5,7 @@
 //   AC-19104-1 timeframe refetch fan-out (every fetch same from/to/preset, matching as-of stamp)
 //   AC-19103-1 per-tile four-state contract (role region, aria-live polite, non-colour distinction)
 //
-// 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 tile
 // grid TAC (TAC-2001), the fan-out contract TAC (TAC-2002) and the
@@ -17,7 +17,7 @@
 // reads both to reconcile the timeframe-preset refetch batch.
 //
 // The runner exposes viewport resize through pack-browser's
-// `resize(width, height)` seam (T-3 extension): the primary-KPI
+// `resize(width, height)` seam (extension): the primary-KPI
 // position check drives 1440, 1024 and 360 through the same handle.
 
 export default {
@@ -27,7 +27,7 @@ export default {
   // Applies to any FBS that realises the dashboard tile-grid TAC or
   // whose navModel routes match an operator-configured dashboard
   // route glob. The source references BOTH `tacIds` and `route` so
-  // the T-0 loader's applicability source-scan sees the two legal
+  // the loader's applicability source-scan sees the two legal
   // seams (route is one of the three legal predicates).
   appliesTo: ({ fbs }) => {
     const routes = fbs?.designStage?.navModel?.routes ?? [];
@@ -44,7 +44,7 @@ export default {
       run: async ({ browser, runtimeUrl }) => {
         if (!browser) return { verdict: 'fail', detail: 'no packBrowser wired' };
         if (typeof browser.resize !== 'function') {
-          return { verdict: 'fail', detail: 'packBrowser has no resize seam; the T-3 extension has not landed' };
+          return { verdict: 'fail', detail: 'packBrowser has no resize seam; the extension has not landed' };
         }
         const url = new URL('', runtimeUrl).toString();
         const widths = [1440, 1024, 360];