rcf-lite 0.26.0 → 0.27.0

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,31 @@
 # application-dashboard CHANGELOG
 
-## 1.0.0 (visual round T-3, spec 2026-09-04)
+## 1.0.4 - 2026-09-10
+
+Findings closed: F-1, F-2, F-3, F-4, F-5, F-6. 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 generic phrasing. AC-19107-1 changed to `disposition: fixed` (no project-side substitution: the shipped guidance file satisfies the AC directly). Register cleanup on README shipped prose (removed the dated visual-specification reference and neutralised the pack-browser seam-extension paragraph).
+
+
+## 1.0.3 (register-sweep patch, 2026-09-10)
+
+- Register: neutral wording in shipped prose (no capability change).
+
+## 1.0.2 (application-core completion pass, 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).
+- Review fix pass 2026-09-10: F-1 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; F-3 Applying agent sets clause appended to AC-19107-5 naming the CALLS MADE entry text, the superseding REQ id and the specific deviation; F-6 pre-existing internal work-item reference stripped from the README elicited-parameters paragraph.
+
+## 1.0.1 (application-core hardening, 2026-09-09)
+
+- hardening pass: chain-consistency lint zero (pass1 + pass2); 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) covering the 2026-09-08 review finding F-1 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) covering F-2 on TAC-2003.interfaces[0].
+
+
+## 1.0.0 (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 `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 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.
+- 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 ratified visual specification). No new global topics; suggests the `logging` and `errorHandling` companions. Third blueprint on the shelf that ships a Playwright probe pack under the runner extension.
 
 ## Apply
 
@@ -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,7 +84,7 @@ 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.
@@ -99,4 +99,4 @@ Every runtime-observable AC that is not bound to a pack check appears here indiv
 
 ## 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/blueprint.json

