rcf-lite 0.25.0 → 0.27.0

package/blueprints/application-file-upload/contributions/user-stories/application-file-upload-us-23104.json

@@ -13,7 +13,50 @@
       "id": "AC-23104-1",
       "testable": true,
       "scope": "runtime",
-      "description": "On the ?transport=multipart branch the fixture returns 200 with a completed chunk count higher than 1 on a file large enough to force chunking; the DOM exposes [data-transport=\"multipart\"] and [data-chunks-uploaded] whose numeric value equals the completed chunk count. On the ?transport=tus branch the pack observes at least one PATCH request on the browser's network log whose request headers include Upload-Offset with a numeric value, and the DOM exposes [data-transport=\"tus\"] with [data-chunks-uploaded] > 1."
+      "description": "On the ?transport=multipart branch the fixture returns 200 with a completed chunk count higher than 1 on a file large enough to force chunking; the DOM exposes [data-transport=\"multipart\"] and [data-chunks-uploaded] whose numeric value equals the completed chunk count. On the ?transport=tus branch the pack observes at least one PATCH request on the browser's network log whose request headers include Upload-Offset with a numeric value, and the DOM exposes [data-transport=\"tus\"] with [data-chunks-uploaded] > 1.",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://tus.io/protocols/resumable-upload#patch",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-23104-2",
+      "description": "When the transport is tus.io and no tus server or client library prerequisite is available at apply time, apply refuses with TUS_PREREQUISITE_MISSING naming the missing side (server or client) and the remedy to install it; no upload code is written to the project until the prerequisite is present.",
+      "given": "tus transport elicited without the tus server or client dependency installed",
+      "when": "apply runs",
+      "then": "apply exits with a non-zero code, TUS_PREREQUISITE_MISSING names the missing side and the remedy, and no transport code is added",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23104-3",
+      "description": "Upload-Offset on the tus branch matches the byte offset the server has durably acknowledged; a chunk write that returns a non-2xx does not advance Upload-Offset and a subsequent PATCH resumes from the last acknowledged offset.",
+      "given": "a tus upload with a chunk that returns a non-2xx",
+      "when": "the client inspects Upload-Offset and retries",
+      "then": "Upload-Offset reflects the last acknowledged offset only, and the resume PATCH sends bytes from that offset onward",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://tus.io/protocols/resumable-upload#patch",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-23104-4",
+      "description": "A chunk write whose response headers do not include a valid Upload-Offset header (missing, malformed, or beyond the total) is treated as a transport failure: the client refuses to advance and the polite live region announces the failure.",
+      "given": "a chunk response with a malformed or missing Upload-Offset",
+      "when": "the client processes the response",
+      "then": "the client does not advance its offset, the polite live region announces the failure and a retry stays keyboard-reachable",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://tus.io/protocols/resumable-upload#patch",
+        "verifiedOn": "2026-09-10"
+      }
     }
   ],
   "tacIds": [
@@ -24,5 +67,5 @@
     "affordance:chunked-resumable"
   ],
   "createdAt": "2026-09-06T16:55:00Z",
-  "updatedAt": "2026-09-06T16:55:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-file-upload/contributions/user-stories/application-file-upload-us-23105.json

@@ -13,7 +13,42 @@
       "id": "AC-23105-1",
       "testable": true,
       "scope": "runtime",
-      "description": "After the fixture completes the upload set the upload region carries a [data-assertive-slot] element with aria-live=\"assertive\" or role=\"status\" whose textContent matches /^\\d+ files uploaded successfully$/, each completed file row carries [data-file-row][data-file-state=\"complete\"], a keyboard-reachable [data-recovery=\"remove\"] button per row and, after a refused-then-succeeded row, a [data-recovery=\"retry\"] button visible only until the retry succeeds."
+      "description": "After the fixture completes the upload set the upload region carries a [data-assertive-slot] element with aria-live=\"assertive\" or role=\"status\" whose textContent matches /^\\d+ files uploaded successfully$/, each completed file row carries [data-file-row][data-file-state=\"complete\"], a keyboard-reachable [data-recovery=\"remove\"] button per row and, after a refused-then-succeeded row, a [data-recovery=\"retry\"] button visible only until the retry succeeds.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23105-2",
+      "description": "On successful removal (the transport DELETE returns 204 or a defined 200), the upload surface removes the row, announces the removal via the polite live region and no upload artefact remains referenced in the applied data blueprint.",
+      "given": "a completed upload row and a successful DELETE",
+      "when": "the principal activates remove",
+      "then": "the row is removed from the DOM, a polite announcement fires and the applied data blueprint no longer references the artefact",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23105-3",
+      "description": "When the transport DELETE returns a non-2xx or times out, the row remains with data-remove-outcome=failed, the assertive live region announces the failure, no recovery artefact is deleted downstream, and a retry stays keyboard-reachable.",
+      "given": "a completed upload row and a DELETE that returns a non-2xx or times out",
+      "when": "the principal activates remove",
+      "then": "the row remains with data-remove-outcome=failed, the assertive live region announces the failure and a retry is keyboard-reachable",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2402-application-file-upload-transport",
+        "field": "interfaces.removeFile"
+      }
+    },
+    {
+      "id": "AC-23105-4",
+      "description": "The completion once contract: a single upload emits exactly one completion announcement even under a retry; two rapid completions from the same upload id emit one announcement (idempotency of a retried operation).",
+      "given": "an upload that emits two completion events for the same upload id",
+      "when": "the completions are dispatched",
+      "then": "exactly one completion announcement fires and no duplicate data-complete=true is emitted",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -25,5 +60,5 @@
     "affordance:completion"
   ],
   "createdAt": "2026-09-06T16:55:00Z",
