rcf-lite 0.27.0 → 0.28.0

package/blueprints/application-dashboard/contributions/probes/probe-utils.mjs

@@ -0,0 +1,177 @@
+// Shared helpers for application-dashboard probes.
+//
+// The engine under probe is the sample-app fixture at
+// packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js. The
+// fixture stamps an x-fixture-request-id header on every response as
+// part of its own request pipeline (no probe-side monkey-patch), so
+// the identifier the probe records is the identifier the engine
+// itself issued. Probes call the fixture over real HTTP via node's
+// fetch, vary inputs, assert derived outputs, and record the
+// request-id, status, body excerpt, the varied input and the derived
+// output as evidence on every result row.
+// No account-bound branch: the engine is a local fixture, not a
+// third-party account, so no CI_HAS_* gate is invented. Every env
+// var this pack reads is declared on the fixture README.
+
+import { mkdir, writeFile } from 'node:fs/promises';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const HERE = dirname(fileURLToPath(import.meta.url));
+export const PROJECT_ROOT = resolve(HERE, '..', '..', '..', '..');
+export const FIXTURE_DIR = resolve(PROJECT_ROOT, 'packages/rcf-lite/test/fixtures/probe-pack-application-dashboard');
+export const REPORT_DIR = resolve(PROJECT_ROOT, '.rcf/reports/blueprints/application-dashboard');
+
+export const DEFAULT_PORT = 0;
+
+export function aggregate(results) {
+  if (!Array.isArray(results) || results.length === 0) return 'fail';
+  if (results.some((r) => r.verdict === 'fail')) return 'fail';
+  if (results.some((r) => r.verdict === 'warn')) return 'warn';
+  return 'pass';
+}
+
+// Empty results never pass: a synthesised row is emitted with an actionable detail and its
+// own evidence object recording the empty condition so the row is
+// not a naked verdict scalar.
+export function normaliseResults(results) {
+  if (!Array.isArray(results) || results.length === 0) {
+    return [{
+      anchorReqId: 'unknown',
+      verdict: 'fail',
+      detail: 'no checks ran',
+      evidence: {
+        reason: 'empty-results',
+        route: 'n/a',
+        status: 0,
+        xFixtureRequestId: null,
+        bodyExcerpt: '',
+      },
+    }];
+  }
+  return results;
+}
+
+export async function writeReport({ probeName, engine, results, extra }) {
+  await mkdir(REPORT_DIR, { recursive: true });
+  const report = {
+    slug: 'application-dashboard',
+    probeName,
+    runAt: new Date().toISOString(),
+    engine,
+    results,
+    aggregateVerdict: aggregate(results),
+    ...(extra ?? {}),
+  };
+  const path = resolve(REPORT_DIR, `${probeName}.json`);
+  await writeFile(path, JSON.stringify(report, null, 2) + '\n', 'utf8');
+  return { report, path };
+}
+
+// Starts the fixture on an ephemeral port (or PROBE_PORT when set)
+// and returns { server, port, baseUrl, close }. The close helper
+// rejects when the underlying close callback carries an error;
+// swallowing a teardown error would hide a boundary failure.
+export async function startFixture({ startServer, port } = {}) {
+  const resolvedPort = typeof port === 'number'
+    ? port
+    : Number(process.env.PROBE_PORT ?? DEFAULT_PORT);
+  const started = await startServer({ port: resolvedPort });
+  return {
+    server: started.server,
+    port: started.port,
+    baseUrl: `http://127.0.0.1:${started.port}`,
+    close: () => new Promise((res, rej) => started.server.close((err) => {
+      if (err) rej(err);
+      else res();
+    })),
+  };
+}
+
+// Reads a distinctive slice of a response body: the first N chars
+// so the report carries a body excerpt alongside the header id.
+export function bodyExcerpt(text, max = 240) {
+  if (text == null) return '';
+  const s = typeof text === 'string' ? text : String(text);
+  return s.length > max ? s.slice(0, max) + '...' : s;
+}
+
+// Records the positive-evidence shape on a probe result. Every row
+// carries route, status, the request id the fixture stamped, and a
+// body excerpt; the caller may extend the object with the varied
+// input and the derived output for that row.
+export function evidenceFromResponse({ route, response, bodyText, extraFields }) {
+  return {
+    route,
+    status: response.status,
+    xFixtureRequestId: response.headers.get('x-fixture-request-id') || null,
+    bodyExcerpt: bodyExcerpt(bodyText),
+    ...(extraFields ?? {}),
+  };
+}
+
+export async function runShim(probeName, engine, mainFn) {
+  try {
+    const outcome = (await mainFn()) ?? { results: [] };
+    const { results, extra } = outcome;
+    const { report, path } = await writeReport({ probeName, engine, results: normaliseResults(results), extra });
+    process.stdout.write(JSON.stringify(report, null, 2) + '\n');
+    process.stdout.write(`report written to ${path}\n`);
+    if (report.aggregateVerdict !== 'pass') process.exitCode = 1;
+  } catch (err) {
+    const results = [{
+      anchorReqId: 'unknown',
+      verdict: 'fail',
+      detail: `probe threw: ${err && err.message ? err.message : String(err)}`,
+      evidence: {
+        reason: 'probe-threw',
+        route: 'n/a',
+        status: 0,
+        xFixtureRequestId: null,
+        bodyExcerpt: err && err.stack ? String(err.stack).slice(0, 240) : '',
+      },
+    }];
+    const { report, path } = await writeReport({ probeName, engine, results });
+    process.stdout.write(JSON.stringify(report, null, 2) + '\n');
+    process.stderr.write(`probe error: ${err && err.stack ? err.stack : String(err)}\n`);
+    process.stderr.write(`report written to ${path}\n`);
+    process.exitCode = 1;
+  }
+}
+
+// Browser-observable properties are AMBER on the shelf by ruling.
+// A row that names such a property is recorded as notObservableHere
+// carrying an object with the AC id and a reason; the tally script
+// reads notObservableHere.ac to accept the row.
+export function notObservableHereResult({ ac, anchorAcId, detail, reason, evidence } = {}) {
+  // A notObservableHere row anchors nothing else: no anchorAcId,
+  // no anchorReqId - only notObservableHere.ac.
+  const acId = ac || anchorAcId;
+  return {
+    verdict: 'pass',
+    notObservableHere: {
+      ac: acId,
+      reason: reason || 'not observable on server-side probe pack; needs a browser-driven runner',
+    },
+    detail: detail || 'not observable on server-side probe pack',
+    evidence: {
+      reason: reason || 'not observable here; needs a browser-driven probe runner',
+      ...(evidence || {}),
+    },
+  };
+}
+
+// A row that keeps a real observation but records that the
+// observation only covers part of an AC uses conformanceOnly +
+// limitation carrying the AC id and the property not observed.
+export function conformanceOnlyResult({ anchorAcId, anchorReqId, verdict, detail, evidence, limitation }) {
+  return {
+    ...(anchorAcId ? { anchorAcId } : {}),
+    ...(anchorReqId ? { anchorReqId } : {}),
+    verdict: verdict || 'pass',
+    conformanceOnly: true,
+    limitation: limitation || 'browser-observable property not asserted from the server-side probe',
+    detail,
+    evidence,
+  };
+}

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

