rcf-lite 0.21.0 → 0.22.0

package/blueprints/application-file-upload/contributions/requirements/application-file-upload-req-002.json

@@ -0,0 +1,18 @@
+{
+  "reqId": "application-file-upload-REQ-002",
+  "prdId": "PRD-001",
+  "title": "Progress contract: per-file percent, aggregate percent, and a polite live-region tick",
+  "description": "Every file in the upload set carries a per-file percent that advances monotonically from 0 to 100. The surface also carries an aggregate percent that reflects the mean weighted by byte size. A polite live-region wrapper (aria-live polite) receives a text tick at least every 10 percent of aggregate progress with the string format \"<uploaded> of <total> files, <PP> percent\". The polite wrapper is preseeded at render time so a screen reader adopts it before the first tick fires.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "rationale": "Per visual round 4 spec section 5.2, REQ 2.",
+  "tags": [
+    "blueprint:application-file-upload",
+    "category:02-progress-contract"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/requirements/application-file-upload-req-003.json

@@ -0,0 +1,18 @@
+{
+  "reqId": "application-file-upload-REQ-003",
+  "prdId": "PRD-001",
+  "title": "Refusal contract: MIME-type, size-limit and virus-scan refusals with an aria-describedby error binding and focus-to-retry",
+  "description": "The upload surface refuses a file that fails the MIME-type gate, exceeds the per-file size cap, or matches the virus-scan hit. Every refusal renders a per-file error message inside a region bound to the file row via aria-describedby, moves keyboard focus to the row's retry control, and refuses to send the file to the server. The refusal reason is one of the closed strings mime-refused, size-refused, virus-refused so a project's log pipeline can classify without prose parsing.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "rationale": "Per visual round 4 spec section 5.2, REQ 3.",
+  "tags": [
+    "blueprint:application-file-upload",
+    "category:03-refusal-contract"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/requirements/application-file-upload-req-004.json

@@ -0,0 +1,18 @@
+{
+  "reqId": "application-file-upload-REQ-004",
+  "prdId": "PRD-001",
+  "title": "Transport contract: chunked-and-resumable, multipart POST default, tus.io elicited alternative",
+  "description": "The upload transport is chunked-and-resumable: an interrupted upload resumes from the last acknowledged offset on retry, and the client retries on transient failures without re-sending acknowledged bytes. The recommended default is a multipart POST with the file split into fixed-size chunks the server assembles server-side. The tus.io resumable upload protocol 1.0.0 is the elicited alternative for projects with a tus server or the third-party SDK; when applied it exposes an Upload-Offset header per PATCH request and supports server-side pause and resume. A per-vendor SDK (S3 multipart, Cloudflare R2 client-direct) is the second elicited alternative when the project has committed to a vendor library.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "rationale": "Per visual round 4 spec section 5.2, REQ 4.",
+  "tags": [
+    "blueprint:application-file-upload",
+    "category:04-transport-contract"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/requirements/application-file-upload-req-005.json

@@ -0,0 +1,18 @@
+{
+  "reqId": "application-file-upload-REQ-005",
+  "prdId": "PRD-001",
+  "title": "Completion contract: assertive-slot success announcement per WCAG 4.1.3 plus per-file remove and retry",
+  "description": "On successful completion of the upload set, the surface renders an assertive-slot announcement in a wrapper carrying role=status or aria-live=assertive with the string \"<N> files uploaded successfully\", per WCAG 4.1.3 Status Messages. Every completed file row carries a keyboard-reachable remove control (returns the row to the pre-upload state and issues a DELETE against the transport where the transport supports removal) and a retry control (visible only after a refusal or a transport error). The completion announcement fires exactly once per set; a retried refusal that then succeeds increments the completed count but does not re-announce.",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "rationale": "Per visual round 4 spec section 5.2, REQ 5.",
+  "tags": [
+    "blueprint:application-file-upload",
+    "category:05-completion-contract"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/tacs/tac-2401-application-file-upload-input.json

@@ -0,0 +1,46 @@
+{
+  "tacId": "TAC-2401-application-file-upload-input",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Upload input surface",
+  "purpose": "Owns the input-side surface of the file-upload contract: the labelled file input, the drop-zone region, the keyboard-focusable picker-opener, the accessible-name binding, the file-collector aggregating the three input paths into one selection set, and the refusal-render seam. Every AC on REQ-001 and REQ-003 that reads the surface anchors on this TAC.",
+  "responsibilities": [
+    "Render a labelled <input type=\"file\"> with a keyboard-reachable label and an accessible name (AC-23101-1).",
+    "Render a [data-drop-zone] region that accepts dropped files but is never the only input path (WCAG 2.5.7).",
+    "Render a [data-open-picker] button that opens the same picker on Enter or Space (AC-23101-1).",
+    "Aggregate the three input paths into one file-selection set the transport TAC drains (AC-23101-1).",
+    "Render a per-file error region with an aria-describedby binding and a [data-recovery=\"retry\"] control on refusal, and hand refused files to the transport TAC's refusal-render seam so no bytes leave the browser (AC-23103-1)."
+  ],
+  "internalStructure": "One input-surface module the shell mounts on route entry. On file addition the module normalises the three input paths (input change, drop event, picker-opener button) into a File[] selection set, tags each entry with a stable [data-file-row] id, runs the accepted-set gates (MIME per ADR-2402, size per ADR-2402) and the virus-scan hook per ADR-2403 before handing the set to the transport TAC. Refusal renders inside the file row with a [data-error-message] element whose id is referenced by the row's aria-describedby attribute; the closed refusal-reason enum {mime-refused, size-refused, virus-refused} rides [data-refusal-reason].",
+  "interfaces": [
+    {
+      "name": "collectFiles",
+      "kind": "factory",
+      "description": "collectFiles({ inputEvent | dropEvent | pickerClick }) -> FileSelection. Every input path routes through this factory."
+    },
+    {
+      "name": "renderRefusal",
+      "kind": "factory",
+      "description": "renderRefusal({ fileRow, reason }) -> void. Binds the error region to the row via aria-describedby, sets [data-refusal-reason], focuses the [data-recovery=\"retry\"] control."
+    },
+    {
+      "name": "affordancesEnum",
+      "kind": "shape",
+      "description": "The three input affordances (input, drop-zone, keyboard-opener) are the closed enum {file-input, drop-zone, keyboard-opener}. Removing one is a v2.0.0 major bump."
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "Transport contract",
+      "kind": "tac",
+      "tacId": "TAC-2402-application-file-upload-transport",
+      "description": "The input surface hands accepted files to the transport TAC and honours its refusal-render seam on virus-scan hits."
+    }
+  ],
+  "tradeoffs": "One input-surface module keeps the WCAG 2.5.7 discipline lint-checkable but ties every framework to the collectFiles factory. Projects using a vendor upload widget (Filepond, Uppy) satisfy the surface by adapting the vendor's mount seam to the TAC's factories rather than rewriting the collector. Known mechanism-reach gap: the pack cannot exhaustively probe every drop-target inside a nested drop-zone; the primary drop-zone attribute is asserted.",
+  "notes": "See README Known mechanism-reach gaps for the full list.",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/tacs/tac-2402-application-file-upload-transport.json

@@ -0,0 +1,47 @@
+{
+  "tacId": "TAC-2402-application-file-upload-transport",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Upload transport contract",
+  "purpose": "Owns the wire-level side of the file-upload contract: chunking, resumption, the multipart POST default, the tus.io elicited alternative, the refusal-render seam, and the completion callback. Every AC on REQ-004 that reads the request log anchors on this TAC.",
+  "responsibilities": [
+    "Split each accepted file into fixed-size chunks and upload chunks in bounded parallelism (default 3) (AC-23104-1).",
+    "On the multipart branch, POST the chunk set to the applied endpoint and assemble server-side; expose [data-transport=\"multipart\"] and [data-chunks-uploaded] on the file row (AC-23104-1).",
+    "On the tus branch, PATCH chunks to the tus creation URL with an Upload-Offset header per request; expose [data-transport=\"tus\"] (AC-23104-1).",
+    "On interruption, pause the upload and resume from the last acknowledged offset on reconnect, without re-sending acknowledged bytes (AC-23106-1).",
+    "Refuse to enqueue a refused file (mime, size, virus-scan) and hand control back to TAC-2401's refusal-render seam (AC-23103-1).",
+    "Call the progress-announcer TAC with per-chunk acknowledgements so the per-file and aggregate percent advance (AC-23102-1)."
+  ],
+  "internalStructure": "One transport module the input TAC drains. The module reads the applied ADR-2401 branch (multipart, tus, per-vendor SDK) and instantiates one of three adapter shapes. Each adapter drains the file-selection set through a bounded worker pool (concurrency default 3, elicited cap), tracks per-file [data-chunks-uploaded], and posts an acknowledgement event on every server acknowledgement the progress-announcer TAC reads. Interruption is detected via fetch reject (multipart) or the tus client's onError seam (tus); resumption re-fetches the Upload-Offset (tus) or resumes from the last completed chunk index (multipart). The refusal-render seam is a thin wrapper the input TAC calls, not a separate class, so the input surface stays authoritative.",
+  "interfaces": [
+    {
+      "name": "uploadFile",
+      "kind": "factory",
+      "description": "uploadFile({ file, endpoint, transport }) -> UploadSession. Returns a session the caller reads for per-chunk progress and completion."
+    },
+    {
+      "name": "resumeSession",
+      "kind": "factory",
+      "description": "resumeSession(session) -> UploadSession. Resumes from the last acknowledged offset."
+    },
+    {
+      "name": "transportsEnum",
+      "kind": "shape",
+      "description": "The transport branches are the closed enum {multipart, tus, vendor-sdk}. multipart is the recommended default per ADR-2401."
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "Progress announcer",
+      "kind": "tac",
+      "tacId": "TAC-2403-application-file-upload-progress-announcer",
+      "description": "The transport calls the announcer's tick on every acknowledged chunk."
+    }
+  ],
+  "tradeoffs": "Three transport branches keep the shelf usable for teams already committed to a vendor SDK, but the per-branch adapter code is real work; a project that never elicits tus or a vendor SDK ships with the multipart adapter only. Bounded parallelism (default 3) is a heuristic; a slow-link project can lower it via the applied endpoint config. Known mechanism-reach gap: the pack cannot probe a network-interruption resume path on the multipart branch without a request-blocking driver; the fixture simulates the pause via a ?interrupt=1 branch and the pack reads the resulting DOM state.",
+  "notes": "See README Known mechanism-reach gaps for the full list.",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

package/blueprints/application-file-upload/contributions/tacs/tac-2403-application-file-upload-progress-announcer.json

@@ -0,0 +1,46 @@
+{
+  "tacId": "TAC-2403-application-file-upload-progress-announcer",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Upload progress announcer",
+  "purpose": "Owns the announcement side of the file-upload contract: the polite live-region wrapper the transport ticks, the aggregate-percent calculator, the assertive-slot completion announcement, and the background-tab tick continuity. Every AC on REQ-002 and REQ-005 that reads the aria-live regions anchors on this TAC.",
+  "responsibilities": [
+    "Mount the polite live-region wrapper at render time so a screen reader adopts it before the first tick (AC-23102-1).",
+    "Emit a polite text tick every 10 percent of aggregate progress in the closed format \"<uploaded> of <total> files, <PP> percent\" (AC-23102-1).",
+    "Compute the aggregate percent as the mean weighted by byte size across the active file set (AC-23102-1).",
+    "On completion of the set, mount an assertive-slot announcement (aria-live=\"assertive\" or role=\"status\") with the closed text \"<N> files uploaded successfully\", exactly once per set (AC-23105-1).",
+    "Continue ticking under document visibilitychange to hidden so a backgrounded tab does not stall the announcement (AC-23107-1)."
+  ],
+  "internalStructure": "One announcer module the transport hooks. The module preseeds the polite wrapper (aria-live polite) on mount, reads per-chunk acknowledgements from the transport, updates a per-file percent + aggregate percent record, and pushes a text tick every time the floor(aggregate/10) integer changes. Completion detection is a single flag; the assertive slot is mounted on mount as an empty wrapper and its textContent is set exactly once per set. Background-tab continuity is achieved by using setInterval on the ack polling loop rather than requestAnimationFrame; the interval keeps firing when the tab is hidden. A project that wants to pause on hidden explicitly elicits the alternative.",
+  "interfaces": [
+    {
+      "name": "tick",
+      "kind": "factory",
+      "description": "tick({ fileRowId, bytesAcknowledged, totalBytes }) -> void. Transport calls this on every acknowledgement."
+    },
+    {
+      "name": "complete",
+      "kind": "factory",
+      "description": "complete({ successCount }) -> void. Transport calls this exactly once per set."
+    },
+    {
+      "name": "announcementFormatsEnum",
+      "kind": "shape",
+      "description": "The polite format is fixed: /^\\d+ of \\d+ files, \\d{1,3} percent$/; the assertive format is fixed: /^\\d+ files uploaded successfully$/. Localisation is a v1.1.0 minor bump extending the enum with a lookup table."
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "Transport contract",
+      "kind": "tac",
+      "tacId": "TAC-2402-application-file-upload-transport",
+      "description": "The announcer reads per-chunk acknowledgements from the transport."
+    }
+  ],
+  "tradeoffs": "One announcer module keeps the aria-live discipline testable but pins the wire format in English at v1.0.0; a localised project elicits the format table in a v1.1.0 minor. Known mechanism-reach gap: the pack asserts the polite wrapper's textContent format but does not additionally probe screen-reader adoption (that requires a real assistive tech in the loop).",
+  "notes": "See README Known mechanism-reach gaps for the full list.",
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,28 @@
+{
+  "usId": "application-file-upload-US-23101",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The upload surface renders a labelled file input, a drop-zone region and a keyboard-focusable alternative that opens the picker on Enter",
+  "asA": "operator selecting files to upload, whether by pointer, drag-drop or keyboard alone",
+  "iWant": "a labelled native file input, a drop-zone region and a keyboard-focusable button that opens the picker so I can add files from whichever input mode I use",
+  "soThat": "I never have to drag to add a file and my screen reader announces the picker rather than a silent drop-zone",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-23101-1",
+      "testable": true,
+      "scope": "runtime",
+      "description": "The upload region carries [data-surface=\"file-upload\"] and inside it: a labelled <input type=\"file\"> with a keyboard-reachable label (an id-referenced <label> or an aria-label), a [data-drop-zone] region, and a keyboard-focusable [data-open-picker] button that opens the same picker on Enter or Space. The pack drives the real browser to /upload, asserts the three affordances are present, focuses the [data-open-picker] control and presses Enter, then reads that the file input received focus."
+    }
+  ],
+  "tacIds": [
+    "TAC-2401-application-file-upload-input"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:input-plus-drop-plus-keyboard"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,28 @@
+{
+  "usId": "application-file-upload-US-23102",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-002",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The progress announcer emits per-file and aggregate progress through a polite live-region wrapper",
+  "asA": "operator watching an upload progress on a screen reader or a low-vision magnifier",
+  "iWant": "a polite live-region tick every 10 percent of aggregate progress that names how many files have completed out of how many",
+  "soThat": "I know the upload is still working without watching the screen and I can tell when it stalls",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-23102-1",
+      "testable": true,
+      "scope": "runtime",
+      "description": "The upload region ships a [data-live-region=\"polite\"] wrapper with aria-live=\"polite\" preseeded at render time. During an upload the wrapper's textContent matches /^\\d+ of \\d+ files, \\d{1,3} percent$/ and the numeric aggregate percent advances monotonically. Per-file rows carry [data-file-row] with a [data-file-progress] element whose text or aria-valuenow reflects the per-file percent. The pack drives /upload?transport=multipart, starts the upload, and reads the wrapper text plus one per-file progress value before completion."
+    }
+  ],
+  "tacIds": [
+    "TAC-2403-application-file-upload-progress-announcer"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:polite-progress"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,29 @@
+{
+  "usId": "application-file-upload-US-23103",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-003",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "A refused file renders an aria-describedby-bound error and moves focus to its retry control, without sending the bytes",
+  "asA": "operator whose selected file is refused by the MIME gate, the size gate or the virus scanner",
+  "iWant": "an inline error that names the refusal reason, is bound to my file row via aria-describedby, and moves my focus to the retry control without sending the file to the server",
+  "soThat": "I learn why the file was refused, do not waste my upload budget on a refused file, and can retry with a corrected file from my keyboard",
+  "acceptanceCriteria": [
+    {
+      "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."
+    }
+  ],
+  "tacIds": [
+    "TAC-2401-application-file-upload-input",
+    "TAC-2402-application-file-upload-transport"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:refusal"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,28 @@
+{
+  "usId": "application-file-upload-US-23104",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The transport uploads files in chunks and, on the tus.io branch, exposes an Upload-Offset header per PATCH",
+  "asA": "operator uploading a large file over a spotty connection",
+  "iWant": "the transport to split my file into chunks and to resume from the last acknowledged offset on retry",
+  "soThat": "an interrupted upload does not re-send bytes I already delivered",
+  "acceptanceCriteria": [
+    {
+      "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."
+    }
+  ],
+  "tacIds": [
+    "TAC-2402-application-file-upload-transport"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:chunked-resumable"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,29 @@
+{
+  "usId": "application-file-upload-US-23105",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-005",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "On successful completion the upload surface renders an assertive-slot announcement and per-file remove and retry controls",
+  "asA": "operator whose upload set has just finished",
+  "iWant": "an assertive-slot announcement saying how many files uploaded successfully, plus a keyboard-reachable remove control per completed file",
+  "soThat": "my screen reader tells me the set is done and I can remove a file I no longer want without a page reload",
+  "acceptanceCriteria": [
+    {
+      "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."
+    }
+  ],
+  "tacIds": [
+    "TAC-2401-application-file-upload-input",
+    "TAC-2403-application-file-upload-progress-announcer"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:completion"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,28 @@
+{
+  "usId": "application-file-upload-US-23106",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "A network interruption mid-upload resumes from the last acknowledged offset when the connection returns",
+  "asA": "operator uploading through a spotty connection or a captive portal that drops mid-request",
+  "iWant": "the transport to pause on interruption, wait for the connection to return, and resume from the last acknowledged offset without re-sending",
+  "soThat": "a dropped connection does not force me to restart a large upload",
+  "acceptanceCriteria": [
+    {
+      "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)."
+    }
+  ],
+  "tacIds": [
+    "TAC-2402-application-file-upload-transport"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:resumption"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,28 @@
+{
+  "usId": "application-file-upload-US-23107",
+  "prdId": "PRD-001",
+  "reqId": "application-file-upload-REQ-002",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Progress continues to advance and the polite live-region continues to tick when the browser tab is backgrounded",
+  "asA": "operator who tabs away from the upload while it is running",
+  "iWant": "the upload to continue and the polite live-region to keep receiving ticks so a screen reader can pick up the announcement when I return",
+  "soThat": "backgrounding the tab does not stall the upload or my accessibility affordance",
+  "acceptanceCriteria": [
+    {
+      "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."
+    }
+  ],
+  "tacIds": [
+    "TAC-2403-application-file-upload-progress-announcer"
+  ],
+  "tags": [
+    "blueprint:application-file-upload",
+    "affordance:background-tab-progress"
+  ],
+  "createdAt": "2026-09-06T16:55:00Z",
+  "updatedAt": "2026-09-06T16:55:00Z"
+}

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

@@ -0,0 +1,58 @@
+# application-file-upload: coordination vocabulary
+
+## Global topics
+
+The blueprint claims no new global topics at v1.0.0. Every ADR (transport branch, accepted set, virus-scan integration) is non-global.
+
+## Deliberately unclaimed topics
+
+- `uploadEnvelope` (the shape of an upload success or completion response body). Reserved for the applied API blueprint (`application-api-rest` claims it today); this blueprint reads the wire-level chunk acknowledgements, not the envelope body shape, so no claim collides.
+- `commonAcceptedSets` (a shelf-wide registry of accepted MIME sets a consumer can reach for). Reserved for a future v1.1.0 minor bump if three or more consumer blueprints start elicitizing the same lists. Held here as an unclaimed topic so a composing author sees the reservation.
+- `objectStorageTransport` (a shared engine for the chunked-and-resumable transport that both an object-storage blueprint and this UI blueprint would reach for). Reserved for a future dedicated `application-file-transport` blueprint; held here so a composing author sees the reservation before minting a new topic.
+- `announcementFormatsCatalogue` (the localised polite and assertive text formats). Reserved for a v1.1.0 minor bump extending the announcer TAC's `announcementFormatsEnum` with a lookup table.
+
+## Shelf id band and suffix block
+
+| Blueprint | US band | ADR/TAC suffix block | Status | Global topics |
+|---|---|---|---|---|
+| application-datatable | 17101-17899 | 18xx | shipped v1.0.0 | none |
+| application-charts | 18101-18899 | 19xx | shipped v1.0.0 | none |
+| application-dashboard | 19101-19899 | 20xx | shipped v1.0.0 | none |
+| application-notifications-in-app | 20101-20899 | 21xx | shipped v1.0.0 | none |
+| application-admin-console | 21101-21899 | 22xx | shipped v1.0.0 | none |
+| application-empty-error-states | 22101-22899 | 23xx | shipped v1.0.0 | none |
+| application-file-upload | 23101-23899 | 24xx | shipped v1.0.0 | none |
+| application-forms-wizard | 24101-24899 | 25xx | shipped v1.0.0 | none |
+| 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` |
+
+The shelf-wide band registry lives in `packages/rcf-lite/docs/blueprint-authoring.md` section 5.
+
+## Composition with application-spa
+
+`application-spa` REQ-006 ships upload and progress and error components as part of its component library. Applying this blueprint alongside `application-spa` composes cleanly: SPA holds the visual tokens for the upload region; this blueprint holds the input affordances, the transport contract, the refusal contract and the runtime enforcement pack. No `scope: "global"` ADR conflict.
+
+## Composition with application-empty-error-states
+
+A refused upload is a refusal contract state, not an empty or error state; the two blueprints do not overlap on state slugs. A transport-level failure (server 5xx during a chunk PATCH) surfaces through `application-empty-error-states`'s server-error state after the transport's retry budget is exhausted. No global-topic overlap.
+
+## Composition with application-error-handling
+
+Refusals and transport-layer failures construct an internal error record through the applied error-handling factory (`suggestedCompanions: errorHandling`). This blueprint reads the factory's shape; `application-error-handling` owns the shape and its correlation-identifier discipline.
+
+## The four fixture states and the two transport slugs
+
+The four state slugs `idle`, `uploading`, `refused`, `complete` and the two transport slugs `multipart`, `tus` appear identically across the blueprint README, the fixture README, the operator guide, the probe pack `checks[]` descriptions and this file. Extending either enum is a v1.1.0 minor bump; removing or renaming is a v2.0.0 major.
+
+## Probe pack
+
+`probe-packs/application-file-upload.pack.mjs` ships four surface-observable checks anchored to blueprint AC ids, one per contract:
+
+- `AC-23101-1` input surface (file input, drop-zone, keyboard-focusable opener)
+- `AC-23102-1` progress announcer (polite tick format and monotonic advance)
+- `AC-23103-1` refusal contract (aria-describedby error binding, refused bytes never on the wire)
+- `AC-23104-1` chunked transport (multipart chunks or tus Upload-Offset)
+
+The pack applies to any FBS binding `TAC-2401-application-file-upload-input` or whose navModel routes name an operator-configured upload path (matching `/upload`). See `packages/rcf-lite/docs/blueprint-authoring.md` section 8c for the pack authoring rules.

package/blueprints/application-file-upload/guide/application-file-upload.md

@@ -0,0 +1,48 @@
+# application-file-upload: operator guide
+
+## When to reach for it
+
+Your project accepts file uploads from operators, whether one file at a time or a set, whether small text and image assets or large media. You want one contract for the input surface (labelled input plus drop-zone plus keyboard opener per WCAG 2.5.7), one recommended transport that ships resumable-chunked out of the box, one refusal contract that binds errors via `aria-describedby` and never lets refused bytes reach the server, one polite live-region tick that keeps a screen-reader user informed of progress, and a runtime pack that refuses ship on a dropped input, a dropped live-region, a refused file that reached the wire, or a collapsed transport.
+
+## The two transports
+
+The two shipped transport slugs are `multipart` and `tus`. `multipart` is the recommended default (ADR-2401 `recommendedDefault: true`) because every server toolkit accepts it and the client-side code is a Blob split into fixed-size chunks. `tus` is the elicited alternative for projects with a tus server or the third-party tus client library; on the tus branch each chunk is a PATCH request with an `Upload-Offset` header the pack asserts. A third alternative, `vendor-sdk` (S3 multipart, Cloudflare R2 client-direct, Cloudinary widget), is documented in ADR-2401 for projects committed to a vendor; the shipped fixture does not exercise it, and a vendor-sdk project runs the pack against a fixture that mocks the vendor's completion callback.
+
+## The four file-row states
+
+The four shipped state slugs are `idle`, `uploading`, `refused`, `complete`. Every file row on the fixture cycles through this closed set; the same slugs ride `[data-file-state]` on the file row in your applied project. Extending the state set is a v1.1.0 minor bump; removing or renaming a state is a v2.0.0 major.
+
+## When NOT to reach for it
+
+Your product is a marketing site or a static content surface that never accepts an upload. The four contracts model a live upload surface; a static site has no transport, no progress tick, no refusal contract, and forcing the model on a static site adds mechanism without payoff.
+
+Your product has already committed to an opinionated single-vendor upload widget (Uppy with a specific backend, Filepond with a specific plugin set) whose contract is materially different from the input plus refusal plus progress catalogue. Adopt this blueprint only when the vendor widget composes with the input TAC's `collectFiles` factory rather than replacing it.
+
+## What stays your call
+
+- The visual design of the upload region, the file rows and the drop-zone. The blueprint contributes WHAT surfaces under WHAT condition; the palette, spacing and typography are your project's design system's call.
+- The accepted MIME set (ADR-2402 elicited enum). No default; every project elicits its own list of IANA media types.
+- The per-file size cap in bytes (ADR-2402 elicited). No default; every project elicits its own cap.
+- The transport branch (ADR-2401 elicited). Recommended `multipart`; elicit `tus` when a tus server is available or the third-party SDK is on the path; elicit `vendor-sdk` when a vendor SDK is on the path.
+- The virus-scan verifier (ADR-2403 capability-plus-elicit). Every project elicits the verifier or the explicit noop; there is no shelf default and the guide names the risk in plain language for the noop path.
+- The concurrency cap for the transport worker pool. Recommended default 3; a slow-link project elicits a lower cap.
+- The announcer polling interval in milliseconds. Recommended default 250; a project sensitive to CPU cost on a hot page elicits a higher interval.
+- The upload endpoint URL. The blueprint declares the shape (`POST /api/upload/chunk` for multipart, `POST /api/upload/tus` for the tus creation URL); the endpoint's server-side handling is your call.
+
+## What a good outcome looks like
+
+The pack fires on every FBS whose surface renders an upload route, and every check returns `pass` on the honest render (both transport branches) and `fail` on the corresponding break switch. Your CI runs the fixture round-trip on every PR that touches an upload surface. Your operator uploads a file with the keyboard alone and hears the polite tick as it advances. Your production upload surface never lets a refused file's bytes leave the browser. Your production stack ships with an explicit virus-scan verifier or with the noop plus the guide's risk paragraph on file.
+
+## Mechanism-reach gaps
+
+The blueprint's README lists the runtime-observable ACs the pack does NOT bind directly (drop-event round-trip, screen-reader adoption, error-message content, network-interruption resume on multipart, assertive-slot exclusive fire, network interruption resumption, background-tab tick continuity). Every gap is a candidate for a v1.1.0 minor bump extending the pack. Combine with `application-error-handling` to route refusal internal error records through the shipped factory and with `application-spa` to inherit the visual tokens.
+
+## Promotion signals
+
+- Three or more consumer blueprints (forms-wizard, an eventual CSV-import, account-settings avatar upload) start elicitizing the same accepted-set entries. Candidate: a `commonAcceptedSets` global topic in a v1.1.0 minor.
+- The transport TAC needs a shared engine across an object-storage blueprint and this UI blueprint. Candidate: a dedicated `application-file-transport` blueprint absorbing the chunked-and-resumable path.
+- Localisation of the polite and assertive text formats. Candidate: a v1.1.0 minor bump extending the announcer TAC's `announcementFormatsEnum` with a lookup table.
+
+## Costs to be honest about
+
+Realising all three input affordances honestly in a client is a chunk of code even after adopting the TACs; the WCAG 2.5.7 keyboard alternative is often the piece a first cut skips. The pack is Playwright-first, so a project without a running dev server at gate time cannot fire it. The tus branch assumes a tus server or the third-party client; a project that elicits tus without one hits an apply-time refusal on the elicit and unblocks by wiring one in or falling back to multipart.