-  "updatedAt": "2026-09-06T16:55:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-file-upload/contributions/user-stories/application-file-upload-us-23106.json

@@ -13,7 +13,18 @@
       "id": "AC-23106-1",
       "testable": true,
       "scope": "runtime",
-      "description": "On the ?interrupt=1 branch of the fixture the upload pauses after the first acknowledged chunk, the DOM exposes [data-file-state=\"paused\"] and [data-chunks-uploaded] with a numeric value greater than zero on the paused row, and after the fixture resumes with ?resume=1 the row transitions to [data-file-state=\"complete\"] with the accumulated [data-chunks-uploaded] equal to the total chunk count. The pack asserts no chunk index is re-uploaded (the fixture records the received offsets on the row and never repeats one)."
+      "description": "On the ?interrupt=1 branch of the fixture the upload pauses after the first acknowledged chunk, the DOM exposes [data-file-state=\"paused\"] and [data-chunks-uploaded] with a numeric value greater than zero on the paused row, and after the fixture resumes with ?resume=1 the row transitions to [data-file-state=\"complete\"] with the accumulated [data-chunks-uploaded] equal to the total chunk count. The pack asserts no chunk index is re-uploaded (the fixture records the received offsets on the row and never repeats one).",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23106-2",
+      "description": "When the resume PATCH lands but the server responds with an Upload-Offset less than the client-known offset (a lost server-side state), the client aborts the upload with UPLOAD_OFFSET_REGRESSION rather than replaying bytes; the row remains with a defined failure and a manual retry option.",
+      "given": "a resume attempt where the server returns a lower Upload-Offset than the client tracked",
+      "when": "the client processes the response",
+      "then": "the upload aborts with UPLOAD_OFFSET_REGRESSION, the row shows the defined failure and a manual retry is offered",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -24,5 +35,5 @@
     "affordance:resumption"
   ],
   "createdAt": "2026-09-06T16:55:00Z",
-  "updatedAt": "2026-09-06T16:55:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-file-upload/contributions/user-stories/application-file-upload-us-23107.json

@@ -13,7 +13,22 @@
       "id": "AC-23107-1",
       "testable": true,
       "scope": "runtime",
-      "description": "On the ?background=1 branch of the fixture the fixture drives a visibilitychange event to hidden, the upload continues (the aggregate percent advances between two polite-tick reads separated by at least one polling interval), and the [data-live-region=\"polite\"] wrapper's text updates. The pack reads the wrapper twice with a wait between and asserts the aggregate percent increased and the tick text changed."
+      "description": "On the ?background=1 branch of the fixture the fixture drives a visibilitychange event to hidden, the upload continues (the aggregate percent advances between two polite-tick reads separated by at least one polling interval), and the [data-live-region=\"polite\"] wrapper's text updates. The pack reads the wrapper twice with a wait between and asserts the aggregate percent increased and the tick text changed.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23107-2",
+      "description": "The polite live region continues to tick under prefers-reduced-motion: reduce; only the animated visual progress indicator switches to a static text ratio (\"3 of 5 MiB\"), the announcement cadence and shape are unchanged.",
+      "given": "a user agent asserting prefers-reduced-motion: reduce",
+      "when": "an upload is in-flight",
+      "then": "the polite live region announcements continue at the same cadence and the visual indicator switches to static text",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/TR/WCAG22/#animation-from-interactions",
+        "verifiedOn": "2026-09-10"
+      }
     }
   ],
   "tacIds": [
@@ -24,5 +39,5 @@
     "affordance:background-tab-progress"
   ],
   "createdAt": "2026-09-06T16:55:00Z",
-  "updatedAt": "2026-09-06T16:55:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-file-upload/docs/topics.md