@@ -0,0 +1,4 @@
+import runProbe from './export-handle-formats.mjs';
+import { runShim } from './probe-utils.mjs';
+const engine = { kind: 'application-dashboard-fixture', server: 'packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js' };
+runShim('export-handle-formats', engine, runProbe);

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

@@ -0,0 +1,4 @@
+import runProbe from './four-tile-states.mjs';
+import { runShim } from './probe-utils.mjs';
+const engine = { kind: 'application-dashboard-fixture', server: 'packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js' };
+runShim('four-tile-states', engine, runProbe);

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

@@ -0,0 +1,4 @@
+import runProbe from './primary-kpi-top-left.mjs';
+import { runShim } from './probe-utils.mjs';
+const engine = { kind: 'application-dashboard-fixture', server: 'packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js' };
+runShim('primary-kpi-top-left', engine, runProbe);

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

@@ -0,0 +1,4 @@
+import runProbe from './shell-five-regions.mjs';
+import { runShim } from './probe-utils.mjs';
+const engine = { kind: 'application-dashboard-fixture', server: 'packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/server.js' };
+runShim('shell-five-regions', engine, runProbe);

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

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

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

@@ -2,7 +2,7 @@
   "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. 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.",
+  "description": "The tile row's primary KPI carries a top-left placement the reader reaches first, on the NN/g F-scan of the surface, at every shipped breakpoint (1440, 1024, 360). At 1440 and 1024 the primary KPI is the first tile in DOM order and its computed CSS Grid column-start is 1 and row-start is 1; at 360 the tile row reflows to one column and the primary KPI is the first tile in DOM order and its row-start is 1. The tile carries a `data-tile-role=\"primary-kpi\"` attribute and a `data-kpi-kind` attribute whose value is one of the ADR-2001 enum values (revenue, active-users, error-rate, throughput, custom). A dashboard that ships no primary KPI tile fails this REQ at project-side check; a dashboard whose primary KPI is not top-left at any of the three breakpoints fails the pack check AC-19102-1. When the elicited `primary-kpi-kind` is `custom` the tile also carries a `data-kpi-name` attribute whose value is the operator-elicited `primary-kpi-custom-name` short name.",
   "category": "functional",
   "domain": "application",
   "priority": "must",

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

@@ -2,7 +2,7 @@
   "reqId": "application-dashboard-REQ-003",
   "prdId": "PRD-001",
   "title": "Every tile honours a four-state contract with distinct visuals, role region, aria-live polite, and non-colour distinction",
