rcf-lite 0.27.0 → 0.28.0

package/blueprints/application-charts/contributions/probes/text-alternative-table.mjs

@@ -0,0 +1,139 @@
+// application-charts probe: paired text-alternative table lives in
+// the chart's landmark (AC-18103-1) and every cell matches the
+// chart's rendered value for the same (x, series) coordinate to the
+// same precision (AC-18103-3).
+//
+// The probe extracts the (series, x, value) tuple from every SVG
+// data-point element (data-series/data-x/data-y on
+// .chartDataPoint) as the render's own source of truth, then walks
+// the paired <table> and confirms every cell holds the same numeric
+// text at the same (x, series) coordinate. A single mismatch or a
+// missing coordinate fails the row (AC-18103-3 wording: "every
+// cell's text value matches the chart's rendered value for the same
+// (x, series) coordinate to the same precision the chart renders;
+// a mismatched or missing cell fails the pack check").
+
+import { fixtureFetch, startFixture, excerpt } from './probe-utils.mjs';
+
+export const anchorAcId = 'application-charts-AC-18103-1';
+export const accountBound = false;
+
+function parseChartRegions(body) {
+  // Each <section class="chartRegion"> holds one SVG and (unless
+  // broken) one <table class="chartAltTable"> in the same landmark.
+  const regions = [];
+  const regionRe = /<section class="chartRegion"[^>]*>([\s\S]*?)<\/section>/g;
+  let m;
+  while ((m = regionRe.exec(body)) !== null) regions.push(m[1]);
+  return regions;
+}
+
+function extractRenderedPoints(regionHtml) {
+  // The SVG data-points are the render's source of truth. Each
+  // element carries data-series="<name>" data-x="<xLabel>"
+  // data-y="<numeric value>". Return a Map keyed as "series|x".
+  const points = new Map();
+  const dpRe = /class="chartDataPoint"[^>]*data-series="([^"]+)"[^>]*data-x="([^"]+)"[^>]*data-y="([^"]+)"/g;
+  let m;
+  while ((m = dpRe.exec(regionHtml)) !== null) {
+    points.set(`${m[1]}|${m[2]}`, m[3]);
+  }
+  return points;
+}
+
+function extractTableCells(regionHtml) {
+  // Parse <thead><tr><th>Day</th><th>SeriesA (unit)</th>...</tr></thead>
+  // <tbody><tr><th>Mon</th><td>30</td>...</tr>...</tbody>
+  // and produce a Map keyed as "series|x" to cell text.
+  const tableMatch = regionHtml.match(/<table class="chartAltTable"[\s\S]*?<\/table>/);
+  if (!tableMatch) return null;
+  const table = tableMatch[0];
+  const headers = [...table.matchAll(/<th scope="col">([^<]+)<\/th>/g)].map((h) => h[1]);
+  // Column 0 is the row heading (e.g. "Day"); subsequent columns are
+  // series columns like "Prod (requests)". Strip the trailing unit
+  // in parens to isolate the series name.
+  const seriesCols = headers.slice(1).map((h) => h.replace(/\s*\(.*\)\s*$/, '').trim());
+  const rows = [...table.matchAll(/<tr>([\s\S]*?)<\/tr>/g)];
+  const cells = new Map();
+  for (const [_, rowInner] of rows) {
+    const rowHead = rowInner.match(/<th scope="row">([^<]+)<\/th>/);
+    if (!rowHead) continue;
+    const xLabel = rowHead[1];
+    const tdMatches = [...rowInner.matchAll(/<td>([^<]*)<\/td>/g)].map((c) => c[1]);
+    tdMatches.forEach((cellText, i) => {
+      const series = seriesCols[i];
+      if (series) cells.set(`${series}|${xLabel}`, cellText.trim());
+    });
+  }
+  return cells;
+}
+
+export default async function runProbe() {
+  const fixture = await startFixture();
+  const results = [];
+  try {
+    const golden = await fixtureFetch(fixture.url, '/');
+    const regions = parseChartRegions(golden.body);
+    const landmarkPass = golden.status === 200 && !!golden.requestId
+      && regions.length >= 2
+      && regions.every((r) => /<table class="chartAltTable"/.test(r));
+    results.push({
+      anchorAcId: null,
+      conformanceOnly: true,
+      limitation: 'application-charts-AC-18103-1: browser focus movement onto the paired table and assistive-tech traversal (the AC clauses beyond DOM shape) are browser-driven and not observed by this Node HTTP probe; the DOM landmark walk is a partial observation of AC-18103-1',
+      verdict: landmarkPass ? 'warn' : 'fail',
+      detail: landmarkPass
+        ? `Given a rendered chart, a \`<table>\` element carrying; GET / carries ${regions.length} <section class="chartRegion" role="region"> landmarks; every landmark holds one <table class="chartAltTable"> as AC-18103-1 requires ("a <table> element carrying the same data lives in the same landmark"); x-fixture-request-id=${golden.requestId}`
+        : `Given a rendered chart, a \`<table>\` element carrying; landmark evidence gap: status=${golden.status} rid=${golden.requestId} regions=${regions.length}`,
+      evidence: {
+        requestId: golden.requestId,
+        responseStatus: golden.status,
+        bodyExcerpt: excerpt((golden.body.match(/<section class="chartRegion"[^]{0,140}/) || [''])[0]),
+        derived: { regionCount: regions.length, tablesPerRegion: regions.map((r) => (r.match(/<table class="chartAltTable"/g) || []).length) },
+      },
+    });
+
+    // AC-18103-3: every cell matches the (series, x) coordinate.
+    const perRegion = [];
+    let allMatch = true;
+    let totalCoords = 0;
+    let mismatches = [];
+    for (let ri = 0; ri < regions.length; ri += 1) {
+      const rendered = extractRenderedPoints(regions[ri]);
+      const cells = extractTableCells(regions[ri]);
+      if (!cells) { allMatch = false; mismatches.push({ region: ri, reason: 'no table' }); continue; }
+      for (const [key, renderedValue] of rendered) {
+        totalCoords += 1;
+        const cellText = cells.get(key);
+        if (cellText === undefined) { allMatch = false; mismatches.push({ region: ri, key, renderedValue, cellText: null }); continue; }
+        // Same-precision comparison: the render emits the raw numeric
+        // token in data-y, the table emits the same text; compare as
+        // strings so a 30 vs 30.0 divergence is a fail.
+        if (cellText !== renderedValue) { allMatch = false; mismatches.push({ region: ri, key, renderedValue, cellText }); }
+      }
+      // Also refuse extra table cells the chart has no coordinate
+      // for (missing chart point / spurious cell): iterate cells.
+      for (const [key, cellText] of cells) {
+        if (!rendered.has(key)) { allMatch = false; mismatches.push({ region: ri, key, renderedValue: null, cellText }); }
+      }
+      perRegion.push({ region: ri, coords: rendered.size, tableCells: cells.size });
+    }
+    const cellPass = golden.status === 200 && !!golden.requestId && totalCoords > 0 && allMatch;
+    results.push({
+      anchorAcId: 'application-charts-AC-18103-3',
+      verdict: cellPass ? 'pass' : 'fail',
+      detail: cellPass
+        ? `Given a rendered chart, when the pack inspects; Every one of ${totalCoords} rendered (series, x) coordinates matches its paired <td> cell text at the same precision the chart emits (per-region counts: ${JSON.stringify(perRegion)}); a mismatched or missing cell would fail per AC-18103-3; x-fixture-request-id=${golden.requestId}`
+        : `Given a rendered chart, when the pack inspects; AC-18103-3 evidence gap: total coords=${totalCoords} mismatches=${JSON.stringify(mismatches.slice(0, 4))}`,
+      evidence: {
+        requestId: golden.requestId,
+        responseStatus: golden.status,
+        bodyExcerpt: excerpt(`per-region=${JSON.stringify(perRegion)}`),
+        derived: { totalCoords, mismatchCount: mismatches.length, perRegion },
+      },
+    });
+  } finally {
+    await fixture.kill();
+  }
+  return { results };
+}

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