@@ -26,7 +26,7 @@ The blueprint claims no new global topics at v1.0.0. Every ADR (transport branch
 | application-account-settings | 25101-25899 | 26xx | shipped v1.0.0 | none |
 | application-onboarding-tour | 26101-26899 | 27xx | shipped v1.0.0 | none |
 | persistence-data-postgres | 27101-27899 | 28xx | shipped v1.0.0 | `persistenceStore`, `migrationDiscipline` |
-| object-storage-s3 | 28101-28899 | 29xx | shipped v1.0.0 | `objectStorageContract` |
+| object-storage-s3 | 28101-28899 | 29xx | shipped v1.1.0 | `objectStorageContract` |
 | messaging-queue-cloudflare | 29101-29899 | 30xx | shipped v1.0.0 | `deliverySemantics` |
 | jobs-background | 30101-30899 | 31xx | shipped v1.0.0 | `backgroundJobModel` |
 | platform-cloudflare-kv | 31101-31899 | 32xx | shipped v1.0.0 | `keyValueStoreContract` |

package/blueprints/application-file-upload/probe-packs/application-file-upload.pack.mjs

@@ -7,9 +7,9 @@
 //   AC-23103-1 refusal contract    (aria-describedby, no bytes for refused)
 //   AC-23104-1 chunked transport   (multipart chunks OR tus Upload-Offset)
 //
-// Every check drives the real Playwright browser the T-0 runner
+// Every check drives the real Playwright browser the runner
 // injects. URLs are composed by the withUrl(runtimeUrl, path) helper
-// per the round 3 T-3 fix train; no bare string concatenation.
+// per the round 3 fix train; no bare string concatenation.
 //
 // Sample-app fixture:
 // packages/rcf-lite/test/fixtures/probe-pack-application-file-upload/
@@ -32,8 +32,8 @@ export default {
   blueprintSlug: 'application-file-upload',
   // Applies to any FBS that binds the input TAC or whose navModel
   // routes name the operator-configured upload path. References BOTH
-  // `tacIds` AND `route` per the loader source-scan rule (T-0
-  // AC-1701-3, cross-check with authoring standard 8c).
+  // `tacIds` AND `route` per the loader source-scan rule
+  // (AC-1701-3, cross-check with authoring standard 8c).
   appliesTo: ({ fbs }) => {
     const routes = fbs?.designStage?.navModel?.routes ?? [];
     const tacIds = fbs?.contextRequirements?.tacIds ?? [];
@@ -178,7 +178,16 @@ export default {
         if (dom.sentRefused) {
           return { verdict: 'fail', detail: `refused filename ${JSON.stringify(dom.refusedFilename)} appears in the upload request log` };
         }
-        return { verdict: 'pass', detail: `reason=${JSON.stringify(dom.reason)} err=${JSON.stringify(dom.errText)} no refused bytes on the wire (${dom.network.length} recorded upload requests)` };
+        // positive refusal-receipt: assert the row exposes a per-file [data-refusal-receipt] keyed by file id.
+                const receipt = await browser.evaluate(() => {
+                  const row = document.querySelector('[data-file-row][data-refused="true"]');
+                  const rec = row ? row.querySelector('[data-refusal-receipt]') : null;
+                  const fileId = row ? row.getAttribute('data-file-id') : null;
+                  return { hasReceipt: !!rec, receiptFileId: rec ? rec.getAttribute('data-refusal-receipt') : null, fileId };
+                });
+                if (!receipt.hasReceipt) return { verdict: 'fail', detail: 'refused row missing positive [data-refusal-receipt] marker' };
+                if (!receipt.receiptFileId || receipt.receiptFileId !== receipt.fileId) return { verdict: 'fail', detail: `refusal-receipt file id ${JSON.stringify(receipt.receiptFileId)} does not match row file id ${JSON.stringify(receipt.fileId)}` };
+                return { verdict: 'pass', detail: `reason=${JSON.stringify(dom.reason)} err=${JSON.stringify(dom.errText)} refusal-receipt fileId=${receipt.fileId}` };
       },
     },
     {

package/blueprints/application-forms-wizard/CHANGELOG.md

@@ -1,9 +1,40 @@
 # application-forms-wizard CHANGELOG
 
-## 1.0.0 (visual round T-3, spec 2026-09-06)
+## 1.2.0 (2026-09-10)
+
+### Added
+
+- Five elicits (`step-manifest`, `navigation`, `step-indicator`, `draft-transport`, `validation-policy`) declared on blueprint.json; REQ-006 binds one runtime clause per apply-time answer family.
+- Vendor citations on AC-24101-1 (GOV.UK task-list) and AC-24103-1 (ARIA aria-invalid).
+
+### Changed
+
+- AC-24106-2 references `ADR-2503.decision` via ownerRef (`task-list` / `aria-progressbar-only` / `breadcrumb`).
+- REQ-002.deliveredBy retargeted to `TAC-2502.responsibilities.validationTimingGate` (new responsibility carrying the on-blur / on-change / on-submit clauses).
+- REQ-003.deliveredBy retargeted to `TAC-2502.interfaces.renderSummary`.
+- REQ-004.deliveredBy retargeted to `TAC-2501.responsibilities.renderSummaryReview` (new responsibility).
+- AC-24101-1 references `TAC-2501.interfaces.statesEnum` via ownerRef; drops the four-value restatement.
+
+## 1.1.1 (register-sweep patch, 2026-09-10)
+
+- Register: neutral wording in shipped prose (no capability change).
+
+## 1.1.0 (2026-09-10, hardening pass)
+
+### Added
+
+- Failure-path acceptance criteria on US-24101 (STEP_STATE_UNKNOWN refusal, Cannot start yet blocker announcement), US-24102 (error summary field bindings, throwing validator surface), US-24103 (submit refusal focus and summary link focus contract), US-24104 (summary submit failure preserves answers), US-24105 (server-side POST failure with unsaved banner, localStorage denial with fallback, hydrate failure), US-24106 (step-indicator apply refusal for values outside the closed set), US-24107 (in-progress list read failure with cache, cross-principal draft refusal), US-24108 (fallback empty message when application-empty-error-states not applied). Closes review finding F-1.
+- Vendor citations on the GOV.UK task-list-pages and error-summary acceptance criteria (verified 2026-09-10).
+
+### Changed
+
+- Every REQ now carries a deliveredBy link into TAC-2501 (task-list), TAC-2502 (error-summary) or TAC-2503 (draft-store).
+- Every AC on every user story now carries an explicit disposition (fixed or template).
+
+## 1.0.0 (visual round, spec 2026-09-06)
 
 - First ratified version of the shelf's forms-wizard blueprint. Five REQs (task-list contract with the closed GOV.UK vocabulary Cannot start yet, Not started, In progress, Completed and an ARIA progressbar wrapper; per-step validation timing with on-blur before first submit then on-change after first failure and a full pass on submit reusing SPA forms-engine TAC-205; error-summary contract with a top-of-page summary, skip links, aria-invalid on the field, aria-describedby to the field-level message and focus moved to the summary heading; summary-review contract with a summary-list per step, Change links per row and answer retention on save; save-and-return contract with a server-side draft table or a client-side local buffer with a sync tick, refuses to ship if neither is wired), eight USs 24101 to 24108 binding one runtime-observable AC per contract plus three cross-cutting cases (linear-vs-free navigation, in-progress list, no-in-progress empty state delegated to application-empty-error-states), three TACs 2501 to 2503 (task-list shell, error-summary contract, draft store), three ADRs 2501 to 2503 (navigation posture linear default with elicited free branch, save-and-return transport with no recommendedDefault so the abandoned-draft loss class does not ship silently, step-indicator shape with task-list default and elicited ARIA progressbar-only or breadcrumb). No new global topics.
-- Ships `probe-packs/application-forms-wizard.pack.mjs`: four surface-observable browser-verify checks anchored one per core contract (`AC-24101-1` task-list, `AC-24103-1` error-summary, `AC-24104-1` summary-review, `AC-24105-1` save-and-return). Every URL is composed by the `withUrl(runtimeUrl, path)` helper per the round 3 T-3 fix train; no bare string concatenation. The pack-level `appliesTo` predicate references BOTH `tacIds` (TAC-2501) AND `route` (the operator-configured wizard-route glob).
+- Ships `probe-packs/application-forms-wizard.pack.mjs`: four surface-observable browser-verify checks anchored one per core contract (`AC-24101-1` task-list, `AC-24103-1` error-summary, `AC-24104-1` summary-review, `AC-24105-1` save-and-return). Every URL is composed by the `withUrl(runtimeUrl, path)` helper per the round 3 fix train; no bare string concatenation. The pack-level `appliesTo` predicate references BOTH `tacIds` (TAC-2501) AND `route` (the operator-configured wizard-route glob).
 - Ships a dependency-free sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-forms-wizard/` with a Node HTTP server realising the four wizard surfaces honestly (`/task-list`, `/step/<n>`, `/summary`, `/in-progress`), both save-and-return transports on their query branches (`?draft-store=server` default posting to `/drafts`, `?draft-store=local` writing to `localStorage` with a sync tick), and four break switches (`?break=task-list-vocab`, `?break=no-summary`, `?break=no-retain`, `?break=no-draft`) driving the negative runs from a single boot. The fixture ships its own README naming PORT, every `?step=`, `?draft-store=`, `?nav=`, `?seed=`, `?refused=`, `?preseed=`, `?edit=`, every `?break=`, the manual boot line and the two-line gate-reviewer boot.
 - Declares `suggestedCompanions` `logging` (every step transition, validation failure and save-and-return event writes one request-scoped log line with the correlation identifier and the step slug) and `errorHandling` (the error-summary contract constructs an internal error record per failed field through the applied error-handling factory). Does NOT declare `providesRoles` (leaf blueprint per spec). Does NOT declare `capabilities` and does NOT declare `requiresAppliedCapabilities` (no auth required).
-- Consumes `application-empty-error-states` for the no-in-progress empty state on the /in-progress list surface; the wizard's TAC-2503 delegates the zero-drafts case to the sibling's empty-list state and reads `[data-surface="empty-list"]` with a `[data-recovery="create"]` control from the sibling. T-4 `application-account-settings` will consume this blueprint for its multi-part account setup flow and the summary-review confirm-before-save gate.
+- Consumes `application-empty-error-states` for the no-in-progress empty state on the /in-progress list surface; the wizard's TAC-2503 delegates the zero-drafts case to the sibling's empty-list state and reads `[data-surface="empty-list"]` with a `[data-recovery="create"]` control from the sibling. `application-account-settings` will consume this blueprint for its multi-part account setup flow and the summary-review confirm-before-save gate.

package/blueprints/application-forms-wizard/README.md

@@ -66,7 +66,7 @@ The in-progress-list surface delegates the zero-drafts case to the `application-
 
 ## The one runtime gate
 
-`probe-packs/application-forms-wizard.pack.mjs` ships four checks the `rcf verify browser` runner invokes on any FBS whose surface binds `TAC-2501-application-forms-wizard-task-list` or whose nav model routes name an operator-configured wizard path. Each check drives the real Playwright browser the runner provisions, reads the DOM and the accessibility tree, and returns a verdict. URLs are composed by the `withUrl(runtimeUrl, path)` helper per the round 3 T-3 fix train; no bare string concatenation.
+`probe-packs/application-forms-wizard.pack.mjs` ships four checks the `rcf verify browser` runner invokes on any FBS whose surface binds `TAC-2501-application-forms-wizard-task-list` or whose nav model routes name an operator-configured wizard path. Each check drives the real Playwright browser the runner provisions, reads the DOM and the accessibility tree, and returns a verdict. URLs are composed by the `withUrl(runtimeUrl, path)` helper per the round 3 fix train; no bare string concatenation.
 
 ## Quality bar
 
@@ -91,7 +91,7 @@ Runtime-observable ACs the pack does NOT bind directly (checklist section 6.g),
 
 ## Consumers
 
-- `application-account-settings` (T-4 of this round) consumes the wizard task-list pattern for its multi-part account setup flow and the summary-review pattern for its confirm-before-save gate.
+- `application-account-settings` (of this round) consumes the wizard task-list pattern for its multi-part account setup flow and the summary-review pattern for its confirm-before-save gate.
 
 ## Composition with application-spa
 

package/blueprints/application-forms-wizard/blueprint.json

@@ -1,6 +1,6 @@
 {
   "slug": "application-forms-wizard",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "category": "application",
   "suggestedCompanions": [
     {
@@ -38,6 +38,11 @@
       "kind": "req",
       "path": "requirements/application-forms-wizard-req-005.json"
     },
+    {
+      "id": "application-forms-wizard-REQ-006",
+      "kind": "req",
+      "path": "requirements/application-forms-wizard-req-006.json"
+    },
     {
       "id": "application-forms-wizard-US-24101",
       "kind": "us",
@@ -116,5 +121,56 @@
       "elicited": true,
       "standardsTraceClause": "GOV.UK Design System task list pattern; WCAG 2.2 SC 2.4.6 Headings and Labels"
     }
+  ],
+  "elicits": [
+    {
+      "id": "step-manifest",
+      "prompt": "Wizard step manifest: comma-separated step slugs in order.",
+      "kind": "string",
+      "default": "about,detail,confirm"
+    },
+    {
+      "id": "navigation",
+      "prompt": "Step navigation model: linear (steps are gated by prerequisites) or free (any step reachable at any time).",
+      "kind": "enum",
+      "options": [
+        "linear",
+        "free"
+      ],
+      "default": "linear"
+    },
+    {
+      "id": "step-indicator",
+      "prompt": "Step-indicator surface: task-list (recommended default), aria-progressbar-only, or breadcrumb.",
+      "kind": "enum",
+      "options": [
+        "task-list",
+        "aria-progressbar-only",
+        "breadcrumb"
+      ],
+      "default": "task-list"
+    },
+    {
+      "id": "draft-transport",
+      "prompt": "Draft persistence transport: spa-local-storage (default), server-scoped, or none.",
+      "kind": "enum",
+      "options": [
+        "spa-local-storage",
+        "server-scoped",
+        "none"
+      ],
+      "default": "spa-local-storage"
+    },
+    {
+      "id": "validation-policy",
+      "prompt": "Validation policy: on-blur-then-on-change (default per REQ-002), on-change-always, or on-submit-only.",
+      "kind": "enum",
+      "options": [
+        "on-blur-then-on-change",
+        "on-change-always",
+        "on-submit-only"
+      ],
+      "default": "on-blur-then-on-change"
+    }
   ]
 }

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-001.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Task-list contract: per-step completion state announced through the GOV.UK vocabulary Cannot start yet, Not started, In progress, Completed",
   "description": "The wizard renders a task-list surface listing every step in a stable order. Each step exposes one of four completion states from the closed GOV.UK vocabulary: Cannot start yet (a prerequisite step is unfinished), Not started (the step is reachable but has no answers), In progress (the step has partial answers), Completed (the step is fully valid). The task-list carries an ARIA progressbar shape naming the total step count and the number completed. The four state strings are a closed enum at v1.0.0; a fifth state is a v1.1.0 minor bump. The surface anchors on TAC-2501 (task-list shell) and is vendor-neutral: the blueprint contributes WHAT strings under WHAT condition, not the visual token set.",
+  "deliveredBy": {
+    "tacId": "TAC-2501-application-forms-wizard-task-list",
+    "field": "interfaces.renderTaskList"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-002.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Per-step validation timing: on-blur before first submit, then on-change after the first failure, and a full pass on submit reusing the SPA forms-engine",
   "description": "Every step validates its own answers before advancing. Validation timing is on-blur before the first submit attempt on a step (a field validates when the operator leaves it), then on-change after the first submit failure on that field (so the operator sees the message clear as they correct it), and a full pass on submit that rebuilds the error set from scratch. Validation delegates to the SPA blueprint's forms-engine TAC-205 so a project already applying application-spa does not compose two overlapping engines. On refusal the engine surfaces the failed fields to the error-summary contract (REQ-003). The timing rule is a closed set at v1.0.0; different projects can elicit stricter (validate on every change from the start) via a project-level ADR but the shipped default is the three-mode rule above.",
+  "deliveredBy": {
+    "tacId": "TAC-2502-application-forms-wizard-error-summary",
+    "field": "responsibilities.validationTimingGate"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
@@ -11,8 +15,8 @@
     "blueprint:application-forms-wizard",
     "category:02-validation-timing"
   ],
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-003.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Error-summary contract: top-of-page summary with skip links per failed field, aria-invalid on the field, and focus moved to the summary heading on submit failure",
   "description": "On submit refusal the step renders a top-of-page error summary region carrying a heading and one skip link per failed field. Each skip link's target is a focusable field element; the field carries aria-invalid=\"true\" while unresolved and aria-describedby pointing at the field-level error message. On submit failure the client moves focus to the summary heading so a screen-reader user hears the error class and can walk the skip links; visual users see the heading anchor scroll into view. The summary and per-field bindings anchor on TAC-2502 (error-summary contract). Per WCAG 2.2 SC 3.3.1 Error Identification and SC 3.3.3 Error Suggestion.",
+  "deliveredBy": {
+    "tacId": "TAC-2502-application-forms-wizard-error-summary",
+    "field": "interfaces.renderSummary"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
@@ -11,8 +15,8 @@
     "blueprint:application-forms-wizard",
     "category:03-error-summary"
   ],
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-004.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Summary-review contract: a summary-list rendering per step with Change links returning to each step and retaining every other answer on save",
   "description": "After every step is Completed (per REQ-001) the wizard renders a summary-review surface: one summary-list section per step, each row a definition-list entry naming the field label and the operator's answer, and a Change link per row that navigates to the step with the field focused. Editing on the target step and saving returns to the summary-review surface with every other answer retained; only the edited answer is updated. The summary-list shape follows the GOV.UK Design System summary-list pattern. Per WCAG 2.2 SC 3.3.4 Error Prevention (Legal, Financial, Data): the summary-review is the last checkpoint before submission and every answer is reversible up to submit.",
+  "deliveredBy": {
+    "tacId": "TAC-2501-application-forms-wizard-task-list",
+    "field": "responsibilities.renderSummaryReview"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
@@ -11,8 +15,8 @@
     "blueprint:application-forms-wizard",
     "category:04-summary-review"
   ],
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-005.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Save-and-return contract: a server-side draft table or a client-side local buffer with a sync tick; refuses to ship if neither is wired",
   "description": "The wizard commits partial answers between steps to a draft store so an operator can leave the surface and return without losing progress. Two transports ship: a server-side draft table (POST /drafts persists per-operator per-wizard rows, GET /drafts hydrates on return) and a client-side local buffer (localStorage keyed by operator identifier and wizard slug with a per-write sync tick). ADR-2502 commits to no recommendedDefault because the abandoned-draft loss class is genuinely per-project. A wizard that ships without either transport is refused at build gate: the draft-store TAC is a required companion. Per WCAG 2.2 SC 3.3.7 Redundant Entry: information the operator has already entered is preserved across sessions and not re-solicited.",
+  "deliveredBy": {
+    "tacId": "TAC-2503-application-forms-wizard-draft-store",
+    "field": "interfaces.resolveTransport"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",

package/blueprints/application-forms-wizard/contributions/requirements/application-forms-wizard-req-006.json

@@ -0,0 +1,21 @@
+{
+  "reqId": "application-forms-wizard-REQ-006",
+  "prdId": "PRD-001",
+  "title": "Apply-time answer families bind the five elicits to the wizard contract",
+  "description": "When the applying project answers the five apply-time elicits, the wizard honours each with a runtime clause per family: `blueprint.json.elicits[id=step-manifest]` populates the step order the task-list enumerates; `blueprint.json.elicits[id=navigation]` picks the linear-vs-free branch on TAC-2501 (linear gates rows by prerequisites; free allows anchor navigation to every row); `blueprint.json.elicits[id=step-indicator]` picks the indicator surface owned by `ADR-2503.decision`; `blueprint.json.elicits[id=draft-transport]` picks the draft-store backend on TAC-2503 (spa-local-storage default; server-scoped delegates to the applied persistence blueprint; none disables draft persistence); `blueprint.json.elicits[id=validation-policy]` sets the on-blur/on-change/on-submit gate on TAC-2502.",
+  "deliveredBy": {
+    "tacId": "TAC-2501-application-forms-wizard-task-list",
+    "field": "responsibilities.applyElicits"
+  },
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "rationale": "The five apply-time answer families named in the guide needed one must REQ per family so a project cannot elicit a value and see it ignored silently.",
+  "tags": [
+    "blueprint:application-forms-wizard"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-10T00:00:00Z",
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-forms-wizard/contributions/tacs/tac-2501-application-forms-wizard-task-list.json

@@ -2,7 +2,7 @@
   "tacId": "TAC-2501-application-forms-wizard-task-list",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Wizard task-list shell",
   "purpose": "Owns the task-list surface of the wizard: the ordered enumeration of steps, the per-step completion-state slot from the closed GOV.UK vocabulary, the ARIA progressbar wrapper, and the linear-or-free navigation gate. Every AC on REQ-001 anchors on this TAC, and every AC that reads step order anchors here.",
@@ -11,7 +11,9 @@
     "Render [data-step-state] on every row from the closed enum {Cannot start yet, Not started, In progress, Completed} (AC-24101-1).",
     "Render an ARIA progressbar wrapper on the surface with aria-valuenow (completed count), aria-valuemax (total step count) and aria-valuetext naming the completion in words (AC-24101-1).",
     "Honour the ADR-2501 linear-vs-free branch by rendering rows whose prerequisites are unfinished as non-anchor spans on linear and as anchors on free (AC-24106-1).",
-    "Delegate to TAC-2503 to hydrate step states from the draft store on entry and to persist step completion transitions on advance."
+    "Delegate to TAC-2503 to hydrate step states from the draft store on entry and to persist step completion transitions on advance.",
+    "renderSummaryReview: render the per-step summary-list at review time with Change links returning to each step and retaining every other answer on save (REQ-004).",
+    "applyElicits: at apply time, dispatch each of the five answer families to its owner interface: `step-manifest` populates the step order enumerated by the task-list; `navigation` picks the linear-or-free branch on the task-list; `step-indicator` selects the indicator surface owned by `ADR-2503.decision`; `draft-transport` binds the draft-store backend on `TAC-2503`; `validation-policy` sets the timing gate on `TAC-2502.validationTimingGate`. Per REQ-006."
   ],
   "internalStructure": "One task-list module the shell mounts on the /task-list route. On mount it reads the step manifest, reads the draft store for the operator's per-step answers, computes the per-step completion state from the answers, renders the enumeration, and wires the row-click handler to the linear-vs-free branch. On step advance the module recomputes the state for the just-completed step and updates the progressbar aria-valuenow. Framework is not prescribed; the module's interfaces are what the project realises against React, Vue, Svelte or vanilla DOM.",
   "interfaces": [
@@ -42,5 +44,5 @@
   "tradeoffs": "One task-list module keeps the enumeration deterministic and lint-checkable but ties every step to a manifest entry the project supplies. A project rendering the wizard without a task-list (a single-flow submit surface with no completion overview) does not apply this TAC; the wizard-shell TACs still hold. Known mechanism-reach gap: the pack asserts row order and state strings but does not additionally probe that focus moves to the task-list on route entry; a v1.1.0 minor bump can drive the accessibility tree.",
   "notes": "See README Known mechanism-reach gaps.",
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
-}
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-forms-wizard/contributions/tacs/tac-2502-application-forms-wizard-error-summary.json

@@ -2,7 +2,7 @@
   "tacId": "TAC-2502-application-forms-wizard-error-summary",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Wizard error-summary contract",
   "purpose": "Owns the top-of-page error-summary contract on submit refusal: the summary region, the skip-link binding per failed field, the aria-invalid and aria-describedby marking on the fields themselves, the focus move to the summary heading, and the validation-timing gate the SPA forms-engine drives per REQ-002. Every AC on REQ-002 and REQ-003 anchors on this TAC.",
@@ -11,7 +11,8 @@
     "Mark every failed field with aria-invalid=\"true\" and aria-describedby pointing at its per-field error message id (AC-24103-1).",
     "Move focus to the summary heading on submit failure (AC-24103-1).",
     "Delegate validation to the SPA forms-engine TAC-205 on the on-blur, on-change and on-submit triggers per REQ-002 (AC-24102-1); this TAC does not re-implement validation, it consumes the engine.",
-    "Clear aria-invalid on a field when its message clears and remove the anchor from the summary on the next successful submit."
+    "Clear aria-invalid on a field when its message clears and remove the anchor from the summary on the next successful submit.",
+    "validationTimingGate: honour the elicited validation-policy (on-blur-then-on-change default, on-change-always, on-submit-only) by wiring the SPA forms-engine triggers accordingly (REQ-002)."
   ],
   "internalStructure": "One error-summary module the shell mounts inside the step surface. On submit refusal the module reads the engine's error set, renders the anchor list, moves focus, and wires the anchor click to focus the corresponding field. On subsequent input events after the first failure the module re-runs the engine per-field and updates the message; on the next submit the module rebuilds the error set from scratch. Framework is not prescribed; the interfaces are what the project realises.",
   "interfaces": [
@@ -36,5 +37,5 @@
   "tradeoffs": "Consuming the SPA forms-engine keeps a project on the shelf free from a second overlapping engine but ties this TAC to the SPA blueprint's validation shape. Known mechanism-reach gap: the pack asserts the summary and the aria bindings but does not additionally probe the focus-order sweep across every field in the DOM after focus moves to the heading; a v1.1.0 minor bump can walk the tab order and diff.",
   "notes": "See README Known mechanism-reach gaps.",
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-forms-wizard/contributions/user-stories/application-forms-wizard-us-24101.json

@@ -13,7 +13,40 @@
       "id": "AC-24101-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given the wizard task-list route, the rendered surface exposes [data-surface=\"task-list\"] carrying a [role=\"progressbar\"] with aria-valuenow, aria-valuemax and aria-valuetext, and one child element per step carrying [data-step-slug] and [data-step-state] whose value is one of the closed set {Cannot start yet, Not started, In progress, Completed}. The pack drives the real browser to /task-list and reads the state string per step, the progressbar values, and the enumerated step order."
+      "description": "Given the wizard task-list route, the rendered surface exposes [data-surface=\"task-list\"] carrying a [role=\"progressbar\"] with aria-valuenow, aria-valuemax and aria-valuetext, and one child element per step carrying [data-step-slug] and [data-step-state] whose value is drawn from the closed enum owned by `TAC-2501.interfaces.statesEnum`. The pack drives the real browser to /task-list and reads the state string per step, the progressbar values, and the enumerated step order. (Progressbar ARIA role verified against https://www.w3.org/TR/wai-aria-1.2/#progressbar, 2026-09-10.)",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2501-application-forms-wizard-task-list",
+        "field": "interfaces.statesEnum"
+      },
+      "vendorCitation": {
+        "url": "https://design-system.service.gov.uk/patterns/task-list-pages/",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-24101-2",
+      "description": "Every step row carries exactly one of the four GOV.UK completion states (Not started, In progress, Cannot start yet, Completed) as data-step-state; an unknown value refuses to render (data-error=STEP_STATE_UNKNOWN is emitted and the row is suppressed).",
+      "given": "a task-list with a step whose state is outside the four-state enum",
+      "when": "the surface renders",
+      "then": "the row is suppressed, data-error=STEP_STATE_UNKNOWN is emitted and no fallback state renders",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://design-system.service.gov.uk/patterns/task-list-pages/",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-24101-3",
+      "description": "A Cannot-start-yet step lists its blocking dependencies in an aria-describedby-bound description; activating a blocked step is refused with focus preserved on the row and a polite live-region announcement of the block.",
+      "given": "a step in Cannot start yet state with named blockers",
+      "when": "the principal activates the row",
+      "then": "the row does not navigate, focus stays and the polite live region announces the block",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -24,5 +57,5 @@
     "contract:task-list"
   ],
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }