rcf-lite 0.19.0 → 0.21.0

package/rcf/requirements/req-019.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-09-04T21:08:13.117Z",
+  "updatedAt": "2026-09-04T21:08:13.139Z",
+  "description": "The rcf-lite shelf ships the application-charts v1.0.0 blueprint (blueprints/application-charts/) with 15 contributions (4 REQs, 6 USs binding runtime-observable ACs, 2 TACs, 3 ADRs), a shipped Playwright probe pack (blueprints/application-charts/probe-packs/application-charts.pack.mjs) whose three checks (AC-18102-1 non-colour distinction, AC-18103-1 text-alternative table, AC-18104-1 keyboard traversal with reduced motion) are anchored to blueprint AC ids per T-0 AC-1701-3, and a dependency-free sample-app fixture (packages/rcf-lite/test/fixtures/probe-pack-application-charts/) the pack probes at the shelf gate. The blueprint is the ratification of the visual round T-2 (spec 2026-09-04 section 5.2), the second shipped consumer of T-0's probe-pack runner extension, and the leaf blueprint the application-dashboard T-3 consumes.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "reqId": "REQ-019",
+  "prdId": "PRD-001",
+  "title": "Application-charts v1.0.0 blueprint on the shelf with its Playwright probe pack and sample-app fixture",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "webUi",
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-09-04T21:08:13.137Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "dashboard"
+      }
+    ]
+  }
+}

package/rcf/requirements/req-020.json

@@ -0,0 +1,13 @@
+{
+  "createdAt": "2026-09-04T22:10:00.000Z",
+  "updatedAt": "2026-09-04T22:10:00.000Z",
+  "reqId": "REQ-020",
+  "prdId": "PRD-001",
+  "title": "Application-dashboard v1.0.0 blueprint on the shelf with its packaged design-guidance asset, Playwright probe pack and sample-app fixture",
+  "description": "The rcf-lite shelf ships the application-dashboard v1.0.0 blueprint (blueprints/application-dashboard/) with 18 contributions (5 REQs on the dashboard shell composition, the primary-KPI visual hierarchy, the per-tile four-state contract, the timeframe and filter chrome fan-out, and the export handle with format delegation to charts; 7 USs binding runtime-observable ACs plus one US on packaged-guidance adherence; 3 TACs on the tile grid with CSS Grid position semantics and breakpoint reflow, the filter chrome and timeframe picker with the refetch fan-out contract, and the export handle; 3 ADRs on the primary-KPI kinds enum, the timeframe presets and the export formats). Ships a packaged design-guidance asset at blueprints/application-dashboard/assets/guidance/dashboard-design.md covering primary KPI placement, tile density and count limits, timeframe and filter chrome, loading/empty/error states, colour and contrast, when a table beats a chart with delegation to application-datatable, refresh cadence and staleness, and anti-patterns (five https citations from NN/g, Few, Tufte, GOV.UK, WCAG). Ships a Playwright probe pack under blueprints/application-dashboard/probe-packs/application-dashboard.pack.mjs whose three checks (AC-19102-1 primary-KPI position by DOM order and CSS Grid position at 1440/1024/360, AC-19104-1 timeframe refetch fan-out with same boundary and matching as-of ISO-8601 stamp, AC-19103-1 per-tile four-state contract with role region, aria-live polite and non-colour distinction) are anchored to blueprint AC ids per T-0 AC-1701-3. Ships a dependency-free sample-app fixture at packages/rcf-lite/test/fixtures/probe-pack-application-dashboard/ with break switches for the negative runs. Extends the pack-browser seam with a resize(width, height) method (via the pinned Playwright MCP's browser_resize tool on the MCP route and page.setViewportSize on the project route) so probe packs can probe breakpoint reflow honestly. Third shipped consumer of T-0's probe-pack runner extension; consumes application-charts on the chart region and references application-datatable in the packaged guidance.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft"
+}

package/rcf/requirements/req-021.json

@@ -0,0 +1,13 @@
+{
+  "createdAt": "2026-09-04T23:59:00.000Z",
+  "updatedAt": "2026-09-04T23:59:00.000Z",
+  "reqId": "REQ-021",
+  "prdId": "PRD-001",
+  "title": "Application-notifications-in-app v1.0.0 blueprint on the shelf with its Playwright probe pack and sample-app fixture",
+  "description": "The rcf-lite shelf ships the application-notifications-in-app v1.0.0 blueprint (blueprints/application-notifications-in-app/) with 19 contributions (5 REQs on live-region preseeding, the transient toast contract, the notification centre inbox with acknowledge round-trip, the per-user preferences UI with sibling-channel delegation, and the delivery-attempt log; 8 USs binding runtime-observable ACs plus three cross-cutting cases on the page load with backlog, the background event and the disjoint-content contract; 3 TACs on the live-region wrappers and the toast factory, the centre inbox with retention and acknowledge round-trip, and the preferences UI with sibling delegation; 3 ADRs on the priority-to-role mapping polite/status vs assertive/alert, the WCAG 2.2.1 six-second toast timeout floor, and the ADR-2103 thirty-day retention window). Reserves the family prefix application-notifications- for the sibling channels the shelf will grow into (email, push, webhook) as documented in the blueprint README and the shelf band registry. Ships a Playwright probe pack under blueprints/application-notifications-in-app/probe-packs/application-notifications-in-app.pack.mjs whose three checks (AC-20101-1 live-region preseeding on every declared route, AC-20102-1 transient toast contract with priority-to-role mapping and timeout floor measured via data-shown-at/data-dismissed-at timestamps, AC-20103-1 centre acknowledge round-trip through data-notification-id enumeration and reconciliation of client + server request logs) are anchored to blueprint AC ids per T-0 AC-1701-3. Ships a dependency-free sample-app fixture at packages/rcf-lite/test/fixtures/probe-pack-application-notifications-in-app/ with four break switches for the negative runs (preseed, role, timeout, ack). Fourth shipped consumer of T-0's probe-pack runner extension; consumes the logging companion for the delivery-log write path and the errorHandling companion for the assertive-slot alert boundary; adds no runner surface (reuses the T-3 pack-browser resize seam only for future minor bumps, none in v1.0.0).",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft"
+}