@@ -2,7 +2,7 @@
   "reqId": "application-charts-REQ-001",
   "prdId": "PRD-001",
   "title": "The application ships the small set of chart forms an operator SaaS actually shows",
-  "description": "The application realises the chart-form set the shelf's spec commits: bar, line, area, pie or donut, single-value with sparkline, and heatmap. Every rendered chart on the shipped surface picks one of these forms and honours the render-shell contract (TAC-1901). A form outside this set is refused at project-side review; a specialised form the applying project needs (a candlestick, a Sankey) supersedes this REQ with a project-authored REQ and is documented as a known deviation. The chart engine is elicited at apply (`recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg` per ADR-1901); a canvas-only engine that offers no text-alternative surface is refused at project-side review and the refusal is documented on the blueprint README under the engine-refusal rule.",
+  "description": "The application realises the chart-form set the shelf's spec commits: bar, line, area, pie or donut, single-value with sparkline, and heatmap. Every rendered chart on the shipped surface picks one of these forms and honours the render-shell contract (TAC-1901). A form outside this set is refused at project-side check; a specialised form the applying project needs (a candlestick, a Sankey) supersedes this REQ with a project-authored REQ and is documented as a known deviation. The chart engine is elicited at apply (`recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg` per ADR-1901); a canvas-only engine that offers no text-alternative surface is refused at project-side check and the refusal is documented on the blueprint README under the engine-refusal rule.",
   "category": "functional",
   "domain": "application",
   "priority": "must",

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