@@ -1,29 +1,155 @@
 {
   "slug": "application-dashboard",
-  "version": "1.0.0",
+  "version": "1.0.4",
   "category": "application",
   "suggestedCompanions": [
-    { "role": "logging", "reason": "Dashboard tile refresh, timeframe change and export activation are the surface's most-touched instrumentation points; a logging companion supplies the factory the tiles and the chart region write records against." },
-    { "role": "errorHandling", "reason": "A tile whose fetch fails renders the error-state visual per REQ-003; the error-state contract needs a project-side error-record factory the application-error-handling companion provides." }
+    {
+      "role": "logging",
+      "reason": "Dashboard tile refresh, timeframe change and export activation are the surface's most-touched instrumentation points; a logging companion supplies the factory the tiles and the chart region write records against."
+    },
+    {
+      "role": "errorHandling",
+      "reason": "A tile whose fetch fails renders the error-state visual per REQ-003; the error-state contract needs a project-side error-record factory the application-error-handling companion provides."
+    }
+  ],
+  "elicits": [
+    {
+      "id": "primary-kpi-kind",
+      "prompt": "Primary KPI kind for the top-left tile: revenue, active-users, error-rate, throughput or custom. The elicited value lands on the primary tile as data-kpi-kind.",
+      "kind": "enum",
+      "options": [
+        "revenue",
+        "active-users",
+        "error-rate",
+        "throughput",
+        "custom"
+      ],
+      "default": "revenue"
+    },
+    {
+      "id": "primary-kpi-custom-name",
+      "prompt": "Custom primary KPI short name. Applies only when primary-kpi-kind is custom; the value lands on the primary tile as data-kpi-name. Ignored otherwise.",
+      "kind": "string",
+      "default": ""
+    },
+    {
+      "id": "timeframe-presets",
+      "prompt": "Timeframe presets the timeframe picker offers, comma separated (missing presets from the shipped set are ignored, extra presets append). Recommended default: last-7-days, last-30-days, quarter-to-date.",
+      "kind": "string",
+      "default": "last-7-days,last-30-days,quarter-to-date"
+    },
+    {
+      "id": "auto-refresh-interval-seconds",
+      "prompt": "Auto-refresh interval in seconds for the whole dashboard fan-out. 0 keeps auto-refresh off (the ship default); a positive integer sets data-auto-refresh on the shell root and refetches on the same fan-out contract at that interval.",
+      "kind": "string",
+      "default": "0"
+    },
+    {
+      "id": "export-formats",
+      "prompt": "Export formats the export handle offers, comma separated (missing formats from the shipped set are ignored, extra formats append with an operator-supplied label). Recommended default: csv, pdf, png-chart.",
+      "kind": "string",
+      "default": "csv,pdf,png-chart"
+    }
   ],
   "contributions": [
-    { "id": "application-dashboard-REQ-001", "kind": "req", "path": "requirements/application-dashboard-req-001.json" },
-    { "id": "application-dashboard-REQ-002", "kind": "req", "path": "requirements/application-dashboard-req-002.json" },
-    { "id": "application-dashboard-REQ-003", "kind": "req", "path": "requirements/application-dashboard-req-003.json" },
-    { "id": "application-dashboard-REQ-004", "kind": "req", "path": "requirements/application-dashboard-req-004.json" },
-    { "id": "application-dashboard-REQ-005", "kind": "req", "path": "requirements/application-dashboard-req-005.json" },
-    { "id": "application-dashboard-US-19101", "kind": "us", "path": "user-stories/application-dashboard-us-19101.json" },
-    { "id": "application-dashboard-US-19102", "kind": "us", "path": "user-stories/application-dashboard-us-19102.json" },
-    { "id": "application-dashboard-US-19103", "kind": "us", "path": "user-stories/application-dashboard-us-19103.json" },
-    { "id": "application-dashboard-US-19104", "kind": "us", "path": "user-stories/application-dashboard-us-19104.json" },
-    { "id": "application-dashboard-US-19105", "kind": "us", "path": "user-stories/application-dashboard-us-19105.json" },
-    { "id": "application-dashboard-US-19106", "kind": "us", "path": "user-stories/application-dashboard-us-19106.json" },
-    { "id": "application-dashboard-US-19107", "kind": "us", "path": "user-stories/application-dashboard-us-19107.json" },
-    { "id": "TAC-2001-application-dashboard-tile-grid", "kind": "tac", "path": "tacs/tac-2001-application-dashboard-tile-grid.json" },
-    { "id": "TAC-2002-application-dashboard-filter-chrome", "kind": "tac", "path": "tacs/tac-2002-application-dashboard-filter-chrome.json" },
-    { "id": "TAC-2003-application-dashboard-export-handle", "kind": "tac", "path": "tacs/tac-2003-application-dashboard-export-handle.json" },
-    { "id": "ADR-2001-application-dashboard-primary-kpi-enum", "kind": "adr", "path": "adrs/adr-2001-application-dashboard-primary-kpi-enum.json", "recommendedDefault": false, "elicited": true, "standardsTraceClause": "NN/g F-scan; Gestalt proximity" },
-    { "id": "ADR-2002-application-dashboard-timeframe-presets", "kind": "adr", "path": "adrs/adr-2002-application-dashboard-timeframe-presets.json", "recommendedDefault": true, "elicited": true, "standardsTraceClause": "NN/g dashboard design (timeframe defaults)" },
-    { "id": "ADR-2003-application-dashboard-export-formats", "kind": "adr", "path": "adrs/adr-2003-application-dashboard-export-formats.json", "recommendedDefault": true, "elicited": true, "standardsTraceClause": "GOV.UK Design System (download patterns); WCAG 1.3.1 (info and relationships)" }
+    {
+      "id": "application-dashboard-REQ-001",
+      "kind": "req",
+      "path": "requirements/application-dashboard-req-001.json"
+    },
+    {
+      "id": "application-dashboard-REQ-002",
+      "kind": "req",
+      "path": "requirements/application-dashboard-req-002.json"
+    },
+    {
+      "id": "application-dashboard-REQ-003",
+      "kind": "req",
+      "path": "requirements/application-dashboard-req-003.json"
+    },
+    {
+      "id": "application-dashboard-REQ-004",
+      "kind": "req",
+      "path": "requirements/application-dashboard-req-004.json"
+    },
+    {
+      "id": "application-dashboard-REQ-005",
+      "kind": "req",
+      "path": "requirements/application-dashboard-req-005.json"
+    },
+    {
+      "id": "application-dashboard-US-19101",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19101.json"
+    },
+    {
+      "id": "application-dashboard-US-19102",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19102.json"
+    },
+    {
+      "id": "application-dashboard-US-19103",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19103.json"
+    },
+    {
+      "id": "application-dashboard-US-19104",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19104.json"
+    },
+    {
+      "id": "application-dashboard-US-19105",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19105.json"
+    },
+    {
+      "id": "application-dashboard-US-19106",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19106.json"
+    },
+    {
+      "id": "application-dashboard-US-19107",
+      "kind": "us",
+      "path": "user-stories/application-dashboard-us-19107.json"
+    },
+    {
+      "id": "TAC-2001-application-dashboard-tile-grid",
+      "kind": "tac",
+      "path": "tacs/tac-2001-application-dashboard-tile-grid.json"
+    },
+    {
+      "id": "TAC-2002-application-dashboard-filter-chrome",
+      "kind": "tac",
+      "path": "tacs/tac-2002-application-dashboard-filter-chrome.json"
+    },
+    {
+      "id": "TAC-2003-application-dashboard-export-handle",
+      "kind": "tac",
+      "path": "tacs/tac-2003-application-dashboard-export-handle.json"
+    },
+    {
+      "id": "ADR-2001-application-dashboard-primary-kpi-enum",
+      "kind": "adr",
+      "path": "adrs/adr-2001-application-dashboard-primary-kpi-enum.json",
+      "recommendedDefault": false,
+      "elicited": true,
+      "standardsTraceClause": "NN/g F-scan; Gestalt proximity"
+    },
+    {
+      "id": "ADR-2002-application-dashboard-timeframe-presets",
+      "kind": "adr",
+      "path": "adrs/adr-2002-application-dashboard-timeframe-presets.json",
+      "recommendedDefault": true,
+      "elicited": true,
+      "standardsTraceClause": "NN/g dashboard design (timeframe defaults)"
+    },
+    {
+      "id": "ADR-2003-application-dashboard-export-formats",
+      "kind": "adr",
+      "path": "adrs/adr-2003-application-dashboard-export-formats.json",
+      "recommendedDefault": true,
+      "elicited": true,
+      "standardsTraceClause": "GOV.UK Design System (download patterns); WCAG 1.3.1 (info and relationships)"
+    }
   ]
 }

