rcf-lite 0.26.0 → 0.28.0

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

@@ -13,7 +13,18 @@
       "id": "AC-23103-1",
       "testable": true,
       "scope": "runtime",
-      "description": "When the fixture is seeded with a refused file (MIME mismatch, size cap exceeded, or virus-scan hit), the file row [data-file-row][data-refused=\"true\"] renders a [data-error-message] element whose id is referenced by the row's aria-describedby attribute, the row exposes the closed refusal reason via [data-refusal-reason] (one of mime-refused, size-refused, virus-refused), a [data-recovery=\"retry\"] control receives keyboard focus, and the pack observes zero POST or PATCH requests carrying the refused filename on the browser's request log."
+      "description": "When the fixture is seeded with a refused file (MIME mismatch, size cap exceeded, or virus-scan hit), the file row [data-file-row][data-refused=\"true\"] renders a [data-error-message] element whose id is referenced by the row's aria-describedby attribute, the row exposes the closed refusal reason via [data-refusal-reason] (one of mime-refused, size-refused, virus-refused), a [data-recovery=\"retry\"] control receives keyboard focus, and the pack observes zero POST or PATCH requests carrying the refused filename on the browser's request log.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-23103-2",
+      "description": "On a per-file transport failure (non-2xx from the transport POST/PATCH), the row renders with data-file-outcome=failed and focus moves to a retry control on the row; a subsequent retry starts from the last acknowledged Upload-Offset on tus.",
+      "given": "a per-file upload that fails on the transport",
+      "when": "the failure is reported",
+      "then": "the row shows data-file-outcome=failed, focus lands on the retry control and retry starts from the last acknowledged offset",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -25,5 +36,5 @@
     "affordance:refusal"
   ],
   "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-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/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.
+// that joins runtime URL and path safely; 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,54 @@
 # application-forms-wizard CHANGELOG
 
-## 1.0.0 (visual round T-3, spec 2026-09-06)
+## 1.2.6 - 2026-09-11
 
-- 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 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.
+- task-list-surface now emits a notObservableHere row for AC-24101-1 alongside the existing conformanceOnly server row: the AC contract names driving the real browser to /task-list and reading data-step-state per step, the progressbar aria values and the enumerated step order from the rendered DOM. The AC is now represented on the shelf as (i) a conformanceOnly counting row observing the varied-manifest surface derived from /__task-manifest.allowedStates and (ii) a notObservableHere row carrying the AC id and the browser-observable-half reason.
+- Anatomy test pin bumped to 1.2.6.
+
+## 1.2.5 - 2026-09-11
+
+- Adds a contributions/probes pack meeting rule 7d.
+- Probes: task-list-surface, step-page-shape, draft-persistence-round-trip.
+- Task-list order and progressbar values are derived from two varied manifests the probe controls; AC-24101-1 is a conformanceOnly row because the closed enum is validated against the fixture's /__task-manifest rather than a shipped enum from the applying project; the row carries a limitation naming that gap and the AC id.
+- Validation timing (blur/change/submit) is a conformanceOnly row anchored on AC-24102-1: the probe drives /validate twice (an invalid submit then a valid submit that references the prior errorCount) and asserts the /validate rebuild count differs across the two calls; the limitation names that the DOM-side blur/change/submit browser events are not observable on a server-driven probe pack.
+- Anatomy test pin bumped to 1.2.5.
+
+
+## 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)
+
+### Added
+
+- Failure-path acceptance criteria added 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), so applying projects have explicit failure-path acceptance criteria on each story.
+- 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 (2026-09-06)
+
+- Initial shipped 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; 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 manual 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

@@ -54,7 +54,7 @@ ADR-2502 commits to two transports without recommendedDefault. The server-side d
 
 ## The no-in-progress empty case
 
-The in-progress-list surface delegates the zero-drafts case to the `application-empty-error-states` empty-list state (`[data-surface="empty-list"]` with a `[data-recovery="create"]` control). The wizard blueprint does not ship its own empty component; a project applying both blueprints reads the same surface from either lane.
+The in-progress-list surface delegates the zero-drafts case to the `application-empty-error-states` empty-list state (`[data-surface="empty-list"]` with a `[data-recovery="create"]` control). The wizard blueprint does not ship its own empty component; a project applying both blueprints reads the same surface from either blueprint.
 
 ## Elicited parameters
 
@@ -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; 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.6",
   "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,57 @@
       "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"
+    }
+  ],
+  "updatedAt": "2026-09-11T16:04:17Z"
 }

package/blueprints/application-forms-wizard/contributions/probes/draft-persistence-round-trip.mjs