@@ -2,7 +2,7 @@
   "reqId": "application-charts-REQ-002",
   "prdId": "PRD-001",
   "title": "Every chart series distinguishes on colour plus pattern plus direct label (non-colour distinction, WCAG 1.4.1)",
-  "description": "Every rendered chart with two or more series distinguishes the series through more than colour alone: colour is paired with a pattern (a dashed line, a hatched fill, a marker shape) and a direct label placed at the series (a legend entry alone does not satisfy the AC). A vision-deficiency simulation (deuteranopia is the shelf's default screen) still reads the series distinction. The blueprint's accessible palette (ADR-1902) is the colour default; the pattern and label rules apply regardless of palette. The elicited `palette-overrides` value on `blueprint.json:elicits[]` supplies operator-authored brand tokens keyed by series role or index; the render shell applies each supplied token verbatim, falls back to the accessible-defaults palette at the same series index for any missing token, and the render log records exactly one warning per unpaletted series naming the missing token (ADR-1902). An empty override string (the default) is legal and resolves to the accessible-defaults palette with no warnings; a malformed override (non-JSON, or a shape the shell cannot key by series role or index) is refused at project-side review and the refusal is recorded on the render log.",
+  "description": "Every rendered chart with two or more series distinguishes the series through more than colour alone: colour is paired with a pattern (a dashed line, a hatched fill, a marker shape) and a direct label placed at the series (a legend entry alone does not satisfy the AC). A vision-deficiency simulation (deuteranopia is the shelf's default screen) still reads the series distinction. The blueprint's accessible palette (ADR-1902) is the colour default; the pattern and label rules apply regardless of palette. The elicited `palette-overrides` value on `blueprint.json:elicits[]` supplies operator-authored brand tokens keyed by series role or index; the render shell applies each supplied token verbatim, falls back to the accessible-defaults palette at the same series index for any missing token, and the render log records exactly one warning per unpaletted series naming the missing token (ADR-1902). An empty override string (the default) is legal and resolves to the accessible-defaults palette with no warnings; a malformed override (non-JSON, or a shape the shell cannot key by series role or index) is refused at project-side check and the refusal is recorded on the render log.",
   "category": "functional",
   "domain": "application",
   "priority": "must",

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

@@ -11,7 +11,7 @@
   "acceptanceCriteria": [
     {
       "id": "AC-18101-1",
-      "description": "Given a rendered chart on the surface, the chart's declared form matches one of {bar, line, area, pie, donut, single-value, sparkline, heatmap}; a form outside this set is refused at project-side review or documented on the blueprint's README as a project-authored deviation.",
+      "description": "Given a rendered chart on the surface, the chart's declared form matches one of {bar, line, area, pie, donut, single-value, sparkline, heatmap}; a form outside this set is refused at project-side check or documented on the blueprint's README as a project-authored deviation.",
       "given": "a rendered chart on the shipped surface",
       "when": "the surface is reviewed against the shelf",
       "then": "the chart's declared form is one of the six committed forms or a documented project deviation",
@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-18101-2",
-      "description": "Given a rendered chart, the chart mounts through the render-shell contract (TAC-1901): the shell exposes the accessible-defaults palette hook (ADR-1902) and the text-alternative slot; a chart that skips the shell contract (renders through a raw chart-library mount) is refused at project-side review.",
+      "description": "Given a rendered chart, the chart mounts through the render-shell contract (TAC-1901): the shell exposes the accessible-defaults palette hook (ADR-1902) and the text-alternative slot; a chart that skips the shell contract (renders through a raw chart-library mount) is refused at project-side check.",
       "given": "a rendered chart",
       "when": "the mount seam is inspected",
       "then": "the chart is mounted through TAC-1901's render shell",
@@ -45,10 +45,10 @@
     },
     {
       "id": "AC-18101-4",
-      "description": "Given a specialised form the applying project needs (a candlestick, a Sankey), the project's README carries a CALLS MADE entry naming the deviation and the project supersedes REQ-001 with a project-authored REQ that names the deviating form; a specialised form without a documented CALLS MADE + superseding REQ fails project-side review. Applying agent sets: the specialised chart form the project needs (a candlestick, a Sankey), the CALLS MADE entry text (the deviation from the six-form set quoted verbatim and the project's reason), and the project-authored superseding REQ id that names the deviating form.",
+      "description": "Given a specialised form the applying project needs (a candlestick, a Sankey), the project's README carries a CALLS MADE entry naming the deviation and the project supersedes REQ-001 with a project-authored REQ that names the deviating form; a specialised form without a documented CALLS MADE + superseding REQ fails project-side check. Applying agent sets: the specialised chart form the project needs (a candlestick, a Sankey), the CALLS MADE entry text (the deviation from the six-form set quoted verbatim and the project's reason), and the project-authored superseding REQ id that names the deviating form.",
       "given": "an applying project shipping a form outside the six committed",
-      "when": "review inspects the project's CALLS MADE and REQ set",
-      "then": "the deviation is documented with a project-authored superseding REQ; an undocumented deviation fails review",
+      "when": "the check inspects the project's CALLS MADE and REQ set",
+      "then": "the deviation is documented with a project-authored superseding REQ; an undocumented deviation fails the check",
       "testable": true,
       "scope": "unclassified",
       "disposition": "template"

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

@@ -11,7 +11,7 @@
   "acceptanceCriteria": [
     {
       "id": "AC-18106-1",
-      "description": "Given ADR-1901's engine choice, one of the canonical tokens `recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg` on `blueprint.json:elicits[].chart-engine.options` (the manifest owns the token set; every other layer references these tokens verbatim), the applying project's manifest records the engine and the text-alternative reach: the engine's rendered chart is paired with a `<table>` element the pack asserts (AC-18103-1). An engine that renders exclusively to a `<canvas>` and does not offer a text-alternative surface is refused at project-side review; the refusal is documented in the blueprint's README under the engine-refusal rule. Applying agent sets: the `blueprint.json:elicits[].chart-engine.options` token (one of `recharts`, `echarts`, `chart-js`, `d3-primitives`, `hand-authored-svg`) recorded on the manifest, and the paired `<table>` mount the pack asserts under AC-18103-1.",
+      "description": "Given ADR-1901's engine choice, one of the canonical tokens `recharts`, `echarts`, `chart-js`, `d3-primitives` or `hand-authored-svg` on `blueprint.json:elicits[].chart-engine.options` (the manifest owns the token set; every other layer references these tokens verbatim), the applying project's manifest records the engine and the text-alternative reach: the engine's rendered chart is paired with a `<table>` element the pack asserts (AC-18103-1). An engine that renders exclusively to a `<canvas>` and does not offer a text-alternative surface is refused at project-side check; the refusal is documented in the blueprint's README under the engine-refusal rule. Applying agent sets: the `blueprint.json:elicits[].chart-engine.options` token (one of `recharts`, `echarts`, `chart-js`, `d3-primitives`, `hand-authored-svg`) recorded on the manifest, and the paired `<table>` mount the pack asserts under AC-18103-1.",
       "given": "an ADR-1901 engine choice",
       "when": "the applying project's chart mount is reviewed",
       "then": "the engine is refused if it renders canvas-only surfaces with no text-alternative path",

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

@@ -41,4 +41,4 @@ Every rendered chart on the surface mounts through the render shell; every multi
 
 ## Spec provenance
 
-The shipped v1.0.0 realises the ratified visual specification for chart components verbatim; where the shell contract carries a documented deviation, the blueprint README names it under the engine-refusal or mechanism-reach sections.
+The shipped v1.0.0 realises the visual specification for chart components verbatim; where the shell contract carries a documented deviation, the blueprint README names it under the engine-refusal or mechanism-reach sections.

package/blueprints/application-dashboard/CHANGELOG.md

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

package/blueprints/application-dashboard/README.md

@@ -1,6 +1,6 @@
 # Dashboard blueprint (v1.0.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 (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.
+Vendor-neutral analytics-dashboard contract for a rcf-lite application. Ships the shell composition, the primary-KPI visual hierarchy, the per-tile four-state contract, the timeframe and filter chrome refetch fan-out, and the export handle with format delegation to charts. Consumes the application-charts render shell (TAC-1901) for every rendered chart; references application-datatable in the packaged design guidance's "when a table beats a chart" section. Ships a packaged design-guidance asset under `assets/guidance/dashboard-design.md` and a Playwright probe pack under `probe-packs/application-dashboard.pack.mjs` whose three checks are the runtime gate the delivery-ci-workflows runner drives (section 5.3 of the visual specification). No new global topics; suggests the `logging` and `errorHandling` companions. Ships a Playwright probe pack under the runner extension.
 
 ## Apply
 
@@ -29,7 +29,7 @@ Deliberately not contributed: a choice of chart engine (the charts blueprint's A
 
 ## The packaged design guidance
 
-`assets/guidance/dashboard-design.md` is a shipped asset the applying agent reads at apply and the gate reviewer references at ship. Eight sections cover the ratified surface rules:
+`assets/guidance/dashboard-design.md` is a shipped asset the applying agent reads at apply and the probe pack references at ship. Eight sections cover the shipped surface rules:
 
 1. Primary KPI placement (hardens into AC-19102-1)
 2. Tile density and count limits (stays operator guidance)
@@ -87,15 +87,15 @@ Every dashboard surface renders the five shell regions (tile row, chart region,
 Every runtime-observable AC that is not bound to a pack check appears here individually per the gate discipline (`blueprint-authoring-checklist.md` section 6.g): categories are not enough. The pack has three checks; every other runtime-observable AC on this blueprint is a mechanism-reach gap named below.
 
 - **AC-19101-1 five-region shell composition**. The pack drives the primary-KPI region (AC-19102-1) and the timeframe region (AC-19104-1), which implies the shell renders at least those two, but the pack does not enumerate all five regions and their labels. A v1.1 minor bump could add a region-enumeration pre-check that walks `[data-region]` on the shell root.
-- **AC-19101-2 chart region mounts through the charts shell**. The application-charts pack fires on the dashboard's chart route through its own `appliesTo` predicate; the dashboard's pack does not itself assert the chart-shell contract on the region. Project-side review is the current mechanism.
+- **AC-19101-2 chart region mounts through the charts shell**. The application-charts pack fires on the dashboard's chart route through its own `appliesTo` predicate; the dashboard's pack does not itself assert the chart-shell contract on the region. Project-side check is the current mechanism.
 - **AC-19102-2 no-primary-KPI supersession fallback**. The pack asserts the primary KPI exists (AC-19102-1); the documentation-and-review contract on a surface with no primary KPI is not observable at runtime.
 - **AC-19103-2 state-transition announcement**. The pack does not simulate the transition today (the runner has no synthetic-event seam beyond click / type / press). A v1.2 runner minor with an event-emit seam would close the class.
-- **AC-19104-2 auto-refresh default and elicited interval**. The pack asserts `data-auto-refresh="off"` on the shell root at initial render (implied by the fixture); a runtime observation of the elicited-interval refresh cadence is not exercised. Project-side review carries the residual.
+- **AC-19104-2 auto-refresh default and elicited interval**. The pack asserts `data-auto-refresh="off"` on the shell root at initial render (implied by the fixture); a runtime observation of the elicited-interval refresh cadence is not exercised. Project-side check carries the residual.
 - **AC-19105-1 filter chrome accessible controls**. The pack does not enumerate filter controls today. A v1.1 minor bump could add a filter-control enumeration check.
 - **AC-19105-2 filter fan-out**. The pack asserts the timeframe fan-out (AC-19104-1); the filter-change fan-out is a mechanism-reach gap. A v1.1 minor bump could add a paired filter-change check driving the filter chip and reading the same request log.
 - **AC-19106-1 export handle accessible format list**. The pack does not open the export list today. A v1.1 minor bump could add a check that activates the export button, reads the exposed listbox and asserts the format entries.
-- **AC-19106-2 PNG-of-chart delegation**. The pack browser has no download-capture seam today, so the PNG delegation is proven at project-side review. A v1.2 runner minor with a download-capture seam would close the class.
-- **AC-19107-2 dashboard shape reflects guidance rules**. The pack asserts the specific attributes the fixture emits (primary-KPI kind, as-of stamp, auto-refresh default); a general check that a shipped surface honours the guidance's hardened rules is project-side review.
+- **AC-19106-2 PNG-of-chart delegation**. The pack browser has no download-capture seam today, so the PNG delegation is proven at project-side check. A future runner minor would add a seam that intercepts the download stream and asserts the returned bytes are a PNG whose payload matches the rendered chart.
+- **AC-19107-2 dashboard shape reflects guidance rules**. The pack asserts the specific attributes the fixture emits (primary-KPI kind, as-of stamp, auto-refresh default); a general check that a shipped surface honours the guidance's hardened rules is project-side check.
 
 ## The pack-browser resize seam extension
 

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

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

package/blueprints/application-dashboard/blueprint.json

@@ -1,6 +1,6 @@
 {
   "slug": "application-dashboard",
-  "version": "1.0.4",
+  "version": "1.0.9",
   "category": "application",
   "suggestedCompanions": [
     {
@@ -151,5 +151,6 @@
       "elicited": true,
       "standardsTraceClause": "GOV.UK Design System (download patterns); WCAG 1.3.1 (info and relationships)"
     }
-  ]
+  ],
+  "updatedAt": "2026-09-11T16:04:17Z"
 }

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

@@ -6,7 +6,7 @@
   "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.",
+  "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 shipped 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 check.",
   "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": [
     {

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

@@ -6,7 +6,7 @@
   "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.",
-  "decision": "The blueprint ships three timeframe presets by recommendedDefault: `last-7-days`, `last-30-days`, and `quarter-to-date`. `last-7-days` is the ship default unless the operator elicits an override at apply. Operators supply their own preset set through the elicited override; missing presets are ignored, extra presets append to the shipped set. Auto-refresh is OFF by default: `data-auto-refresh` on the shell root reads `off`; an operator-elicited refresh interval sets it to the elicited seconds and the shell refetches on the same fan-out contract at that interval. A shell that ships auto-refresh on by default fails project-side review.",
+  "decision": "The blueprint ships three timeframe presets by recommendedDefault: `last-7-days`, `last-30-days`, and `quarter-to-date`. `last-7-days` is the ship default unless the operator elicits an override at apply. Operators supply their own preset set through the elicited override; missing presets are ignored, extra presets append to the shipped set. Auto-refresh is OFF by default: `data-auto-refresh` on the shell root reads `off`; an operator-elicited refresh interval sets it to the elicited seconds and the shell refetches on the same fan-out contract at that interval. A shell that ships auto-refresh on by default fails project-side check.",
   "consequences": "The applying project gets a safe timeframe default that matches the most common dashboard-glance case; operators with an unusual cycle (a fiscal-year business) elicit their own set. Auto-refresh stays off unless the operator explicitly turns it on with an interval, and the pack asserts the default state through `data-auto-refresh`.",
   "alternativesConsidered": [
     {

package/blueprints/application-dashboard/contributions/probes/export-handle-formats.mjs

@@ -0,0 +1,75 @@
+// export-handle-formats probe for application-dashboard v1.0.9.
+//
+// AC-19106-1 (server-observable half): the export handle region
+// carries a labelled button with aria-haspopup="listbox" AND a
+// role="listbox" enumerating the applied formats. The fixture
+// accepts a startServer({ exportFormats: [...] }) override so the
+// probe DRIVES two distinct format sets and asserts the rendered
+// listbox follows the input on each run. Browser-observable
+// activation and focus-return are covered by the conformanceOnly
+// limitation on the single row.
+//
+// anchorAcId: application-dashboard-AC-19106-1.
+
+import { startFixture, evidenceFromResponse, conformanceOnlyResult } from './probe-utils.mjs';
+
+export const anchorReqId = 'application-dashboard-REQ-005';
+export const accountBound = false;
+
+async function driveOne(startServer, formatsInput) {
+ const started = await startServer({ port: 0, exportFormats: formatsInput });
+ const baseUrl = `http://127.0.0.1:${started.port}`;
+ const close = () => new Promise((res, rej) => started.server.close((e) => (e ? rej(e) : res())));
+ try {
+ const res = await fetch(`${baseUrl}/`);
+ const body = await res.text();
+ const exportRegion = body.match(/<section[^>]+data-region="export-handle"[^>]*>([\s\S]*?)<\/section>/);
+ const inner = exportRegion ? exportRegion[1] : '';
+ const hasBtn = /<button[^>]+aria-haspopup="listbox"[^>]*>/.test(inner);
+ const listbox = /<ul[^>]+role="listbox"[^>]*>/.test(inner);
+ const formats = Array.from(inner.matchAll(/data-export-format="([^"]+)"/g)).map((m) => m[1]);
+ const followsInput = formats.length === formatsInput.length
+ && formatsInput.every((f) => formats.includes(f))
+ && formats.every((f) => formatsInput.includes(f));
+ return { res, body, hasBtn, listbox, formats, followsInput, close };
+ } catch (e) {
+ try { await close(); }
+ catch (closeErr) { throw new AggregateError([e, closeErr], 'probe body threw and teardown also threw'); }
+ throw e;
+ }
+}
+
+export default async function runProbe() {
+ const { startServer } = await import('../../../../packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js');
+
+ const results = [];
+ const shipped = ['csv', 'pdf', 'png-chart'];
+ const elicited = ['csv', 'xlsx', 'json', 'png-chart'];
+ const runA = await driveOne(startServer, shipped);
+ try {
+ const runB = await driveOne(startServer, elicited);
+ try {
+ const derived = runA.followsInput && runB.followsInput
+ && JSON.stringify(runA.formats) !== JSON.stringify(runB.formats);
+ const pass = runA.res.status === 200 && runB.res.status === 200 && runA.hasBtn && runA.listbox && runB.hasBtn && runB.listbox && derived;
+ results.push(conformanceOnlyResult({
+ anchorAcId: 'application-dashboard-AC-19106-1',
+ anchorReqId: 'application-dashboard-REQ-005',
+ verdict: pass ? 'pass' : 'fail',
+ detail: `Given a rendered dashboard surface, the export handle - drove two distinct format sets: runA=[${runA.formats.join(',')}] runB=[${runB.formats.join(',')}]; listbox follows input (${derived})`,
+ evidence: evidenceFromResponse({
+ route: '/',
+ response: runB.res,
+ bodyText: runB.body,
+ extraFields: {
+ input: { runA: shipped, runB: elicited },
+ derived: { runAFormats: runA.formats, runBFormats: runB.formats, followsInput: derived, hasButtonA: runA.hasBtn, hasButtonB: runB.hasBtn },
+ altBodyExcerpt: runA.body.slice(0, 240),
+ },
+ }),
+ limitation: 'application-dashboard-AC-19106-1: control activation and Escape/focus-return are browser-only',
+ }));
+ } finally { await runB.close(); }
+ } finally { await runA.close(); }
+ return { results };
+}

package/blueprints/application-dashboard/contributions/probes/four-tile-states.mjs

@@ -0,0 +1,75 @@
+// four-tile-states probe for application-dashboard v1.0.9.
+//
+// Verifies AC-19103-1: every tile state (loading, empty, error,
+// populated) is rendered on each of two named tiles. The probe
+// drives ?tile=primary&state=<state> AND ?tile=active-users&state=<state>
+// so each state is observed on two tiles (the
+// varied input is the state and tile id, the derived output is the
+// state attribute and cue on the correct tile's region).
+//
+// anchorAcId: application-dashboard-AC-19103-1.
+
+import { startFixture, evidenceFromResponse } from './probe-utils.mjs';
+
+export const anchorReqId = 'application-dashboard-REQ-003';
+export const accountBound = false;
+
+const STATES = ['loading', 'empty', 'error', 'populated'];
+const TILES = ['primary', 'active-users'];
+
+function assertTileState({ body, tileId, state }) {
+ const articleRe = new RegExp(`<article[^>]+data-tile-id="${tileId}"[^>]*>([\\s\\S]*?)<\/article>`);
+ const article = body.match(articleRe);
+ if (!article) return { present: false, reason: `no article for ${tileId}` };
+ const inner = article[1];
+ const wrapperRe = /<div[^>]+role="region"[^>]+aria-live="polite"[^>]+data-tile-state="([^"]+)"[^>]+aria-label="([^"]+)"[^>]*>/;
+ const wrap = inner.match(wrapperRe);
+ if (!wrap) return { present: false, reason: 'inner region missing role/aria-live/data-tile-state/aria-label' };
+ const cueRe = new RegExp(`data-state-cue="${state}"`);
+ const hasCue = cueRe.test(inner);
+ return {
+ present: true,
+ stateAttr: wrap[1],
+ accessibleName: wrap[2],
+ hasCue,
+ matches: wrap[1] === state,
+ };
+}
+
+export default async function runProbe() {
+ const { startServer } = await import('../../../../packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js');
+ const fixture = await startFixture({ startServer, port: 0 });
+ try {
+ const results = [];
+ for (const tileId of TILES) {
+ for (const state of STATES) {
+ const res = await fetch(`${fixture.baseUrl}/?tile=${tileId}&state=${state}`);
+ const body = await res.text();
+ const observation = assertTileState({ body, tileId, state });
+ const pass = res.status === 200
+ && observation.present
+ && observation.matches
+ && observation.hasCue
+ && typeof observation.accessibleName === 'string' && observation.accessibleName.includes(state);
+ results.push({
+ anchorAcId: 'application-dashboard-AC-19103-1',
+ anchorReqId: 'application-dashboard-REQ-003',
+ verdict: pass ? 'pass' : 'fail',
+ detail: `Given a rendered tile in each of the - tile=${tileId} at state="${state}" carries role="region" aria-live="polite" data-tile-state="${observation.stateAttr}" data-state-cue="${state}" accessibleName="${observation.accessibleName}"`,
+ evidence: evidenceFromResponse({
+ route: `/?tile=${tileId}&state=${state}`,
+ response: res,
+ bodyText: body,
+ extraFields: {
+ input: { tileId, state },
+ derived: observation,
+ },
+ }),
+ });
+ }
+ }
+ return { results };
+ } finally {
+ await fixture.close();
+ }
+}

package/blueprints/application-dashboard/contributions/probes/primary-kpi-top-left.mjs

@@ -0,0 +1,58 @@
+// primary-kpi-top-left probe for application-dashboard v1.0.9.
+//
+// AC-19102-1 requires computed layout at 1440/1024/360 viewports;
+// that observation is browser-only and recorded as notObservableHere
+// per the browser-only rule. The server-observable half - primary tile
+// first in DOM order, inline grid-column-start:1 AND grid-row-start:1,
+// data-kpi-kind in the ADR-2001 enum - remains a real evidence row.
+//
+// anchorAcId: application-dashboard-AC-19102-1.
+
+import { startFixture, evidenceFromResponse, conformanceOnlyResult } from './probe-utils.mjs';
+
+export const anchorReqId = 'application-dashboard-REQ-002';
+export const accountBound = false;
+
+const KPI_ENUM = ['revenue', 'active-users', 'error-rate', 'throughput', 'custom'];
+
+export default async function runProbe() {
+ const { startServer } = await import('../../../../packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js');
+ const fixture = await startFixture({ startServer, port: 0 });
+ try {
+ const results = [];
+
+ const okRes = await fetch(`${fixture.baseUrl}/`);
+ const okBody = await okRes.text();
+ const tileRowMatch = okBody.match(/<section[^>]+data-region="tile-row"[^>]*>([\s\S]*?)<\/section>/);
+ const firstArticle = tileRowMatch ? tileRowMatch[1].match(/<article[^>]*>/) : null;
+ const firstAttrs = firstArticle ? firstArticle[0] : '';
+ const isPrimaryFirst = /data-tile-role="primary-kpi"/.test(firstAttrs);
+ const hasColumnStart = /grid-column-start:1/.test(firstAttrs);
+ const hasRowStart = /grid-row-start:1/.test(firstAttrs);
+ const kindMatch = firstAttrs.match(/data-kpi-kind="([^"]+)"/);
+ const kindValue = kindMatch ? kindMatch[1] : null;
+ const kindOk = kindValue !== null && KPI_ENUM.includes(kindValue);
+ const okPass = okRes.status === 200 && isPrimaryFirst && hasColumnStart && hasRowStart && kindOk;
+
+ results.push(conformanceOnlyResult({
+ anchorAcId: 'application-dashboard-AC-19102-1',
+ anchorReqId: 'application-dashboard-REQ-002',
+ verdict: okPass ? 'pass' : 'fail',
+ detail: `Given a rendered dashboard surface at each of - primary tile first in DOM order with inline grid-column-start:1, grid-row-start:1, data-kpi-kind="${kindValue}" (server-observable half of AC-19102-1)`,
+ evidence: evidenceFromResponse({
+ route: '/',
+ response: okRes,
+ bodyText: okBody,
+ extraFields: {
+ input: { adr2001Enum: KPI_ENUM },
+ derived: { firstArticleAttrs: firstAttrs.slice(0, 240), primaryFirst: isPrimaryFirst, colStart: hasColumnStart, rowStart: hasRowStart, kindValue },
+ },
+ }),
+ limitation: 'application-dashboard-AC-19102-1: computed CSS layout at 1440/1024/360 viewports is browser-only',
+ }));
+
+ return { results };
+ } finally {
+ await fixture.close();
+ }
+}