package/blueprints/application-dashboard/contributions/adrs/adr-2001-application-dashboard-primary-kpi-enum.json

@@ -2,15 +2,15 @@
   "adrId": "ADR-2001-application-dashboard-primary-kpi-enum",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "accepted",
   "title": "Elicit the primary KPI kind from a fixed enum (revenue, active-users, error-rate, throughput, custom)",
-  "context": "The primary KPI is the reader's anchor on the dashboard's first fixation. Every applying project already has a primary KPI in the business sense; the problem is that the surface's `data-kpi-kind` attribute either stays free-form (any string) and cross-project comparisons drift, or hard-picks one KPI at the shelf and forces every applying project to relabel. Neither option lands the runtime discipline the pack needs to prove the primary-KPI-top-left rule.",
-  "decision": "The primary-KPI kind is elicited at apply from a fixed enum: `revenue`, `active-users`, `error-rate`, `throughput`, or `custom`. The elicited value lands on the primary tile as `data-kpi-kind`; a `custom` choice carries a `data-kpi-name` attribute with the operator's own short name. The pack asserts the attribute value is one of the enum values (or `custom` with a `data-kpi-name`), the tile is top-left in DOM order and CSS Grid position at every ratified breakpoint. The five enum values cover the shipped shelf's known cases (SaaS revenue dashboards, product-analytics active-users dashboards, SRE error-rate dashboards, throughput-focused ops dashboards, and the custom escape hatch); a new enum value moves the ADR to v1.1.0 with a shelf-wide review.",
+  "context": "The primary KPI is the reader's anchor on the dashboard's first fixation. Every applying project already has a primary KPI in the business sense; the problem is that the surface's `data-kpi-kind` attribute either stays free-form (any string) and cross-project comparisons drift, or hard-picks one KPI at the shelf and forces every applying project to relabel. Neither option lands the runtime discipline the pack needs to prove the primary-kpi-top-left rule.",
+  "decision": "The primary-kpi kind is elicited at apply from a fixed enum: `revenue`, `active-users`, `error-rate`, `throughput`, or `custom`. The elicited value lands on the primary tile as `data-kpi-kind`; a `custom` choice carries a `data-kpi-name` attribute with the operator's own short name. The pack asserts the attribute value is one of the enum values (or `custom` with a `data-kpi-name`), the tile is top-left in DOM order and CSS Grid position at every ratified breakpoint. The five enum values cover the shipped shelf's known cases (SaaS revenue dashboards, product-analytics active-users dashboards, SRE error-rate dashboards, throughput-focused ops dashboards, and the custom escape hatch); a new enum value moves the ADR to v1.1.0 with a shelf-wide review.",
   "consequences": "Applying projects pick from a small, review-worthy set; the pack has a runtime-observable attribute to check; cross-project comparisons on a shelf-wide dashboard registry are trivial. The `custom` value keeps the escape hatch honest: a project with a KPI outside the five stays within the ADR while documenting its own name on `data-kpi-name`.",
   "alternativesConsidered": [
     {
-      "name": "Free-form primary-KPI kind",
+      "name": "Free-form primary-kpi kind",
       "summary": "The attribute accepts any string.",
       "reasonNotChosen": "Every applying project would ship its own label and cross-project reasoning would drift; the pack could not usefully assert a value shape."
     },

package/blueprints/application-dashboard/contributions/adrs/adr-2002-application-dashboard-timeframe-presets.json

@@ -2,7 +2,7 @@
   "adrId": "ADR-2002-application-dashboard-timeframe-presets",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "accepted",
   "title": "Ship three timeframe presets by recommendedDefault with elicited overrides and auto-refresh off unless elicited",
   "context": "Timeframe presets on a dashboard are the single most-touched control; the wrong default (a rolling 24-hour window on a monthly-cycle business) produces a dashboard that is silently wrong at every open. Operators often want their own presets (a fiscal-year window, a shift window). Auto-refresh is one of the most common accessibility and cost defects on shipped dashboards: an unattended refresh runs the fan-out on a hidden tab all day.",

package/blueprints/application-dashboard/contributions/adrs/adr-2003-application-dashboard-export-formats.json

@@ -2,7 +2,7 @@
   "adrId": "ADR-2003-application-dashboard-export-formats",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "accepted",
   "title": "Ship three export formats by recommendedDefault (CSV, PDF, PNG-of-chart) with elicited overrides and PNG delegation to the charts render shell",
   "context": "Export is a legal-and-audit necessity on most shipped dashboards, and the accessibility posture of an export handle is often the last thing anyone reviews. The three most-requested formats are CSV (data extract), PDF (whole-dashboard snapshot), and PNG (one-chart download). SVG, XLSX and a Slack-share button are common project-side additions. A dashboard shell that carries its own PNG generator is a common defect because it produces a chart image that drifts from the shipped chart.",

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 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. 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

@@ -7,9 +7,16 @@
   "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,7 +2,7 @@
   "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).",

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.",

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,7 +16,8 @@
       "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",
@@ -25,11 +26,58 @@
       "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 review.",
+      "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"
 }