package/rcf/requirements/req-022.json

@@ -0,0 +1,13 @@
+{
+  "createdAt": "2026-09-05T01:30:00.000Z",
+  "updatedAt": "2026-09-05T01:30:00.000Z",
+  "reqId": "REQ-022",
+  "prdId": "PRD-001",
+  "title": "Capability-declaration mechanism (capabilities[], elicits[], apply-time discovery, refusal and custom-auth elicitation) and four auth-blueprint 1.1.0 minors adopting it",
+  "description": "The rcf-lite blueprint loader accepts two additive optional top-level fields on blueprint.json: capabilities[] (a non-empty array of lower camelCase strings on the ^[a-z][a-zA-Z0-9]*$ pattern, matching the section 6a role naming convention; a blueprint declares what identity or platform capability it provides so consumer blueprints can gate surfaces on it) and elicits[] (a non-empty array of {id, prompt, kind: enum|string|boolean, default, when?} entries the apply verb reads at apply time to prompt the operator for per-project answers). The loader validates SHAPE; the vocabulary lives in the section 6a table (principalDirectory, roleModel, tenancy, auditLog) extended in the same docs edit. A third additive top-level field requiresAppliedCapabilities[] tells apply that the blueprint refuses to apply when none of the currently-applied blueprints declares any of the required capabilities (unless an allowSkipFlag matching --allow-no-auth-yet is passed); apply then reads back each applied blueprint's source blueprint.json (the applied-blueprint-record schema is closed and refuses new fields; the source-manifest read-back precedent from the T-2 core-companions train applies here) to compute the appliedCapabilities union across the project. When the union is empty AND the blueprint is admin-console AND --allow-no-auth-yet was not passed, the apply exits 3 with a stderr message naming security-auth-* (the spec 5.5.1 verbatim message) and lists the currently-applied blueprints. When --allow-no-auth-yet is passed, apply stamps a note field onto the applied record so a later rcf define validate can flag surfaces that never activated. The elicitation phase prompts on a TTY and reads --answer <id>=<value> (repeatable) plus --answers <file> (JSON object) non-interactively; each elicit's `when` predicate evaluates against the discovered applied-capability set so elicits like the tenancy shape only prompt when the tenancy capability is applied. Apply persists appliedCapabilities and appliedElicitations into a sidecar file at rcf/blueprints/${slug}.applied.json (the applied-blueprint-record schema is closed under additionalProperties:false so the manifest cannot carry them; the sidecar is read by consumer surfaces at runtime). The four shelf auth blueprints adopt capabilities[] in v1.1.0 minor bumps landing in the same PR per spec Q2 default: security-auth-magic-link 1.0.0 -> 1.1.0 capabilities: [principalDirectory]; security-auth-clerk 1.1.0 -> 1.2.0 capabilities: [principalDirectory, roleModel]; security-auth-oauth2 1.0.0 -> 1.1.0 capabilities: [principalDirectory, roleModel]; security-auth-keycloak 1.0.0 -> 1.1.0 capabilities: [principalDirectory, roleModel]. Per section 6 of blueprint-authoring.md, an additive optional field with no global-topic change is a minor bump.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft"
+}

package/rcf/requirements/req-023.json

@@ -0,0 +1,14 @@
+{
+  "createdAt": "2026-09-05T01:30:00.000Z",
+  "updatedAt": "2026-09-05T01:30:00.000Z",
+  "reqId": "REQ-023",
+  "prdId": "PRD-001",
+  "title": "Application-admin-console v1.0.0 blueprint on the shelf with capability-gated surfaces, a Playwright probe pack and a sample-app fixture",
+  "description": "The rcf-lite shelf ships the application-admin-console v1.0.0 blueprint (blueprints/application-admin-console/) with 23 contributions (6 REQs on the console shell with no dead links to unapplied capabilities, the users surface conditional on principalDirectory, the roles surface conditional on roleModel with Owner + Admin + Member + Viewer baseline, the orgs surface conditional on tenancy, the audit-log surface conditional on the auditLog logging companion, and the access-denied and request-access states per WCAG; 9 USs 21101-21109 binding runtime-observable ACs plus the conditional-refusal apply-time behaviour; 4 TACs 2201-2204 on the console shell reading the surface manifest, the apply-time capability discovery, the permission matrix as an ARIA APG grid, and the audit view consuming application-datatable; 4 ADRs 2201-2204 on the capability vocabulary, baseline roles with elicited additions, invite transport with email default delegated to the email sibling and elicited, and audit-log retention window elicited). The blueprint declares requiresAppliedCapabilities: [principalDirectory] and allowSkipFlag: allow-no-auth-yet so a bare-SPA apply refuses with exit 3 and the spec 5.5.1 verbatim message naming security-auth-*; the override records a note on the applied record. Declares elicits[] gating baselineRoles (only when roleModel is applied), tenancyShape (only when tenancy is applied), inviteTransport, and auditRetentionDays (only when auditLog is applied). Declares suggestedCompanions logging and errorHandling with the ratified spec section 5.5 reasons; providesRoles absent per spec 5.5.3 (the console is a consumer of principalDirectory, never a provider). Ships a Playwright probe pack under blueprints/application-admin-console/probe-packs/application-admin-console.pack.mjs whose four checks (AC-21102-1 users directory, AC-21103-1 permission matrix, AC-21104-1 org switcher, AC-21105-1 audit-log surface) each carry an appliesTo predicate that reads manifest.blueprints[] and the read-back capabilities so an inapplicable check records applicable: false and the aggregate verdict treats it as neither pass nor fail. Ships a dependency-free sample-app fixture at packages/rcf-lite/test/fixtures/probe-pack-application-admin-console/ with a CAPS env or query switch selecting which surfaces exist (mirrors the applied capability set so the sample app plays every fixture), a console shell whose nav only links applied surfaces, a users directory table with per-row invite and deactivate controls enumerated by data-user-id, a permission matrix rendered as an ARIA APG grid with role=grid, role=row, role=gridcell, role=rowheader on role rows and role=columnheader on permission columns announcing the exact permission string on focus (WCAG 4.1.3), an org switcher (only under tenancy), an audit-log table with actor / target / before / after / timestamp / correlation id enumerated by data-audit-id, an access-denied route with a request-access control, request log on window.__adminFetches and /__requests, and break switches for the negative runs (matrix-grid, denied, audit-fields). Reads applied capabilities from the rcf/blueprints/application-admin-console.applied.json sidecar or from an ADMIN_CONSOLE_CAPS env override so the fixture can play fixtures (b) SPA + magic-link, (c) SPA + clerk + logging, and (d) custom-auth elicited capabilities. Fifth shipped consumer of T-0's probe-pack runner extension; consumes application-datatable (T-1) for the users directory and audit views."
+,
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft"
+}