-  "description": "Every tile on the shell renders one of four states at any moment: loading, empty, error, populated. Each state carries a distinct visual (a skeleton stripe or spinner for loading, a labelled empty-state block for empty, a labelled error block with the recorded reason for error, and the actual metric for populated). Each tile wraps its content in `role=\"region\"` with an `aria-live=\"polite\"` announcer that reads the state transition on change. The state distinction combines a visual cue and a text label (non-colour distinction, WCAG 1.4.1): the state's visual is not colour-only, and the state's accessible name reads `<tile title>, <state>` on entry. A tile that renders no visible state (a blank tile) fails REQ-003 at project-side review; a tile that carries state-only through colour fails the pack check AC-19103-1.",
+  "description": "Every tile on the shell renders one of four states at any moment: loading, empty, error, populated. Each state carries a distinct visual (a skeleton stripe or spinner for loading, a labelled empty-state block for empty, a labelled error block with the recorded reason for error, and the actual metric for populated). Each tile wraps its content in `role=\"region\"` with an `aria-live=\"polite\"` announcer that reads the state transition on change. The state distinction combines a visual cue and a text label (non-colour distinction, WCAG 1.4.1): the state's visual is not colour-only, and the state's accessible name reads `<tile title>, <state>` on entry. A tile that renders no visible state (a blank tile) fails REQ-003 at project-side check; a tile that carries state-only through colour fails the pack check AC-19103-1.",
   "category": "functional",
   "domain": "application",
   "priority": "must",

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

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

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

@@ -28,8 +28,8 @@
       "description": "PNG-of-chart export generation delegates to the charts shell; the dashboard export handle carries no PNG generator of its own."
     }
   ],
-  "tradeoffs": "The three shipped formats (CSV, PDF, PNG-of-chart) cover the common dashboard export cases; ADR-2003's elicited override handles SVG, XLSX and any operator-specific format. The delegation to the charts shell means a project that ships a bespoke chart engine outside the render shell needs a PNG output path of its own; the export handle names the residual under project-side review.",
-  "notes": "Known mechanism-reach gap: the pack browser has no download-capture seam today, so AC-19106-2 (PNG delegation) is proven at project-side review, not through the shipped pack. The README names it individually.",
+  "tradeoffs": "The three shipped formats (CSV, PDF, PNG-of-chart) cover the common dashboard export cases; ADR-2003's elicited override handles SVG, XLSX and any operator-specific format. The delegation to the charts shell means a project that ships a bespoke chart engine outside the render shell needs a PNG output path of its own; the export handle names the residual under project-side check.",
+  "notes": "Known mechanism-reach gap: the pack browser has no download-capture seam today, so AC-19106-2 (PNG delegation) is proven at project-side check, not through the shipped pack. The README names it individually.",
   "createdAt": "2026-09-04T22:10:00Z",
   "updatedAt": "2026-09-04T22:10:00Z"
 }

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

@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-19101-2",
-      "description": "Given the shell's chart region, the rendered chart mounts through the application-charts render shell (TAC-1901): the chart region contains at least one `section.chartRegion[role=\"region\"]` element carrying the shape the application-charts pack asserts on (an `svg.chartSvg` and a paired `<table>` element in the same landmark). A chart region that renders a chart outside the render shell fails project-side review.",
+      "description": "Given the shell's chart region, the rendered chart mounts through the application-charts render shell (TAC-1901): the chart region contains at least one `section.chartRegion[role=\"region\"]` element carrying the shape the application-charts pack asserts on (an `svg.chartSvg` and a paired `<table>` element in the same landmark). A chart region that renders a chart outside the render shell fails project-side check.",
       "given": "the rendered chart region",
       "when": "the mount seam is inspected",
       "then": "the chart mounts through the application-charts render shell",