@@ -0,0 +1,110 @@
+// draft-persistence-round-trip probe for application-forms-wizard v1.2.6.
+//
+// Verifies AC-24105-1: POST /drafts with { operatorId, wizardSlug,
+// step, field, value } persists the answer scoped to the operator
+// and wizard; a subsequent fresh GET /drafts?operatorId=&wizardSlug=
+// returns the same field with an updatedAt timestamp. Two round
+// trips with different values under the same scope prove the store
+// is real state, and a second operator's write proves the scope
+// key is honoured (AC-24105-1's per-operator, per-wizard scope).
+//
+// anchorAcId: application-forms-wizard-AC-24105-1.
+
+import { startFixture, evidenceFromResponse } from './probe-utils.mjs';
+
+export const anchorReqId = 'application-forms-wizard-REQ-005';
+export const accountBound = false;
+
+export default async function runProbe() {
+  const { startServer } = await import('../../../../packages/rcf-lite/test/fixtures/probe-pack-application-forms-wizard/server.js');
+  const fixture = await startFixture({ startServer, port: 0 });
+  try {
+    const results = [];
+
+    const OP_A = 'probe-op-a';
+    const OP_B = 'probe-op-b';
+    const WIZ = 'application-forms-wizard';
+    const KEY = 'contact-details.fullName';
+
+    // Step 1: OP_A writes then overwrites.
+    const seed1a = { operatorId: OP_A, wizardSlug: WIZ, step: 'contact-details', field: 'fullName', value: 'Probe Runner' };
+    const seed2a = { operatorId: OP_A, wizardSlug: WIZ, step: 'contact-details', field: 'fullName', value: 'Second Value' };
+    const post1a = await fetch(`${fixture.baseUrl}/drafts`, { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify(seed1a) });
+    const get1a = await fetch(`${fixture.baseUrl}/drafts?operatorId=${OP_A}&wizardSlug=${WIZ}`);
+    const drafts1a = JSON.parse(await get1a.text());
+    const post2a = await fetch(`${fixture.baseUrl}/drafts`, { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify(seed2a) });
+    const get2a = await fetch(`${fixture.baseUrl}/drafts?operatorId=${OP_A}&wizardSlug=${WIZ}`);
+    const get2aBody = await get2a.text();
+    const drafts2a = JSON.parse(get2aBody);
+    const persistedA1 = drafts1a.fields && drafts1a.fields[KEY] === seed1a.value;
+    const persistedA2 = drafts2a.fields && drafts2a.fields[KEY] === seed2a.value;
+    const overwrittenA = persistedA1 && persistedA2 && drafts1a.fields[KEY] !== drafts2a.fields[KEY];
+
+    // Step 2: OP_B writes a different value under the same key; if
+    // scope is honoured, OP_A's value stays "Second Value" and OP_B
+    // gets its own.
+    const seedB = { operatorId: OP_B, wizardSlug: WIZ, step: 'contact-details', field: 'fullName', value: 'Op B Value' };
+    const postB = await fetch(`${fixture.baseUrl}/drafts`, { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify(seedB) });
+    const getB = await fetch(`${fixture.baseUrl}/drafts?operatorId=${OP_B}&wizardSlug=${WIZ}`);
+    const draftsB = JSON.parse(await getB.text());
+    const getAAgain = await fetch(`${fixture.baseUrl}/drafts?operatorId=${OP_A}&wizardSlug=${WIZ}`);
+    const draftsAAgain = JSON.parse(await getAAgain.text());
+    const scopeHonoured = draftsB.fields[KEY] === seedB.value && draftsAAgain.fields[KEY] === seed2a.value;
+
+    const pass = post1a.status === 200 && get1a.status === 200 && post2a.status === 200 && get2a.status === 200
+      && postB.status === 200 && getB.status === 200 && getAAgain.status === 200
+      && persistedA1 && persistedA2 && overwrittenA && scopeHonoured;
+
+    results.push({
+      anchorAcId: 'application-forms-wizard-AC-24105-1',
+      anchorReqId: 'application-forms-wizard-REQ-005',
+      verdict: pass ? 'pass' : 'fail',
+      detail: `On ?draft-store=server, entering an answer on step 1 - drafts persisted with operator+wizard scope; OP_A overwrite=${overwrittenA}, OP_B independent value=${draftsB.fields[KEY]}, scope honoured=${scopeHonoured}`,
+      evidence: evidenceFromResponse({
+        route: `/drafts?operatorId=${OP_A}&wizardSlug=${WIZ}`,
+        response: get2a,
+        bodyText: get2aBody,
+        extraFields: {
+          input: { operatorAWrites: [seed1a.value, seed2a.value], operatorBWrite: seedB.value },
+          derived: {
+            valueAfterFirstA: drafts1a.fields[KEY],
+            valueAfterSecondA: drafts2a.fields[KEY],
+            valueOpB: draftsB.fields[KEY],
+            valueOpAAgain: draftsAAgain.fields[KEY],
+            updatedAtA: drafts2a.updatedAt,
+            scopeHonoured,
+            overwrittenA,
+          },
+        },
+      }),
+    });
+
+    // Row 2: request without operator+wizard is refused (AC-24105-1
+    // scope-required derivation).
+    const badRes = await fetch(`${fixture.baseUrl}/drafts`, {
+      method: 'POST', headers: { 'content-type': 'application/json' },
+      body: JSON.stringify({ step: 'contact-details', field: 'fullName', value: 'no-scope' }),
+    });
+    const badBody = await badRes.text();
+    const badRefused = badRes.status === 400;
+    results.push({
+      anchorAcId: 'application-forms-wizard-AC-24105-1',
+      anchorReqId: 'application-forms-wizard-REQ-005',
+      verdict: badRefused ? 'pass' : 'fail',
+      detail: `On ?draft-store=server, entering an answer on step 1 - draft body without operatorId+wizardSlug refused with ${badRes.status}`,
+      evidence: evidenceFromResponse({
+        route: '/drafts',
+        response: badRes,
+        bodyText: badBody,
+        extraFields: {
+          input: { body: 'missing operatorId and wizardSlug' },
+          derived: { httpStatus: badRes.status, refused: badRefused },
+        },
+      }),
+    });
+
+    return { results };
+  } finally {
+    await fixture.close();
+  }
+}