package/rcf/test-suites/ts-045.json

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-09-04T16:22:23.766Z",
+  "updatedAt": "2026-09-04T17:21:35.618Z",
+  "purpose": "Cover the four ACs on US-1601 via the unit and integration suites landed in this train. L1 through L3 are deterministic tests over pure or seam-injected code paths; L4 tests the judge invocation shape via a stubbed spawn seam (a real subprocess round-trip is exercised out-of-band as the section 11 real-claude smoke).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1601-1",
+    "AC-1601-2",
+    "AC-1601-3",
+    "AC-1601-4"
+  ],
+  "id": "TS-045",
+  "usId": "US-1601",
+  "title": "rcf-lite consumer wiring for the rcf-schemas 0.6.0 EVAL node",
+  "testCases": [
+    {
+      "id": "TC-045-computeevalcoverage-across-the-four",
+      "acId": "AC-1601-1",
+      "description": "computeEvalCoverage across the four outcome buckets (covered, covered-optional, missing, not-required) and the classifyEvalDoc pending/superseded/resolving classification",
+      "status": "pending",
+      "testPointer": "test/query/eval-coverage.test.js::nonDeterministic AC without a bound EVAL reports missing and fails the gate"
+    },
+    {
+      "id": "TC-045-per-ac-verdicts-carries-the-two-new-eval",
+      "acId": "AC-1601-2",
+      "description": "PER_AC_VERDICTS carries the two new EVAL classes; evalPerAcVerdict returns null for deterministic ACs; fires EVAL-MISSING when nonDeterministic AC has no resolving EVAL; fires EVAL-BELOW-THRESHOLD on a failing run",
+      "status": "pending",
+      "testPointer": "test/verify/verdict/eval-per-ac.test.js::derivePerAcVerdicts folds EVAL classes alongside the pre-existing per-AC verdicts"
+    },
+    {
+      "id": "TC-045-findevalrefusalacs-and",
+      "acId": "AC-1601-3",
+      "description": "findEvalRefusalAcs and reportHasEvalRefusal read the two EVAL classes off perAcVerdicts[]; composeShipWithoutEvalRecord carries the operator reason and declared per-AC verdicts; nextShipWithoutEvalId increments monotonically",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-eval-refusal.test.js::finalise --ship-without-eval \"harness offline\" exits 0 and appends a monotonic swe-* record on manifest.shipWithoutEval[]"
+    },
+    {
+      "id": "TC-045-runonecase-spawns-the-invoker-claude-or",
+      "acId": "AC-1601-4",
+      "description": "runOneCase spawns the invoker (claude or codex) via the seam, validates response against the declared schema, composeRunRecord verdict resolves to pass on met threshold and fail on critical criterion failure",
+      "status": "pending",
+      "testPointer": "test/eval/judge.test.js::runOneCase returns the parsed graded envelope on a valid response"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-046.json

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-09-04T18:00:42.492Z",
+  "updatedAt": "2026-09-04T18:51:45.216Z",
+  "purpose": "Cover AC-1701-1..8 via unit tests over the pack schema validator, the pack loader (both extensions, cross-check, applicability seams), the runner pack pass (aggregate verdict extension, browser and fetch injection, preChecks with dependsOn), the CLI --probe-pack option (unknown-name refusal, pack restriction, applicable=false record path), the Playwright-MCP pack-browser stdio client (evaluate-result parsing), and the boot fallback (reachability probe, spawn-and-wait, waitForSelector soft-timeout, cleanup on completion).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1701-1",
+    "AC-1701-2",
+    "AC-1701-3",
+    "AC-1701-4",
+    "AC-1701-5",
+    "AC-1701-6",
+    "AC-1701-7",
+    "AC-1701-8"
+  ],
+  "id": "TS-046",
+  "usId": "US-1701",
+  "title": "Blueprint-shipped probe pack loader, scoping, cross-check, runner pass and CLI --probe-pack",
+  "testCases": [
+    {
+      "id": "TC-046-pack-loader-loads-both-pack-js-and-pack",
+      "acId": "AC-1701-1",
+      "description": "Pack loader loads both .pack.js and .pack.mjs; validates packName pattern and blueprint-slug prefix; refuses non-array checks[] with exit 2 diagnostic",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-loader.test.js::loadProbePacks accepts .pack.js and .pack.mjs and reports one loaded pack per legal module"
+    },
+    {
+      "id": "TC-046-applicability-predicate-source-scan",
+      "acId": "AC-1701-2",
+      "description": "Applicability predicate source-scan refuses unqualified predicate () => true and refuses a predicate that references none of route, tacIds, blueprint:; appliesTo returning false records applicable=false",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-loader.test.js::applicability predicate refuses unqualified default and records applicable=false when appliesTo returns false"
+    },
+    {
+      "id": "TC-046-loader-refuses-at-exit-2-a-pack-whose",
+      "acId": "AC-1701-3",
+      "description": "Loader refuses at exit 2 a pack whose checks[].id names an AC id the blueprint does not contribute; the diagnostic names the offending id and the contributed AC ids",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-loader.test.js::loader refuses a pack whose check id names an AC the blueprint does not contribute"
+    },
+    {
+      "id": "TC-046-runner-pack-pass-invokes-each-check-s",
+      "acId": "AC-1701-4",
+      "description": "Runner pack pass invokes each check's run with injected browser and fetch, folds results into probePacks[], and aggregate verdict extension blocks on severity block fail and warns on severity warn fail",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-runner.test.js::runProbePacksForFbs folds probePacks[] onto the record and the aggregate verdict extension blocks on a block-severity pack fail"
+    },
+    {
+      "id": "TC-046-cli-probe-pack-option-restricts-to-one",
+      "acId": "AC-1701-5",
+      "description": "CLI --probe-pack option restricts to one pack by name; unknown name exits 2 with a diagnostic naming the discovered packs; when omitted every discovered pack runs",
+      "status": "pending",
+      "testPointer": "test/cli/browser-verify-probe-pack.test.js::rcf verify browser --probe-pack restricts to one pack and exits 2 on unknown pack name"
+    },
+    {
+      "id": "TC-046-prechecks-runs-before-browser-checks-a",
+      "acId": "AC-1701-6",
+      "description": "preChecks[] runs before browser checks; a failing pre-check skips only browser checks that name it under dependsOn with verdict skipped and detail skipped-by-pre-check; other checks still run",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-runner.test.js::preChecks fast-fail skips browser checks that dependsOn a failing pre-check"
+    },
+    {
+      "id": "TC-046-pack-browser-evaluate-parser",
+      "acId": "AC-1701-7",
+      "description": "The Playwright-MCP stdio client parses browser_evaluate result blocks (both the '### Result' fenced form used by MCP 0.0.80+ and the legacy 'Result:' trailer) into typed JS values so a pack's check can assert on the value directly",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-browser.test.js::parseEvaluateResult returns a parsed JSON value when the MCP block ends with Result: <json>"
+    },
+    {
+      "id": "TC-046-boot-skips-when-runtime-reachable",
+      "acId": "AC-1701-8",
+      "description": "bootIfNeeded returns already-up when the runtime URL responds with any HTTP status; returns no-boot / no-boot-command when the pack declares no boot / no bootCommand; spawns bootCommand and reports started when the URL flips to reachable; SIGTERMs the child on stop()",
+      "status": "pending",
+      "testPointer": "test/browser-verify/boot.test.js::bootIfNeeded spawns bootCommand, polls until waitForUrl responds, then reports started"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-047.json

@@ -0,0 +1,54 @@
+{
+  "createdAt": "2026-09-04T20:05:51.932Z",
+  "updatedAt": "2026-09-04T20:09:33.956Z",
+  "purpose": "Cover AC-1801-1..5 via unit tests over the shipped application-datatable blueprint's contribution counts (six REQs, nine USs, three TACs, four ADRs, 27 ACs total), the pack-loader accepting the shipped pack file with every check id cross-checked against the blueprint's contributed AC ids, the pack schema accepting the pack's applicability predicate (references route and tacIds), and the sample-app fixture's exported startServer plus /api/rows shape.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1801-1",
+    "AC-1801-2",
+    "AC-1801-3",
+    "AC-1801-4",
+    "AC-1801-5"
+  ],
+  "id": "TS-047",
+  "usId": "US-1801",
+  "title": "application-datatable v1.0.0 shelf shape and probe pack cross-check",
+  "testCases": [
+    {
+      "id": "TC-047-blueprint-json-declares-slug-application",
+      "acId": "AC-1801-1",
+      "description": "blueprint.json declares slug application-datatable, version 1.0.0, category application, 22 contributions in 6 REQ / 9 US / 3 TAC / 4 ADR groups, and suggestedCompanions declares logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-datatable-anatomy.test.js::application-datatable: blueprint.json declares the ratified shape (TC-047-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-047-fresh-init-project-applies-the-blueprint",
+      "acId": "AC-1801-2",
+      "description": "Fresh init project applies the blueprint cleanly; walkTree produces zero errors; 6 REQs and 9 USs land under the application-datatable prefix",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-datatable-anatomy.test.js::application-datatable: applies cleanly on a fresh init project and adds 22 documents to the tree (TC-047-applies-clean)"
+    },
+    {
+      "id": "TC-047-every-pack-check-id-resolves-to-an-ac-id",
+      "acId": "AC-1801-3",
+      "description": "Every pack check id resolves to an AC id contributed by the blueprint; expected six check ids in the same order as the spec",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-datatable-anatomy.test.js::application-datatable: every AC id in each contributed US matches the pack check ids and vice versa where anchored (TC-047-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-047-sample-app-fixture-startserver-serves",
+      "acId": "AC-1801-4",
+      "description": "Sample-app fixture startServer serves /api/rows honouring sort, q, page and pageSize; loaders discovery finds the shipped pack against an applied scratch project",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-datatable-anatomy.test.js::application-datatable sample-app fixture: startServer returns rows on /api/rows with sort, q, page and pageSize (TC-047-fixture-api-rows)"
+    },
+    {
+      "id": "TC-047-pack-loader-against-blueprint-discovers",
+      "acId": "AC-1801-5",
+      "description": "pack loader against blueprint discovers exactly one pack with six checks; the pack cross-check test proves the pack refuses ship on broken fixture at the section 9 T-1 row 3 gate the reviewer runs against a live server",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-datatable-anatomy.test.js::application-datatable: pack loader discovers the shipped pack against an applied scratch project (TC-047-pack-loader-discovers)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-048.json

@@ -0,0 +1,54 @@
+{
+  "createdAt": "2026-09-04T21:08:44.011Z",
+  "updatedAt": "2026-09-04T21:09:34.444Z",
+  "purpose": "Cover AC-1901-1..5 via unit tests over the shipped application-charts blueprint's contribution counts (four REQs, six USs, two TACs, three ADRs, 15 contributions total), the pack-loader accepting the shipped pack file with every check id cross-checked against the blueprint's contributed AC ids and every check carrying a description, the pack schema accepting the pack's applicability predicate (references route and tacIds), the sample-app fixture exporting startServer serving a chart route with two-series bar and line charts (colour plus pattern plus direct label) and a text-alternative table with keyboard focus and reduced-motion suppression, and the negative-run behaviour on the ?break=table, ?break=pattern and ?break=keyboard switches.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1901-1",
+    "AC-1901-2",
+    "AC-1901-3",
+    "AC-1901-4",
+    "AC-1901-5"
+  ],
+  "id": "TS-048",
+  "usId": "US-1901",
+  "title": "application-charts v1.0.0 shelf shape and probe pack cross-check",
+  "testCases": [
+    {
+      "id": "TC-048-blueprint-json-shape",
+      "acId": "AC-1901-1",
+      "description": "blueprint.json declares slug application-charts, version 1.0.0, category application, 15 contributions in 4 REQ / 6 US / 2 TAC / 3 ADR groups, and suggestedCompanions declares logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-charts-anatomy.test.js::application-charts: blueprint.json declares the ratified shape (TC-048-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-048-applies-clean",
+      "acId": "AC-1901-2",
+      "description": "Fresh init project applies the blueprint cleanly; walkTree produces zero errors; 4 REQs and 6 USs land under the application-charts prefix",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-charts-anatomy.test.js::application-charts: applies cleanly on a fresh init project and adds 15 documents to the tree (TC-048-applies-clean)"
+    },
+    {
+      "id": "TC-048-pack-checks-cross-check",
+      "acId": "AC-1901-3",
+      "description": "Every pack check id resolves to an AC id contributed by the blueprint; expected three check ids in the same order as the spec (AC-18102-1, AC-18103-1, AC-18104-1) and every check carries a description field",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-charts-anatomy.test.js::application-charts: every AC id in each contributed US matches the pack check ids and every check carries a description (TC-048-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-048-fixture-charts-render",
+      "acId": "AC-1901-4",
+      "description": "Sample-app fixture startServer renders a chart route with two-series bar and line charts (colour plus pattern plus direct label), a visually-hidden focus-reachable table, keyboard-focusable data points and a reduced-motion CSS rule; loader discovery finds the shipped pack against an applied scratch project",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-charts-anatomy.test.js::application-charts sample-app fixture: startServer renders the chart shell (TC-048-fixture-charts-render)"
+    },
+    {
+      "id": "TC-048-negative-runs",
+      "acId": "AC-1901-5",
+      "description": "The pack refuses ship on each broken variant: ?break=table triggers verdict fail on AC-18103-1; ?break=pattern triggers verdict fail on AC-18102-1; ?break=keyboard triggers verdict fail on AC-18104-1; every failure records severity block and the aggregate verdict is block",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-charts-anatomy.test.js::application-charts sample-app fixture: break switches refuse ship on each surface (TC-048-negative-runs)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-049.json

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-09-04T22:10:00.000Z",
+  "updatedAt": "2026-09-04T22:10:00.000Z",
+  "purpose": "Cover AC-2001-1..7 via unit tests over the shipped application-dashboard blueprint's contribution counts (five REQs, seven USs, three TACs, three ADRs, 18 contributions total), the packaged design-guidance asset shape (eight sections and at least five https citations), the pack-loader accepting the shipped pack file with every check id cross-checked against the blueprint's contributed AC ids and every check carrying a description, the pack schema accepting the pack's applicability predicate (references tacIds), the sample-app fixture exporting startServer serving a dashboard route with a primary-KPI-top-left tile grid, a paired chart region, a timeframe preset picker refetching every tile with the same from/to boundary and matching as-of stamp, per-tile four states, an export handle, a request log surface and a reflow to one column at 360, and the negative-run behaviour on the ?break=kpi-position, ?break=fanout and ?break=state-aria switches, plus a unit test for the pack-browser resize seam extension.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2001-1",
+    "AC-2001-2",
+    "AC-2001-3",
+    "AC-2001-4",
+    "AC-2001-5",
+    "AC-2001-6",
+    "AC-2001-7"
+  ],
+  "id": "TS-049",
+  "usId": "US-2001",
+  "title": "application-dashboard v1.0.0 shelf shape, packaged guidance, probe pack cross-check and resize seam",
+  "testCases": [
+    {
+      "id": "TC-049-blueprint-json-shape",
+      "acId": "AC-2001-1",
+      "description": "blueprint.json declares slug application-dashboard, version 1.0.0, category application, 18 contributions in 5 REQ / 7 US / 3 TAC / 3 ADR groups, providesRoles empty array, suggestedCompanions declares logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard: blueprint.json declares the ratified shape (TC-049-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-049-applies-clean",
+      "acId": "AC-2001-2",
+      "description": "Fresh init project applies the blueprint cleanly; walkTree produces zero errors; 5 REQs and 7 USs land under the application-dashboard prefix",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard: applies cleanly on a fresh init project and adds 18 documents to the tree (TC-049-applies-clean)"
+    },
+    {
+      "id": "TC-049-guidance-asset",
+      "acId": "AC-2001-3",
+      "description": "assets/guidance/dashboard-design.md carries the eight ratified section headings and at least five https:// citations from the named sources",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard: packaged design-guidance asset carries eight sections and five https citations (TC-049-guidance-asset)"
+    },
+    {
+      "id": "TC-049-pack-checks-cross-check",
+      "acId": "AC-2001-4",
+      "description": "Every pack check id resolves to an AC id contributed by the blueprint; expected three check ids in the spec's order (AC-19102-1, AC-19104-1, AC-19103-1); every check carries a description field; applicability predicate references tacIds",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard: every pack check id matches a contributed AC id, every check carries a description, appliesTo binds tacIds (TC-049-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-049-fixture-dashboard-render",
+      "acId": "AC-2001-5",
+      "description": "Sample-app fixture startServer renders a dashboard route with a primary KPI top-left tile, a paired chart region, timeframe preset controls, per-tile state switches, an export handle and a request log; loader discovery finds the shipped pack against an applied scratch project",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard sample-app fixture: startServer renders the dashboard shell (TC-049-fixture-dashboard-render)"
+    },
+    {
+      "id": "TC-049-negative-runs",
+      "acId": "AC-2001-6",
+      "description": "The pack refuses ship on each broken variant: ?break=kpi-position triggers verdict fail on AC-19102-1; ?break=fanout triggers verdict fail on AC-19104-1; ?break=state-aria triggers verdict fail on AC-19103-1; every failure records severity block and the aggregate verdict is block",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-dashboard-anatomy.test.js::application-dashboard sample-app fixture: break switches refuse ship on each surface (TC-049-negative-runs)"
+    },
+    {
+      "id": "TC-049-resize-seam",
+      "acId": "AC-2001-7",
+      "description": "pack-browser exposes resize(width, height); the project-route handle drives page.setViewportSize with the given dimensions and the same handle can be re-queried through window.innerWidth after a resize call",
+      "status": "pending",
+      "testPointer": "test/browser-verify/pack-browser-resize.test.js::pack-browser: resize dimension normalisation rounds finite positive numbers (TC-049-resize-seam)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-050.json

@@ -0,0 +1,69 @@
+{
+  "createdAt": "2026-09-04T23:59:00.000Z",
+  "updatedAt": "2026-09-04T23:59:00.000Z",
+  "purpose": "Cover AC-2101-1..6 via unit tests over the shipped application-notifications-in-app blueprint's contribution counts (five REQs, eight USs, three TACs, three ADRs, 19 contributions total), the pack-loader accepting the shipped pack file with every check id cross-checked against the blueprint's contributed AC ids, every check carrying a description, and the AC-20101-1 description containing the word 'preseeded' per section 9 T-4 row, the pack schema accepting the pack's applicability predicate (references BOTH tacIds AND route), the sample-app fixture exporting startServer serving the three routes with the live-region preseeding, the notification centre backlog, the acknowledge round-trip and the preferences UI, and the negative-run behaviour on the ?break=preseed, ?break=role, ?break=timeout and ?break=ack switches, plus the family-prefix reservation documented in the blueprint README and every shelf topics.md registry row.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2101-1",
+    "AC-2101-2",
+    "AC-2101-3",
+    "AC-2101-4",
+    "AC-2101-5",
+    "AC-2101-6"
+  ],
+  "id": "TS-050",
+  "usId": "US-2101",
+  "title": "application-notifications-in-app v1.0.0 shelf shape, probe pack cross-check, sample-app fixture and family-prefix reservation",
+  "testCases": [
+    {
+      "id": "TC-050-blueprint-json-shape",
+      "acId": "AC-2101-1",
+      "description": "blueprint.json declares slug application-notifications-in-app, version 1.0.0, category application, 19 contributions in 5 REQ / 8 US / 3 TAC / 3 ADR groups, providesRoles absent, suggestedCompanions declares logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app: blueprint.json declares the ratified shape (TC-050-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-050-applies-clean",
+      "acId": "AC-2101-2",
+      "description": "Fresh init project applies the blueprint cleanly; walkTree produces zero errors; 5 REQs and 8 USs land under the application-notifications-in-app prefix",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app: applies cleanly on a fresh init project and adds 19 documents to the tree (TC-050-applies-clean)"
+    },
+    {
+      "id": "TC-050-pack-checks-cross-check",
+      "acId": "AC-2101-3",
+      "description": "Every pack check id resolves to an AC id contributed by the blueprint; expected three check ids (AC-20101-1, AC-20102-1, AC-20103-1); every check carries a description; AC-20101-1 description contains the word 'preseeded' per spec section 9 T-4 row; applicability predicate references BOTH tacIds and route",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app: every pack check id matches a contributed AC id, description discipline holds, appliesTo binds tacIds AND route (TC-050-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-050-fixture-preseeding",
+      "acId": "AC-2101-4",
+      "description": "Sample-app fixture startServer serves the main, centre and preferences routes; every route preseeds both live-region wrappers empty at load; the centre lists the seeded backlog with data-notification-id enumeration and acknowledge / mark-read / mark-all-read controls; the preferences route renders category silence toggles and sibling-channel sections disabled",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app sample-app fixture: preseeds live regions on every route (TC-050-fixture-preseeding)"
+    },
+    {
+      "id": "TC-050-fixture-acknowledge",
+      "acId": "AC-2101-4",
+      "description": "POST /api/notifications/acknowledge updates the seeded delivery-log row's acknowledgedAt and returns {ok:true}; GET /api/delivery-log returns the seeded rows; /__requests mirrors the server-side record log",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app sample-app fixture: acknowledge round-trips through /api/notifications/acknowledge and delivery-log endpoint returns the seeded rows (TC-050-fixture-acknowledge)"
+    },
+    {
+      "id": "TC-050-negative-runs",
+      "acId": "AC-2101-5",
+      "description": "?break=preseed drops the wrappers from the initial DOM; ?break=role inverts the priority-to-role mapping in the client script (an error toast lands in the polite wrapper as role=status); ?break=timeout advertises a two-second floor on data-toast-timeout-floor-seconds; ?break=ack renders the acknowledge control with no click POST",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app sample-app fixture: break switches surface the four defects on the DOM (TC-050-negative-runs)"
+    },
+    {
+      "id": "TC-050-family-prefix-reservation",
+      "acId": "AC-2101-6",
+      "description": "The family-prefix reservation is present in the blueprint README (a paragraph naming application-notifications- reserved for the sibling channels -email, -push, -webhook) and in the shelf band registry table in every applying blueprint's docs/topics.md",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-notifications-in-app-anatomy.test.js::application-notifications-in-app: family-prefix reservation documented in blueprint README and own topics.md (TC-050-family-prefix-reservation)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-051.json

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-05T01:30:00.000Z",
+  "updatedAt": "2026-09-05T01:30:00.000Z",
+  "purpose": "Cover AC-2201-1..9 via unit tests over the blueprint loader accepting capabilities[], elicits[] and requiresAppliedCapabilities with shape validation, applyBlueprint discovering applied capabilities from the applied blueprints source blueprint.json files, refusing on a bare-SPA project with the spec 5.5.1 message, honouring --allow-no-auth-yet, running the elicitation phase with --answer and --answers, writing the sidecar rcf/blueprints/${slug}.applied.json with appliedCapabilities and appliedElicitations, the four shelf auth blueprints declaring their capabilities[] in their v1.1.0 minor bumps with matching CHANGELOG entries, and docs/blueprint-authoring.md section 6a carrying the extended capability vocabulary table.",
+  "testLevel": "unit",
+  "acIds": ["AC-2201-1", "AC-2201-2", "AC-2201-3", "AC-2201-4", "AC-2201-5", "AC-2201-6", "AC-2201-7", "AC-2201-8", "AC-2201-9"],
+  "id": "TS-051",
+  "usId": "US-2201",
+  "title": "Capability-declaration mechanism loader and apply verb behaviour; four auth-blueprint 1.1.0 minor adoption",
+  "testCases": [
+    {"id": "TC-051-loader-capabilities-shape", "acId": "AC-2201-1", "description": "loader accepts capabilities[] on shape; refuses empty array, refuses non-string entries, refuses non-camelCase strings", "status": "pending", "testPointer": "test/blueprint/capabilities-loader.test.js::loader accepts capabilities[] shape and refuses malformed variants (TC-051-loader-capabilities-shape)"},
+    {"id": "TC-051-loader-elicits-shape", "acId": "AC-2201-2", "description": "loader accepts elicits[] on shape; refuses empty array, refuses invalid kind, refuses em-dash in prompt, refuses missing options on kind=enum", "status": "pending", "testPointer": "test/blueprint/capabilities-loader.test.js::loader accepts elicits[] shape and refuses malformed variants (TC-051-loader-elicits-shape)"},
+    {"id": "TC-051-loader-requires-shape", "acId": "AC-2201-3", "description": "loader accepts requiresAppliedCapabilities object shape; refuses empty capabilities array, refuses non-kebab allowSkipFlag", "status": "pending", "testPointer": "test/blueprint/capabilities-loader.test.js::loader accepts requiresAppliedCapabilities shape and refuses malformed variants (TC-051-loader-requires-shape)"},
+    {"id": "TC-051-apply-discovery-refuse", "acId": "AC-2201-4", "description": "applyBlueprint returns a requiresAppliedCapabilities rcfError when no applied blueprint declares any required capability and allowNoAuthYet is false; message body includes the spec 5.5.1 verbatim opening line and lists the currently-applied blueprints", "status": "pending", "testPointer": "test/blueprint/capabilities-apply.test.js::apply refuses with requiresAppliedCapabilities rcfError on a bare project (TC-051-apply-discovery-refuse)"},
+    {"id": "TC-051-apply-allow-skip", "acId": "AC-2201-5", "description": "applyBlueprint with allowNoAuthYet true writes contributions and sidecar with allowNoAuthYet true and a notes string naming the no-auth-yet state; manifest applied record is untouched", "status": "pending", "testPointer": "test/blueprint/capabilities-apply.test.js::apply honours allowNoAuthYet and writes sidecar with notes (TC-051-apply-allow-skip)"},
+    {"id": "TC-051-elicit-answers", "acId": "AC-2201-6", "description": "applyBlueprint reads elicitAnswers map; every elicit whose when-predicate resolves true against discovered capabilities is coerced by kind; missing required answer returns validation rcfError naming id", "status": "pending", "testPointer": "test/blueprint/capabilities-apply.test.js::apply elicitation phase coerces answers by kind and refuses missing required (TC-051-elicit-answers)"},
+    {"id": "TC-051-sidecar-write", "acId": "AC-2201-7", "description": "applyBlueprint writes rcf/blueprints/${slug}.applied.json with slug, version, appliedAt, appliedCapabilities and appliedElicitations; re-apply on same version rewrites the file idempotently", "status": "pending", "testPointer": "test/blueprint/capabilities-apply.test.js::apply writes sidecar with appliedCapabilities and appliedElicitations idempotently (TC-051-sidecar-write)"},
+    {"id": "TC-051-auth-minors", "acId": "AC-2201-8", "description": "The four shelf auth blueprints declare capabilities[] and correct new versions; each CHANGELOG.md carries a new entry naming the capabilities added and citing spec section 5.5.2", "status": "pending", "testPointer": "test/blueprint/capabilities-auth-minors.test.js::the four shelf auth blueprints declare capabilities[] and matching CHANGELOG entries (TC-051-auth-minors)"},
+    {"id": "TC-051-docs-section-6a", "acId": "AC-2201-9", "description": "packages/rcf-lite/docs/blueprint-authoring.md section 6a includes the capability vocabulary table with the four capability strings and their shelf providers; the section text cross-references capabilities[] and requiresAppliedCapabilities as loader fields", "status": "pending", "testPointer": "test/blueprint/capabilities-auth-minors.test.js::docs blueprint-authoring section 6a carries the capability vocabulary table (TC-051-docs-section-6a)"}
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-052.json

@@ -0,0 +1,20 @@
+{
+  "createdAt": "2026-09-05T01:30:00.000Z",
+  "updatedAt": "2026-09-05T01:30:00.000Z",
+  "purpose": "Cover AC-2301-1..7 via unit tests over the shipped application-admin-console blueprint.json contribution shape (23 contributions in 6 REQ / 9 US / 4 TAC / 4 ADR groups), the requiresAppliedCapabilities and elicits[] declarations, the pack-loader accepting the shipped pack file with every check id cross-checked against blueprint AC ids, the pack appliesTo predicate discipline (references BOTH tacIds and route), the sample-app fixture serving the console shell with the ARIA APG grid permission matrix, the CAPS switch surface selector, the users directory, org switcher, audit-log table with correlation id, access-denied and request-access control, and the negative-run behaviour on the ?break=matrix-grid, ?break=denied and ?break=audit-fields switches.",
+  "testLevel": "unit",
+  "acIds": ["AC-2301-1", "AC-2301-2", "AC-2301-3", "AC-2301-4", "AC-2301-5", "AC-2301-6", "AC-2301-7"],
+  "id": "TS-052",
+  "usId": "US-2301",
+  "title": "application-admin-console v1.0.0 shelf shape, capability discovery, probe pack cross-check and sample-app fixture",
+  "testCases": [
+    {"id": "TC-052-blueprint-json-shape", "acId": "AC-2301-1", "description": "blueprint.json declares 23 contributions with requiresAppliedCapabilities and elicits[]", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::blueprint.json declares 23 contributions with requiresAppliedCapabilities and elicits[] (TC-052-blueprint-json-shape)"},
+    {"id": "TC-052-applies-clean-with-override", "acId": "AC-2301-2", "description": "Fresh init project applies admin-console --allow-no-auth-yet and writes sidecar with allowNoAuthYet true", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::apply --allow-no-auth-yet on bare SPA writes sidecar with allowNoAuthYet:true and empty appliedCapabilities (TC-052-applies-clean-with-override)"},
+    {"id": "TC-052-refuses-bare-spa", "acId": "AC-2301-3", "description": "Fresh init project without auth refuses admin-console apply with exit 3 and spec 5.5.1 message", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::apply refuses on bare SPA with spec 5.5.1 verbatim message and lists applied blueprints (TC-052-refuses-bare-spa)"},
+    {"id": "TC-052-capability-discovery", "acId": "AC-2301-4", "description": "Discovery reads applied capabilities from applied blueprints", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::apply on magic-link project yields [principalDirectory] and on clerk+logging project yields [principalDirectory,roleModel,auditLog] (TC-052-capability-discovery)"},
+    {"id": "TC-052-pack-checks-cross-check", "acId": "AC-2301-5", "description": "Every pack check id matches contributed AC id and applies gates on capability", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::every pack check id matches a contributed AC id and appliesTo predicate gates on the applied capability (TC-052-pack-checks-cross-check)"},
+    {"id": "TC-052-fixture-surfaces", "acId": "AC-2301-6", "description": "Sample-app fixture serves the console shell with grid matrix and required data attributes", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::sample-app fixture serves console shell with ARIA APG grid permission matrix and required data attributes (TC-052-fixture-surfaces)"},
+    {"id": "TC-052-negative-runs", "acId": "AC-2301-7", "description": "Break switches surface the three defects on the DOM", "status": "pending", "testPointer": "test/blueprint/application-admin-console-anatomy.test.js::sample-app fixture break switches surface the three defects on the DOM (TC-052-negative-runs)"}
+  ],
+  "status": "draft"
+}

package/rcf/user-stories/us-1601.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-09-04T16:21:28.205Z",
+  "updatedAt": "2026-09-04T16:22:01.527Z",
+  "description": "As a project owner shipping non-deterministic behaviour, I want rcf-lite to speak the eval-node surface at every stage of the build cycle so that a non-deterministic AC is graded, audited, verdict-annotated and merge-gated without me holding four disconnected mental models. The surface is one train: audit reports coverage, verify annotates per-AC verdicts, finalise refuses on missing / failing evals with an opt-out, and define authors the determinism flag.",
+  "usId": "US-1601",
+  "prdId": "PRD-001",
+  "reqId": "REQ-016",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The four-track eval-node surface (audit / verdict / finalise / define) reads a single spec across four independent consumers",
+  "asA": "project owner shipping non-deterministic behaviour on an rcf-lite project",
+  "iWant": "rcf-lite to speak the eval-node surface at every stage of the build cycle",
+  "soThat": "a non-deterministic AC is graded, audited, verdict-annotated and merge-gated without me holding four disconnected mental models",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1601-1",
+      "description": "`rcf audit eval coverage --strict` exits 0 on a chain with zero nonDeterministic ACs and exits 4 on any nonDeterministic AC without a resolving EVAL (a non-superseded EVAL whose most recent runRecord entry is not pending). Non-strict runs always exit 0; the mermaid format colours the AC glyph green (deterministic), amber (covered) or red (missing).",
+      "testable": true
+    },
+    {
+      "id": "AC-1601-2",
+      "description": "The verify verdict layer emits EVAL-MISSING on any nonDeterministic AC without a resolving EVAL and EVAL-BELOW-THRESHOLD on any nonDeterministic AC whose bound EVAL last ran with verdict fail. Deterministic ACs never emit either verdict. Both entries ride report.perAcVerdicts[] without expanding the top-level VERDICTS set (backward compatibility on validateReportShape). runStats.evalCoverage rolls up the counts and the CLI prints the preflight line on stderr.",
+      "testable": true
+    },
+    {
+      "id": "AC-1601-3",
+      "description": "rcf finalise refuses (exit 4) with the spec-verbatim message when the verify report carries EVAL-MISSING or EVAL-BELOW-THRESHOLD, and accepts --ship-without-eval <reason> (mandatory reason string; exit 2 without one, refused when the value looks like a flag). The acknowledgement lands on the manifest under shipWithoutEval[] with a monotonic id, the reason, the declared per-AC verdicts and the report path.",
+      "testable": true
+    },
+    {
+      "id": "AC-1601-4",
+      "description": "The LLM-as-judge run path spawns claude (or codex) on PATH, passes the per-case payload on stdin, captures stdout, validates against the declared response schema and composes a runRecord[] entry (aggregateScore, criticalFailures, verdict). No API keys or HTTP APIs enter rcf-lite; the estate subscription-only rule holds. The grader's aggregate verdict is a non-deterministic judgement over graded output, which is the correct home for an EVAL contract on the dogfood tree.",
+      "testable": true,
+      "determinism": "nonDeterministic"
+    }
+  ]
+}