@@ -31,7 +31,7 @@
     },
     {
       "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.",
+      "description": "Given a rendered dashboard surface, when a required region is omitted from the DOM (no export handle, no filter chrome, no timeframe picker), the surface either supersedes REQ-001 with a project-authored REQ documenting the omission (the pack looks up the sidecar `rcf/blueprints/application-dashboard.applied.json` for a `supersedes` entry) or renders the region as an empty labelled `role=\"region\"` element the pack can inspect; a silent omission fails project-side check.",
       "given": "a rendered dashboard surface with a missing region and no documented supersedes entry",
       "when": "the pack inspects the shell",
       "then": "the surface fails the region-count check; the applying project must either supersede REQ-001 with a documented reason or render the region as an empty labelled role=region element",

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

@@ -21,10 +21,10 @@
     },
     {
       "id": "AC-19102-2",
-      "description": "Given a rendered dashboard surface with no primary KPI tile, the surface either supersedes REQ-002 with a project-authored REQ documenting the omission or fails project-side review. This case is a documentation-and-review contract; the pack asserts the primary KPI tile exists (AC-19102-1) but does not itself enforce the fallback path.",
+      "description": "Given a rendered dashboard surface with no primary KPI tile, the surface either supersedes REQ-002 with a project-authored REQ documenting the omission or fails project-side check. This case is a documentation contract; the pack asserts the primary KPI tile exists (AC-19102-1) but does not itself enforce the fallback path.",
       "given": "a rendered dashboard with no primary KPI tile",
       "when": "the surface is reviewed",
-      "then": "the surface supersedes REQ-002 with a project-authored REQ or fails review",
+      "then": "the surface supersedes REQ-002 with a project-authored REQ or fails the check",
       "testable": true,
       "scope": "library",
       "disposition": "fixed"

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

@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-19103-2",
-      "description": "Given a tile transitioning between states (loading to populated, populated to error) at runtime, the tile's `aria-live=\"polite\"` region announces the new state's accessible name to the assistive tech; the announcement text reads `<tile title>, <new state>` and the visual cue changes in the same paint. This AC is a runtime-observable behaviour on state transition; the pack does not simulate the transition today (the runner has no synthetic-event seam beyond click/type/press), so the AC is proven at project-side review and the README names the transition-observation gap under known mechanism-reach gaps.",
+      "description": "Given a tile transitioning between states (loading to populated, populated to error) at runtime, the tile's `aria-live=\"polite\"` region announces the new state's accessible name to the assistive tech; the announcement text reads `<tile title>, <new state>` and the visual cue changes in the same paint. This AC is a runtime-observable behaviour on state transition; the pack does not simulate the transition today (the runner has no synthetic-event seam beyond click/type/press), so the AC is proven at project-side check and the README names the transition-observation gap under known mechanism-reach gaps.",
       "given": "a tile transitioning between states",
       "when": "the transition renders",
       "then": "the aria-live polite region announces the new state's accessible name and the visual cue changes",

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

@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-19104-2",
-      "description": "Given a rendered dashboard with an operator-elicited auto-refresh interval (ADR-2002), the shell refetches on the same fan-out contract at the interval: every tile refetches with the same from/to/preset, the as-of stamp updates on the shell root and every tile. When no auto-refresh interval is elicited, the shell does not refresh unattended (a dashboard that refreshes every ten seconds without an operator opt-in is a defect). The pack asserts the initial default is auto-refresh off through a `data-auto-refresh` attribute on the shell root; a fixture whose default is on fails project-side review. Applying agent sets: the elicited auto-refresh interval value in seconds (ADR-2002) or the explicit off default, recorded on the manifest and reflected on the shell root as `data-auto-refresh`.",
+      "description": "Given a rendered dashboard with an operator-elicited auto-refresh interval (ADR-2002), the shell refetches on the same fan-out contract at the interval: every tile refetches with the same from/to/preset, the as-of stamp updates on the shell root and every tile. When no auto-refresh interval is elicited, the shell does not refresh unattended (a dashboard that refreshes every ten seconds without an operator opt-in is a defect). The pack asserts the initial default is auto-refresh off through a `data-auto-refresh` attribute on the shell root; a fixture whose default is on fails project-side check. Applying agent sets: the elicited auto-refresh interval value in seconds (ADR-2002) or the explicit off default, recorded on the manifest and reflected on the shell root as `data-auto-refresh`.",
       "given": "a rendered dashboard with or without an elicited auto-refresh interval",
       "when": "the shell renders",
       "then": "auto-refresh is off unless the interval is elicited; refreshes follow the same fan-out contract",

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

@@ -11,7 +11,7 @@
   "acceptanceCriteria": [
     {
       "id": "AC-19105-1",
-      "description": "Given a rendered dashboard surface with filter chrome, every filter control (chip, dropdown, search input) is a labelled interactive element (a `<button>`, a `<select>` or an `<input>`) with an accessible name; the controls are keyboard-reachable in reading order before the tile row; the operator's active filter selection is reflected on the shell as a `data-active-filters` attribute the pack can read. A filter chrome that ships hover-only controls (a hover-reveal menu on a mouseover element) fails project-side review.",
+      "description": "Given a rendered dashboard surface with filter chrome, every filter control (chip, dropdown, search input) is a labelled interactive element (a `<button>`, a `<select>` or an `<input>`) with an accessible name; the controls are keyboard-reachable in reading order before the tile row; the operator's active filter selection is reflected on the shell as a `data-active-filters` attribute the pack can read. A filter chrome that ships hover-only controls (a hover-reveal menu on a mouseover element) fails project-side check.",
       "given": "a rendered dashboard with filter chrome",
       "when": "the accessibility tree is read",
       "then": "every filter control is a labelled interactive element keyboard-reachable in reading order",

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

@@ -11,7 +11,7 @@
   "acceptanceCriteria": [
     {
       "id": "AC-19106-1",
-      "description": "Given a rendered dashboard surface, the export handle region contains one labelled `<button>` (accessible name reads `Export` or an operator-configured equivalent) that on activation exposes a keyboard-reachable list of formats (a menu, a listbox or a set of `<button>` elements). The rendered format list carries at least the three shipped formats (CSV, PDF, PNG-of-chart) unless ADR-2003's elicited override replaces the set; every format entry carries a `data-export-format` attribute whose value is one of `csv`, `pdf`, `png-chart` or the elicited value. Escape closes the list and returns focus to the export button. Hover-only export dropdowns fail project-side review. Applying agent sets: the export-button accessible name (default `Export` or the operator-configured equivalent), the export-format list (default `csv`, `pdf`, `png-chart` or the ADR-2003 elicited override) and the `data-export-format` values the format entries carry.",
+      "description": "Given a rendered dashboard surface, the export handle region contains one labelled `<button>` (accessible name reads `Export` or an operator-configured equivalent) that on activation exposes a keyboard-reachable list of formats (a menu, a listbox or a set of `<button>` elements). The rendered format list carries at least the three shipped formats (CSV, PDF, PNG-of-chart) unless ADR-2003's elicited override replaces the set; every format entry carries a `data-export-format` attribute whose value is one of `csv`, `pdf`, `png-chart` or the elicited value. Escape closes the list and returns focus to the export button. Hover-only export dropdowns fail project-side check. Applying agent sets: the export-button accessible name (default `Export` or the operator-configured equivalent), the export-format list (default `csv`, `pdf`, `png-chart` or the ADR-2003 elicited override) and the `data-export-format` values the format entries carry.",
       "given": "a rendered dashboard with an export handle",
       "when": "the operator activates the export button",
       "then": "an accessible format list opens with the shipped formats, keyboard-reachable, closable on Escape",
@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-19106-2",
-      "description": "Given a PNG-of-chart export selection, the export handle delegates the PNG generation to the application-charts render shell (TAC-1901): the handle names the chart the operator picked from the chart region (a `data-chart-id` reference on the format entry, or a runtime prompt asking which chart) and the charts shell owns the PNG output. A dashboard shell that ships its own PNG generator inside the dashboard code fails project-side review. This AC is a project-side contract; the pack does not exercise the PNG generation today (no download-capture seam on the pack browser), and the README names the delegation-observation gap under known mechanism-reach gaps. Applying agent sets: the chart-selection mechanism the export handle uses for PNG-of-chart (the `data-chart-id` reference on the format entry, or a runtime prompt naming the chart the operator picked) and the application-charts render-shell mount point the shell delegates to.",
+      "description": "Given a PNG-of-chart export selection, the export handle delegates the PNG generation to the application-charts render shell (TAC-1901): the handle names the chart the operator picked from the chart region (a `data-chart-id` reference on the format entry, or a runtime prompt asking which chart) and the charts shell owns the PNG output. A dashboard shell that ships its own PNG generator inside the dashboard code fails project-side check. This AC is a project-side contract; the pack does not exercise the PNG generation today (no download-capture seam on the pack browser), and the README names the delegation-observation gap under known mechanism-reach gaps. Applying agent sets: the chart-selection mechanism the export handle uses for PNG-of-chart (the `data-chart-id` reference on the format entry, or a runtime prompt naming the chart the operator picked) and the application-charts render-shell mount point the shell delegates to.",
       "given": "a PNG-of-chart export selection",
       "when": "the export handle activates",
       "then": "PNG generation delegates to the application-charts render shell",

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

@@ -11,7 +11,7 @@
   "acceptanceCriteria": [
     {
       "id": "AC-19107-1",
-      "description": "The blueprint ships an operator-and-agent-readable design-guidance file at `assets/guidance/dashboard-design.md` covering the eight sections named in spec 5.3.1 (primary KPI placement; tile density and count limits; timeframe and filter chrome; loading, empty and error states; colour and contrast; when a table beats a chart, delegating to application-datatable; refresh cadence and staleness; anti-patterns). Each section names whether the rule hardens into an AC on this blueprint (the section names the AC id) or stays operator guidance the applying agent honours at project-side review. The file cites at least five https:// sources from the five named source families (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs). The applying agent confirms the file is present on the applied blueprint source path recorded on `manifest.blueprints[].source` and takes no substitution at project apply time.",
+      "description": "The blueprint ships an operator-and-agent-readable design-guidance file at `assets/guidance/dashboard-design.md` covering the eight sections named in spec 5.3.1 (primary KPI placement; tile density and count limits; timeframe and filter chrome; loading, empty and error states; colour and contrast; when a table beats a chart, delegating to application-datatable; refresh cadence and staleness; anti-patterns). Each section names whether the rule hardens into an AC on this blueprint (the section names the AC id) or stays operator guidance the applying agent honours at project-side check. The file cites at least five https:// sources from the five named source families (NN/g dashboard design, Few, Tufte, GOV.UK Design System patterns, WCAG 2.2 Understanding docs). The applying agent confirms the file is present on the applied blueprint source path recorded on `manifest.blueprints[].source` and takes no substitution at project apply time.",
       "given": "the shipped blueprint",
       "when": "the applying agent reads assets/guidance/dashboard-design.md",
       "then": "the eight sections and the five https citations are present and each section names AC or guidance",
@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-19107-2",
-      "description": "The dashboard shell's runtime shape reflects the rules the guidance hardens into ACs: the primary-kpi kind is one of the ADR-2001 enum values (asserted through `data-kpi-kind` on the primary tile; guidance section 1 hardens into AC-19102-1); the shell renders an `as of <ISO-8601>` stamp (guidance section 7 hardens into AC-19104-1); auto-refresh is off unless the elicited interval is set (guidance section 7 hardens into AC-19104-2). A shipped surface that violates any of these rules fails the corresponding pack check or project-side review. Applying agent sets: the primary-kpi kind value from the ADR-2001 enum (`revenue`, `active-users`, `error-rate`, `throughput`, or `custom` with a `data-kpi-name`), the auto-refresh interval or the off default, and the tile-inventory slot mapping the shell renders.",
+      "description": "The dashboard shell's runtime shape reflects the rules the guidance hardens into ACs: the primary-kpi kind is one of the ADR-2001 enum values (asserted through `data-kpi-kind` on the primary tile; guidance section 1 hardens into AC-19102-1); the shell renders an `as of <ISO-8601>` stamp (guidance section 7 hardens into AC-19104-1); auto-refresh is off unless the elicited interval is set (guidance section 7 hardens into AC-19104-2). A shipped surface that violates any of these rules fails the corresponding pack check or project-side check. Applying agent sets: the primary-kpi kind value from the ADR-2001 enum (`revenue`, `active-users`, `error-rate`, `throughput`, or `custom` with a `data-kpi-name`), the auto-refresh interval or the off default, and the tile-inventory slot mapping the shell renders.",
       "given": "a rendered dashboard shell",
       "when": "the shell is inspected against the guidance's hardened rules",
       "then": "the shape honours the primary-kpi kind, the as-of stamp and the auto-refresh default",
@@ -63,10 +63,10 @@
     },
     {
       "id": "AC-19107-5",
-      "description": "Given an applying project that ships a surface deviating from a ratified rule (a primary KPI placed top-right for cultural reasons, a tile density above the guidance cap), the deviation is documented on the project's own README under CALLS MADE with the guidance section quoted verbatim and the project's reason; a deviation without a documented CALLS MADE entry fails project-side review. Applying agent sets: the CALLS MADE entry text (the ratified guidance section quoted verbatim and the project's reason for deviating), the project's superseding REQ id, and the specific deviation named (for example the primary-kpi placement or the tile-density limit).",
+      "description": "Given an applying project that ships a surface deviating from a shipped rule (a primary KPI placed top-right for cultural reasons, a tile density above the guidance cap), the deviation is documented on the project's own README under CALLS MADE with the guidance section quoted verbatim and the project's reason; a deviation without a documented CALLS MADE entry fails project-side check. Applying agent sets: the CALLS MADE entry text (the shipped guidance section quoted verbatim and the project's reason for deviating), the project's superseding REQ id, and the specific deviation named (for example the primary-kpi placement or the tile-density limit).",
       "given": "an applying project surface deviating from a ratified guidance rule",
-      "when": "the review inspects the project's CALLS MADE section",
-      "then": "the deviation is documented with the guidance section quoted verbatim and the project's reason; an undocumented deviation fails review",
+      "when": "the check inspects the project's CALLS MADE section",
+      "then": "the deviation is documented with the guidance section quoted verbatim and the project's reason; an undocumented deviation fails the check",
       "testable": true,
       "scope": "unclassified",
       "disposition": "template"

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

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

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

@@ -37,7 +37,7 @@ Every dashboard surface renders the five labelled regions. The primary KPI tile
 
 ## Common gotchas
 
-- The primary KPI is a fixed enum (five values plus `custom` with a name). A free-form `data-kpi-kind` is refused at project-side review.
+- The primary KPI is a fixed enum (five values plus `custom` with a name). A free-form `data-kpi-kind` is refused at project-side check.
 - The as-of stamp lives on the shell root and every tile carries the same value. A tile whose stamp drifts is a defect.
 - Auto-refresh is off unless the operator opted in with an interval. A dashboard that refreshes every 30 seconds without an opt-in is a common accessibility and cost defect.
 - The export handle carries no PNG generator of its own. PNG-of-chart delegates to the application-charts render shell; a project that ships a chart engine outside the render shell either supersedes the delegation or loses the PNG affordance.
@@ -45,4 +45,4 @@ Every dashboard surface renders the five labelled regions. The primary KPI tile
 
 ## Cost honesty
 
-Shipping this blueprint costs the project a design pass on the tile inventory (which tile is the primary KPI, how many supporting tiles) and an operator conversation on the timeframe and export sets. It buys the accessibility contract on every tile, the fan-out contract on every timeframe change, the packaged design guidance the applying agent reads at apply, and the probe pack that refuses ship on a broken tile grid or a drifted fan-out. The gate reviewer verifies the pack runs green against the sample-app fixture and reviews the applying project's own dashboard surface against the packaged guidance's eight sections.
+Shipping this blueprint costs the project a design pass on the tile inventory (which tile is the primary KPI, how many supporting tiles) and an operator conversation on the timeframe and export sets. It buys the accessibility contract on every tile, the fan-out contract on every timeframe change, the packaged design guidance the applying agent reads at apply, and the probe pack that refuses ship on a broken tile grid or a drifted fan-out. The probe pack runs green against the sample-app fixture and the applying project's own dashboard surface is reviewed against the packaged guidance's eight sections.

package/blueprints/application-datatable/CHANGELOG.md

@@ -1,29 +1,39 @@
 # application-datatable CHANGELOG
 
+## 1.0.9 - 2026-09-11
+
+- Adds a contributions/probes pack meeting rule 7d.
+- Probes: apg-table-shape, sort-adapter-round-trip, search-adapter-round-trip, four-states-regions.
+- Arrow-key cell focus (AC-17107-5) is a browser-only property and is recorded as notObservableHere with the shipped AC id and reason; the row anchors nothing else.
+- Sort/search adapters observe the server round trip; the DOM click / typing halves are conformanceOnly + limitation naming the AC id and the browser property.
+- No-results uses a non-empty filter and checks the no-filter negative case.
+- 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, F-7, F-8. Template-AC fill-in clauses on AC-17101-3, AC-17102-1, AC-17108-2, AC-17108-3, AC-17109-1 and AC-17109-3 now enumerate the specific applying-project substitutions (column-id set, query-adapter endpoint and debounce, elicited query-adapter mode, applied default page size, elicited selection-persistence value, accessible-copy text near the bulk-action control) in place of the generic phrasing. TAC-1802 owns the `sort=<column>:<asc|desc>` grammar and the fixed `pageSize` query-parameter name; TAC-1803-application-datatable-selection-model patch-bumped to 1.0.2 with the `data-selection-persistence` marker on the bulk-action region added to responsibilities[3] and referenced from AC-17109-3. Register cleanup on the datatable README (removed the dated visual-specification reference and the residual mechanism-reach gap parenthetical) and on the guide (neutralised the dashboard-blueprint mention).
+Template-AC fill-in clauses on AC-17101-3, AC-17102-1, AC-17108-2, AC-17108-3, AC-17109-1 and AC-17109-3 now enumerate the specific applying-project substitutions (column-id set, query-adapter endpoint and debounce, elicited query-adapter mode, applied default page size, elicited selection-persistence value, accessible-copy text near the bulk-action control) in place of the earlier generic phrasing, so applying projects have precise values to fill in. TAC-1802 owns the `sort=<column>:<asc|desc>` grammar and the fixed `pageSize` query-parameter name; TAC-1803-application-datatable-selection-model patch-bumped to 1.0.2 with the `data-selection-persistence` marker on the bulk-action region added to responsibilities[3] and referenced from AC-17109-3. Datatable README and guide shipped prose neutralised: the dated visual-specification reference and the residual mechanism-reach gap parenthetical have been dropped from the README, and the dashboard-blueprint mention has been rewritten in the guide.
 
 
 ## 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 four apply-time answers (query-adapter-mode, url-state-strategy, page-size, selection-persistence); each option value backed by a must REQ description with a runtime clause per section 7c. REQ-001 gains a page-size 25 default clause; REQ-002 gains url-query / session-scoped URL-state clause; REQ-004 gains per-page / cross-page selection-persistence clause. capabilities[] not declared: leaf blueprint (no consumer requiresAppliedCapabilities on the shelf references a datatable capability).
-- Review fix pass 2026-09-10: F-1 vendorCitation added to eight fixed ACs whose assertions rest on W3C facts: AC-17104-3 (WCAG 2.4.3 focus-order), AC-17104-6 (ARIA APG dialog-modal pattern), AC-17105-2 (WCAG 1.4.1 use-of-color), AC-17106-4 (WCAG 2.5.7 dragging-movements), AC-17107-2 (WCAG 4.1.2 name-role-value), AC-17107-3 (WCAG 1.3.1 info-and-relationships), AC-17107-4 (ARIA APG table pattern), AC-17107-5 (ARIA APG grid pattern); each citation carries verifiedOn 2026-09-09.
+- Register-and-citation sweep 2026-09-10: vendorCitation added to eight fixed ACs whose assertions rest on W3C facts: AC-17104-3 (WCAG 2.4.3 focus-order), AC-17104-6 (ARIA APG dialog-modal pattern), AC-17105-2 (WCAG 1.4.1 use-of-color), AC-17106-4 (WCAG 2.5.7 dragging-movements), AC-17107-2 (WCAG 4.1.2 name-role-value), AC-17107-3 (WCAG 1.3.1 info-and-relationships), AC-17107-4 (ARIA APG table pattern), AC-17107-5 (ARIA APG grid pattern); each citation carries verifiedOn 2026-09-09.
 - Adds refusal-path ACs to US-17104 (bulk-action max-cap refusal, dialog Cancel focus return, focus trap), US-17106 (drag-only refusal, hidden-column orphan cells, hidden column with active sort/filter), US-17107 (read-only role=grid refusal, role=grid arrow navigation, mixed-interactive shell pattern), US-17108 (session-scoped no-URL contract, invalid-URL rejection, history.replaceState per micro-change), US-17109 (dialog aria-describedby total count, filter narrows presentation not selection, Clear selection control). Every story now at the 7a floor (4-6 ACs per story, 46 ACs total on the blueprint).
 
-## 1.0.1 (application-core hardening, 2026-09-09)
+## 1.0.1 (2026-09-09)
 
-- hardening pass: chain-consistency lint zero (pass1 + pass2 already clean at baseline); added deliveredBy to every REQ, added ownerRef and disposition to every AC per section 7b.
-- Added AC-17101-4, AC-17102-4, AC-17103-4 and AC-17105-4 (loading indicator clears, announced error region replaces the pending state, last successful rows retained) covering the 2026-09-08 review finding F-1 on TAC-1802.internalStructure for sort, filter, pagination and URL-state page requests that reject.
+- Hardening cleanup: chain-consistency lint clean at baseline; added deliveredBy to every REQ, added ownerRef and disposition to every AC per section 7b.
+- Added AC-17101-4, AC-17102-4, AC-17103-4 and AC-17105-4 (loading indicator clears, announced error region replaces the pending state, last successful rows retained) on TAC-1802.internalStructure for sort, filter, pagination and URL-state page requests that reject, so applying projects have explicit acceptance criteria for the four request-reject paths.
 
 
 ## 1.0.0 (2026-09-04)
 
-- First ratified version of the shelf's datatable blueprint. Six REQs (table shell, sort semantics, filter chrome, selection and bulk actions, empty / loading / error / no-results states, column visibility / reorder / resize), nine USs binding 27 runtime-observable ACs, three TACs (shell, query adapter, selection model), four ADRs (pattern choice, URL state, page size, selection persistence). No new global topics.
+- Initial shipped version of the shelf's datatable blueprint. Six REQs (table shell, sort semantics, filter chrome, selection and bulk actions, empty / loading / error / no-results states, column visibility / reorder / resize), nine USs binding 27 runtime-observable ACs, three TACs (shell, query adapter, selection model), four ADRs (pattern choice, URL state, page size, selection persistence). No new global topics.
 - Ships `probe-packs/application-datatable.pack.mjs`: six browser-verify checks anchored to AC-17101-1, AC-17102-1, AC-17103-2, AC-17104-3, AC-17105-1, AC-17106-1. First 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-datatable/` (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.
-- Suggests the `logging` and `errorHandling` companions with the ratified spec's reasons.
+- Ships a sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-datatable/` (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.
+- Suggests the `logging` and `errorHandling` companions with the shipped spec's reasons.

package/blueprints/application-datatable/README.md

@@ -1,6 +1,6 @@
 # Datatable blueprint (v1.0.4)
 
-Vendor-neutral datatable contract for a rcf-lite application. Ships the ARIA APG table / grid pattern choice (per interactivity), the sort / filter / paginate discipline, the selection model with a bulk-action confirmation dialog, the four-state region contract (empty / loading / error / no-results), and a non-drag keyboard path for column visibility / reorder / resize. Ships a Playwright probe pack under `probe-packs/application-datatable.pack.mjs` whose six checks are the runtime gate the delivery-ci-workflows runner drives (section 5 of the ratified visual specification). No new global topics; suggests the `logging` and `errorHandling` companions.
+Vendor-neutral datatable contract for a rcf-lite application. Ships the ARIA APG table / grid pattern choice (per interactivity), the sort / filter / paginate discipline, the selection model with a bulk-action confirmation dialog, the four-state region contract (empty / loading / error / no-results), and a non-drag keyboard path for column visibility / reorder / resize. Ships a Playwright probe pack under `probe-packs/application-datatable.pack.mjs` whose six checks are the runtime gate the delivery-ci-workflows runner drives (section 5 of the visual specification). No new global topics; suggests the `logging` and `errorHandling` companions.
 
 ## Apply
 
@@ -34,7 +34,7 @@ The pack fires ONLY when its `appliesTo` returns true; a project whose FBS does
 
 ## Quality bar
 
-Table or grid ARIA APG pattern per interactivity (ADR-1801); sortable columns keyboard-reachable with `aria-sort` announcing direction; text filter carrying `q` into the query adapter with per-column dropdowns composing deterministically; pagination controls with an `aria-live=\"polite\"` region reading `Page N of M`; selection model with per-row toggles and a page-level toggle; bulk actions opening a dialog under ARIA APG dialog-modal (`role=\"dialog\"`, `aria-modal=\"true\"`, `aria-labelledby`, `aria-describedby`, focus return to the originating row on close); four distinct states in `role=\"region\"` with `aria-live=\"polite\"`; non-colour distinction on every state (WCAG 1.4.1); URL-state serialisation of sort, filter and page as the recommended default (ADR-1802); default page size 25 elicitable at apply (ADR-1803); selection persistence elicited (ADR-1804); non-drag keyboard alternative for column visibility, reorder and resize (WCAG 2.5.7). Every bar is carried by ACs in the doc set and probed by the shipped pack.
+Table or grid ARIA APG pattern per interactivity (ADR-1801); sortable columns keyboard-reachable with `aria-sort` announcing direction; text filter carrying `q` into the query adapter with per-column dropdowns composing deterministically; pagination controls with an `aria-live=\"polite\"` region reading `Page N of M`; selection model with per-row toggles and a page-level toggle; bulk actions opening a dialog under ARIA APG dialog-modal (`role=\"dialog\"`, `aria-modal=\"true\"`, `aria-labelledby`, `aria-describedby`, focus return to the originating row on close); four distinct states in `role=\"region\"` with `aria-live=\"polite\"`; non-colour distinction on every state (WCAG 1.4.1); URL-state serialisation of sort, filter and page as the recommended default (ADR-1802); default page size 25 elicitable at apply (ADR-1803); selection persistence elicited (ADR-1804); non-drag keyboard alternative for column visibility, reorder and resize (WCAG 2.5.7). Every bar is carried by ACs in the doc set. Browser-observable bars are covered by the shipped Playwright pack. On the server-side probe pack: AC-17107-5 (arrow-key cell focus) is recorded as `notObservableHere`; AC-17107-1 is anchored positively on the returned grid/header markup; AC-17101-1 and AC-17102-1 are anchored on the server round trip and marked `conformanceOnly` with a limitation naming that the corresponding DOM interaction half is browser-only.
 
 ## Known mechanism-reach gaps
 

package/blueprints/application-datatable/blueprint.json

@@ -1,6 +1,6 @@
 {
   "slug": "application-datatable",
-  "version": "1.0.4",
+  "version": "1.0.9",
   "category": "application",
   "suggestedCompanions": [
     {
@@ -171,5 +171,6 @@
       "elicited": true,
       "standardsTraceClause": "generic enterprise practice"
     }
-  ]
+  ],
+  "updatedAt": "2026-09-11T16:04:17Z"
 }