rcf-lite 0.25.0 → 0.27.0

package/blueprints/application-notifications-in-app/contributions/requirements/application-notifications-in-app-req-002.json

@@ -3,11 +3,18 @@
   "prdId": "PRD-001",
   "title": "A transient toast maps its priority to a live-region role, announces exactly once, and dismisses on operator activation or timeout",
   "description": "A notification surfaced as a transient toast writes into one of the two preseeded live regions based on its priority per ADR-2101: an informational priority renders into the polite wrapper and carries `role=\"status\"`, an error priority renders into the assertive wrapper and carries `role=\"alert\"`. The toast body appears in exactly one wrapper text update (the one whose role reflects the priority) and never in both. Every toast is dismissible in two ways: an operator activation on the toast's dismiss control, and a timeout at or above the ADR-2102 floor (six seconds baseline per WCAG 2.2.1 Timing Adjustable, elicited overrides above the floor). The toast records `data-shown-at` and `data-dismissed-at` timestamps on its DOM element so a probe can measure the actual timeout against the floor without sleeping in the pack.",
+  "deliveredBy": {
+    "tacId": "TAC-2102-application-notifications-in-app-centre",
+    "field": "interfaces.renderCentre"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "The WCAG 4.1.3 status-message clause and the ARIA APG alert pattern name the priority-to-role mapping as the accessibility discipline that lets a screen reader distinguish a passive confirmation (polite queue) from an assertive interruption (assertive queue). The WCAG 2.2.1 Timing Adjustable clause names six seconds as the floor for a message a reader can dwell on; a timeout below the floor is a comprehension defect. Recording the shown and dismissed timestamps on the DOM element makes both rules observable at runtime without a race-prone sleep in the pack.",
-  "tags": ["blueprint:application-notifications-in-app", "category:02-toast-contract"],
+  "tags": [
+    "blueprint:application-notifications-in-app",
+    "category:02-toast-contract"
+  ],
   "version": "1.0.0",
   "status": "approved",
   "createdAt": "2026-09-04T23:59:00Z",

package/blueprints/application-notifications-in-app/contributions/requirements/application-notifications-in-app-req-003.json

@@ -2,12 +2,19 @@
   "reqId": "application-notifications-in-app-REQ-003",
   "prdId": "PRD-001",
   "title": "The notification centre inbox lists the last N days of notifications and each acknowledge control round-trips to the server",
-  "description": "The applying project renders a notification-centre route (default `/notifications-centre`, operator-elicited) whose inbox surface lists the notifications delivered in the last N days per the ADR-2103 retention window (default thirty days, elicited). Each notification carries a stable `data-notification-id` attribute the pack enumerates by (never by a role attribute alone, per the T-3 gate discipline), and each carries a keyboard-reachable acknowledge control (`[data-action=\"acknowledge\"]`) plus a mark-read control (`[data-action=\"mark-read\"]`); the surface offers one mark-all-read control (`[data-action=\"mark-all-read\"]`) reachable in reading order. Activating the acknowledge control POSTs an acknowledge request to the applying project's server, the server responds, and the DOM updates in response: the notification's `data-acknowledged` reads `true` after the round-trip. Every item is Tab-reachable from the start of the surface without a mouse.",
+  "description": "The applying project renders a notification-centre route (default `/notifications-centre`, operator-elicited) whose inbox surface lists the notifications delivered in the last N days per the ADR-2103 retention window (default thirty days, elicited). Each notification carries a stable `data-notification-id` attribute the pack enumerates by (never by a role attribute alone, per the gate discipline), and each carries a keyboard-reachable acknowledge control (`[data-action=\"acknowledge\"]`) plus a mark-read control (`[data-action=\"mark-read\"]`); the surface offers one mark-all-read control (`[data-action=\"mark-all-read\"]`) reachable in reading order. Activating the acknowledge control POSTs an acknowledge request to the applying project's server, the server responds, and the DOM updates in response: the notification's `data-acknowledged` reads `true` after the round-trip. Every item is Tab-reachable from the start of the surface without a mouse.",
+  "deliveredBy": {
+    "tacId": "TAC-2102-application-notifications-in-app-centre",
+    "field": "interfaces.acknowledgeRoundTrip"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
-  "rationale": "A transient toast is not a system of record; the notification centre is. Making the centre the operator's inbox with a retention window and per-item acknowledge round-trip is what turns a fleeting on-screen message into a durable one the operator can return to and confirm. Enumerating items by `data-notification-id` rather than by `role=\"listitem\"` on the container follows the T-3 gate discipline: a role attribute the primary element carries alone does not enumerate multiple children; a per-element data attribute does.",
-  "tags": ["blueprint:application-notifications-in-app", "category:03-centre-inbox"],
+  "rationale": "A transient toast is not a system of record; the notification centre is. Making the centre the operator's inbox with a retention window and per-item acknowledge round-trip is what turns a fleeting on-screen message into a durable one the operator can return to and confirm. Enumerating items by `data-notification-id` rather than by `role=\"listitem\"` on the container follows the gate discipline: a role attribute the primary element carries alone does not enumerate multiple children; a per-element data attribute does.",
+  "tags": [
+    "blueprint:application-notifications-in-app",
+    "category:03-centre-inbox"
+  ],
   "version": "1.0.0",
   "status": "approved",
   "createdAt": "2026-09-04T23:59:00Z",

package/blueprints/application-notifications-in-app/contributions/requirements/application-notifications-in-app-req-004.json

@@ -3,13 +3,20 @@
   "prdId": "PRD-001",
   "title": "The preferences UI exposes per-user category silence and delegates digest opt-in to the sibling channels",
   "description": "The applying project renders a preferences surface (default `/notifications-preferences`, operator-elicited) that carries one section per operator-elicited notification category with a labelled silence toggle (`[data-preference-category=\"<category>\"]` on the toggle's `<input>` or `<button>` control), and one section per sibling channel (`-email`, `-push`, `-webhook`) with a digest opt-in control recording the operator's intent on `data-digest-<channel>`. This blueprint ships no transport: the digest opt-in records the intent on the surface, and the applying project's sibling blueprint (once shipped) reads the intent from the preferences store and drives its own delivery. A preferences surface that promises a digest without a corresponding sibling blueprint applied is a defect the applying project surfaces via a `[data-preference-status]` label reading `\"sibling not applied\"`.",
+  "deliveredBy": {
+    "tacId": "TAC-2103-application-notifications-in-app-preferences",
+    "field": "interfaces.renderPreferences"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
-  "rationale": "Per-user category silence is the operator's primary knob on notification fatigue: a labelled toggle per category gives the reader an accountable choice without overloading the transport. Delegating digest opt-in to the sibling channel keeps this blueprint at the in-app surface it names (per Baz decision 2026-09-04: 'we might support more types of notifications - be clear in the name what these ones are'); a digest is a transport concern the sibling blueprint owns.",
-  "tags": ["blueprint:application-notifications-in-app", "category:04-preferences"],
-  "version": "1.0.0",
+  "rationale": "Per-user category silence is the operator's primary knob on notification fatigue: a labelled toggle per category gives the reader an accountable choice without overloading the transport. Delegating digest opt-in to the sibling channel keeps this blueprint at the in-app surface it names (per the 2026-09-04 shelf decision to make the transport type explicit in the blueprint name); a digest is a transport concern the sibling blueprint owns.",
+  "tags": [
+    "blueprint:application-notifications-in-app",
+    "category:04-preferences"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/requirements/application-notifications-in-app-req-005.json

@@ -2,14 +2,21 @@
   "reqId": "application-notifications-in-app-REQ-005",
   "prdId": "PRD-001",
   "title": "The delivery-attempt log records one row per surfaced notification with the operator-readable fields for later inspection",
-  "description": "Every notification the shell surfaces (as a toast, in the notification centre, or both) appends one row to the delivery-attempt log. Each row carries `notificationId`, `category`, `priority`, `deliveredAt` (ISO-8601 timestamp of the surface event), and the optional acknowledgement trail: `dismissedAt` when the operator dismissed the toast, `acknowledgedAt` when the operator activated the centre's acknowledge control. The log is operator-readable via a `GET /api/delivery-log` endpoint the applying project exposes; the endpoint returns JSON in the shape `{ rows: [...] }`. The log is append-only; a row is never rewritten, only augmented (a `dismissedAt` or `acknowledgedAt` may land on a later request). Records write through the applied `logging` companion's factory so the log's persistence and retention layer is the companion's, not this blueprint's.",
+  "description": "Every notification the shell surfaces (as a toast, in the notification centre, or both) appends one row to the delivery-attempt log through `TAC-2102.interfaces.writeDeliveryRow`; every row honours the shape owned by `TAC-2102.interfaces.deliveryRowShape`. The applied `logging` companion persists the rows; the centre reads them back through `TAC-2102.responsibilities.readDeliveryLog` for the current-session read model.",
+  "deliveredBy": {
+    "tacId": "TAC-2102-application-notifications-in-app-centre",
+    "field": "interfaces.writeDeliveryRow"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "A delivery-attempt log is the operator's audit trail for what the shell has said and when, alongside a second row per acknowledgement event. Ownership of the row shape lives on this blueprint; ownership of the persistence layer lives on the applied `logging` companion (per REQ-005 factory delegation). Splitting the two lets the applying project pick a log store per its `logging` companion pin without the notifications blueprint dragging in a store of its own.",
-  "tags": ["blueprint:application-notifications-in-app", "category:05-delivery-log"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-notifications-in-app",
+    "category:05-delivery-log"
+  ],
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
-}
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-notifications-in-app/contributions/requirements/application-notifications-in-app-req-006.json

@@ -0,0 +1,21 @@
+{
+  "reqId": "application-notifications-in-app-REQ-006",
+  "prdId": "PRD-001",
+  "title": "Apply-time answer families bind the five elicits to the notifications-in-app contract",
+  "description": "When the applying project answers the five apply-time elicits, the shell honours each with a runtime clause per family: `blueprint.json.elicits[id=timeout]` sets the toast timeout floor on ADR-2102 (a value below 6 seconds refuses at apply with TOAST_TIMEOUT_TOO_SHORT); `blueprint.json.elicits[id=retention]` sets the notification-centre retention window in days per ADR-2103; `blueprint.json.elicits[id=categories]` populates the per-category preference sections on TAC-2103; `blueprint.json.elicits[id=route]` sets the preferences route the shell mounts; `blueprint.json.elicits[id=page-size]` sets the notification-centre page size.",
+  "deliveredBy": {
+    "tacId": "TAC-2102-application-notifications-in-app-centre",
+    "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-notifications-in-app"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-10T00:00:00Z",
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-notifications-in-app/contributions/tacs/tac-2102-application-notifications-in-app-centre.json

@@ -2,17 +2,18 @@
   "tacId": "TAC-2102-application-notifications-in-app-centre",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Notification centre inbox, retention window, acknowledge round-trip and delivery-attempt log",
   "purpose": "Owns the shell's persistent notification-centre inbox: the centre route the applying project mounts (default `/notifications-centre`, elicited), the retention window contract per ADR-2103 (default thirty days, elicited), the per-item acknowledge round-trip that POSTs to the applying project's server and updates the DOM on the response, and the delivery-attempt log write path per REQ-005. The centre is the durable inbox the operator returns to; the toast is the transient surface.",
   "responsibilities": [
-    "Render one notification wrapper per delivery-log row within the ADR-2103 retention window. Every wrapper carries `data-notification-id` (per-element attribute the pack enumerates by, never `role=\"listitem\"` on the container alone per the T-3 gate discipline) (AC-20103-1, AC-20103-2).",
+    "Render one notification wrapper per delivery-log row within the ADR-2103 retention window. Every wrapper carries `data-notification-id` (per-element attribute the pack enumerates by, never `role=\"listitem\"` on the container alone per the gate discipline) (AC-20103-1, AC-20103-2).",
     "Render one keyboard-reachable `[data-action=\"acknowledge\"]` control and one `[data-action=\"mark-read\"]` control per item; render exactly one `[data-action=\"mark-all-read\"]` control on the surface, reachable in Tab order after the item list (AC-20103-1).",
     "On acknowledge activation, POST `POST /api/notifications/acknowledge` with the notification id, wait for the server response, and update `data-acknowledged` on the item to `true` on a 2xx response; a failed response surfaces an error toast via the TAC-2101 factory and the item's `data-acknowledged` remains unchanged (AC-20103-1).",
     "On a page load with a backlog, render every backlog item on the surface without writing any body text into the polite or assertive live-region wrapper (AC-20106-1).",
-    "Expose the delivery-log write factory `writeDeliveryRow` the TAC-2101 toast factory and this TAC's centre factory both call; every write goes through the applied `logging` companion's record factory (AC-20105-2).",
-    "Expose the delivery-log read endpoint `GET /api/delivery-log` returning `{ rows: [...] }` where every row carries `notificationId`, `category`, `priority`, `deliveredAt`, optionally `dismissedAt`, optionally `acknowledgedAt`; rows are append-only (AC-20105-1)."
+    "Expose the delivery-log write factory `interfaces.writeDeliveryRow`, called by both the TAC-2101 toast factory and this TAC's centre factory; every write goes through the applied `logging` companion's record factory (AC-20105-2).",
+    "readDeliveryLog: expose the delivery-log read endpoint `GET /api/delivery-log` returning `{ rows: [...] }` where every row conforms to `interfaces.deliveryRowShape`; rows are append-only, per REQ-005 (AC-20105-1).",
+    "applyElicits: at apply time, dispatch each of the five answer families to its owner: `timeout` sets the toast timeout floor on `ADR-2102`; `retention` sets the notification-centre retention window on this TAC per `ADR-2103`; `categories` populates the per-category preference sections on `TAC-2103`; `route` sets the preferences route this TAC mounts; `page-size` sets the notification-centre page size. Per REQ-006."
   ],
   "internalStructure": "One centre-route module reading the delivery-log endpoint filtered to the retention window and rendering one wrapper per row through a shared item factory. One acknowledge-round-trip helper that owns the POST plus the DOM-update code path. One delivery-log write helper (`writeDeliveryRow`) that adapts the shell-side row shape to the applied `logging` companion's record factory.",
   "interfaces": [
@@ -24,12 +25,17 @@
     {
       "name": "writeDeliveryRow",
       "kind": "factory",
-      "description": "writeDeliveryRow({ notificationId, category, priority, deliveredAt, dismissedAt?, acknowledgedAt? }) -> Promise<void>. Writes one row through the applied `logging` companion's record factory. Called from TAC-2101's toast factory on a toast surface event and from this TAC's centre-item activation on an acknowledge event."
+      "description": "writeDeliveryRow(row) -> Promise<void>. Writes one row through the applied `logging` companion's record factory, where `row` conforms to `interfaces.deliveryRowShape`. Called from TAC-2101's toast factory on a toast surface event and from this TAC's centre-item activation on an acknowledge event."
     },
     {
       "name": "acknowledgeRoundTrip",
       "kind": "function",
       "description": "acknowledgeRoundTrip({ notificationId }) -> Promise<{ ok: boolean }>. POSTs `POST /api/notifications/acknowledge` and returns the parsed server response. A 2xx flips `data-acknowledged` on the item; a non-2xx surfaces an error toast through TAC-2101."
+    },
+    {
+      "name": "deliveryRowShape",
+      "kind": "shape",
+      "description": "Delivery-log row schema owned by TAC-2102: { deliveryTs (ISO-8601 timestamp of the surface event), priority (\"info\" | \"error\"), category (string), outcome (\"delivered\" | \"dismissed\" | \"acknowledged\" | \"expired\"), correlationId (string) }. Every row the toast factory and the centre factory write goes through writeDeliveryRow honouring this shape."
     }
   ],
   "dependencies": [
@@ -46,7 +52,7 @@
     }
   ],
   "tradeoffs": "The centre reading through the delivery log (rather than a separate inbox store) keeps the shell single-sourced on the applied `logging` companion but couples the surface latency to the log query; a project with a very high notification volume may want to project a materialised inbox view alongside the log. This TAC accepts the coupling because it collapses two writers of the same row into one; a project that needs the materialised view supersedes with a project-authored REQ.",
-  "notes": "Known mechanism-reach gap: the pack asserts one acknowledge round-trip on one item (AC-20103-1); the mark-read control, the mark-all-read control and the retention-window boundary (a row on day 31 must not surface) are runtime-observable ACs the shipped pack does not itself drive. The README names them individually per the T-1 gate discipline; a v1.1 minor bump could add checks for each.",
+  "notes": "Known mechanism-reach gap: the pack asserts one acknowledge round-trip on one item (AC-20103-1); the mark-read control, the mark-all-read control and the retention-window boundary (a row on day 31 must not surface) are runtime-observable ACs the shipped pack does not itself drive. The README names them individually per the gate discipline; a v1.1 minor bump could add checks for each.",
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
-}
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-notifications-in-app/contributions/tacs/tac-2103-application-notifications-in-app-preferences.json

@@ -33,8 +33,8 @@
       "description": "A preference update that fails at the server surfaces an error toast through TAC-2101."
     }
   ],
-  "tradeoffs": "Delegating digest opt-in to sibling blueprints keeps this blueprint's contract at the in-app surface (Baz decision 2026-09-04: 'be clear in the name what these ones are'). The trade-off is that on a project without any sibling channel applied the preferences surface renders disabled sibling sections; a first-time reader might expect the preferences UI to be silent about siblings that do not exist. This TAC ships the disabled section on the argument that the reserved family prefix (`application-notifications-`) is discoverable to the operator and the labelled disabled state names the residual honestly.",
-  "notes": "Known mechanism-reach gap: elicitation of the notification categories is a declarative field on the ADR-2101 elicited-parameters block; the runner has no apply-time elicitation phase today (w-2026-09-04-dave-022, built in T-5), so the applying project gathers the categories by hand at the apply pass. The README names this individually.",
+  "tradeoffs": "Delegating digest opt-in to sibling blueprints keeps this blueprint's contract at the in-app surface (per the 2026-09-04 shelf decision to make the transport type explicit in the blueprint name). The trade-off is that on a project without any sibling channel applied the preferences surface renders disabled sibling sections; a first-time reader might expect the preferences UI to be silent about siblings that do not exist. This TAC ships the disabled section on the argument that the reserved family prefix (`application-notifications-`) is discoverable to the operator and the labelled disabled state names the residual honestly.",
+  "notes": "Known mechanism-reach gap: elicitation of the notification categories is a declarative field on the ADR-2101 elicited-parameters block; the runner has no apply-time elicitation phase today (planned for a follow-up minor), so the applying project gathers the categories by hand at the apply pass. The README names this individually.",
   "createdAt": "2026-09-04T23:59:00Z",
   "updatedAt": "2026-09-04T23:59:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20101.json

@@ -16,7 +16,8 @@
       "when": "the initial DOM is read",
       "then": "both preseeded wrappers are present, carry their id attribute, and are empty",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-20101-2",
@@ -25,11 +26,34 @@
       "when": "the factory is invoked at first render and again on a route change",
       "then": "the same two wrapper elements are returned; identity is stable",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2101-application-notifications-in-app-live-region",
+        "field": "interfaces.renderLiveRegions"
+      }
+    },
+    {
+      "id": "AC-20101-3",
+      "description": "The two live-region wrappers pre-seed at document render, before any state-driven mount, so that an announcement fired during a first render lands in a live region already present. A break that mounts the wrapper on state entry fails the pack.",
+      "given": "a page load on any route",
+      "when": "the DOM is inspected before any state-driven announcement fires",
+      "then": "both polite (aria-live=polite) and assertive (aria-live=assertive) live-region containers are present in the initial DOM",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/TR/WCAG22/#status-messages",
+        "verifiedOn": "2026-09-10"
+      }
     }
   ],
-  "tacIds": ["TAC-2101-application-notifications-in-app-live-region"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2101-application-notifications-in-app-live-region"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20102.json

@@ -16,7 +16,8 @@
       "when": "the accessibility tree and the toast timestamps are read",
       "then": "the priority-to-role mapping holds, the announcement is one-shot, and the timeout is at or above the six second floor",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-20102-2",
@@ -25,11 +26,48 @@
       "when": "the factory is invoked at a given priority",
       "then": "the correct wrapper receives the toast",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2101-application-notifications-in-app-live-region",
+        "field": "interfaces.renderToast"
+      }
+    },
+    {
+      "id": "AC-20102-3",
+      "description": "Apply refuses a toast-timeout-floor answer below 6 seconds with TOAST_TIMEOUT_TOO_SHORT naming the elicited value; a value at or above 6 seconds applies and the polite toast honours it. Vendor citation on WCAG 2.2.1 (https://www.w3.org/TR/WCAG22/#timing-adjustable, verified 2026-09-10).",
+      "given": "a project elicits a toast-timeout-floor below 6 seconds",
+      "when": "apply runs",
+      "then": "apply exits with a non-zero code and TOAST_TIMEOUT_TOO_SHORT names the elicited value; at or above 6 seconds apply succeeds",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/TR/WCAG22/#timing-adjustable",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-20102-4",
+      "description": "A transient toast auto-dismisses at the elicited timeout only if the principal has not focused it; a focused toast pauses the timer and resumes only after focus leaves (WCAG 2.2.1 Timing Adjustable, https://www.w3.org/TR/WCAG22/#timing-adjustable, verified 2026-09-10).",
+      "given": "a rendered toast and the principal focuses it via the keyboard",
+      "when": "the elicited timeout elapses",
+      "then": "the toast remains visible until focus leaves; on focus loss the timer resumes",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/TR/WCAG22/#timing-adjustable",
+        "verifiedOn": "2026-09-10"
+      }
     }
   ],
-  "tacIds": ["TAC-2101-application-notifications-in-app-live-region"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2101-application-notifications-in-app-live-region"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20103.json

@@ -16,7 +16,8 @@
       "when": "an acknowledge control is activated by keyboard",
       "then": "the acknowledge round-trips to the server and the DOM updates in response",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-20103-2",
@@ -25,11 +26,44 @@
       "when": "the delivery log is read",
       "then": "one wrapper is emitted per row within the retention window",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.renderCentre"
+      }
+    },
+    {
+      "id": "AC-20103-3",
+      "description": "When the acknowledge round-trip returns a non-2xx or times out, an error toast surfaces via the assertive live region naming the failure, and data-acknowledged on the row remains false (the row is not visually or programmatically marked read).",
+      "given": "a notification row and an acknowledge POST that returns a non-2xx or times out",
+      "when": "the principal activates the acknowledge control",
+      "then": "an error toast appears via role=alert, data-acknowledged=false remains and no polite acknowledgement announcement fires",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.acknowledgeRoundTrip"
+      }
+    },
+    {
+      "id": "AC-20103-4",
+      "description": "The notification centre inbox lists the last N days of notifications enumerated by data-notification-id and paginates once N exceeds the elicited page-size; a paginated request that fails leaves the currently loaded rows visible and shows an inline retry. Applying agent sets: page-size.",
+      "given": "an inbox whose N exceeds the page-size and a paginated fetch that fails",
+      "when": "the principal scrolls or paginates",
+      "then": "the previously loaded rows remain visible, an inline retry control appears and no rows are removed on the failure",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template"
     }
   ],
-  "tacIds": ["TAC-2102-application-notifications-in-app-centre"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2102-application-notifications-in-app-centre"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20104.json

@@ -16,7 +16,8 @@
       "when": "a silence toggle is activated",
       "then": "the preference is recorded and reflected on the DOM",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-20104-2",
@@ -25,11 +26,36 @@
       "when": "the digest opt-in section is read",
       "then": "the section is disabled and labelled as sibling not applied",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-20104-3",
+      "description": "When the preference write POST returns a non-2xx or times out, an error toast surfaces via the assertive live region, the toggle in the DOM returns to its pre-click state and no false persisted-state is shown.",
+      "given": "a preference toggle change and a write POST that returns a non-2xx or times out",
+      "when": "the principal toggles the preference",
+      "then": "an error toast fires, the toggle rolls back to its pre-click state, and no data-persisted=true is emitted",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-20104-4",
+      "description": "On a successful preference write, the polite live region announces the new persisted state and the toggle reflects it. Two rapid clicks are debounced to a single write (idempotency of a retried operation).",
+      "given": "a preference toggle change accepted by the write POST",
+      "when": "the write returns 2xx",
+      "then": "the polite live region announces the new state, data-persisted=true is emitted, and two rapid clicks fire exactly one write",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
-  "tacIds": ["TAC-2103-application-notifications-in-app-preferences"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2103-application-notifications-in-app-preferences"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20105.json

@@ -4,19 +4,24 @@
   "reqId": "application-notifications-in-app-REQ-005",
   "version": "1.0.0",
   "status": "approved",
-  "title": "The delivery-attempt log records one row per surfaced notification with the operator-readable fields for later inspection",
+  "title": "The delivery-attempt log records one row per surfaced notification, in the shape owned by TAC-2102, for later inspection",
   "asA": "operator inspecting the notification behaviour of a shipped rcf-lite application",
-  "iWant": "one row in the delivery-attempt log per notification the shell surfaced, with the priority, the category and the delivery and acknowledgement timestamps",
+  "iWant": "one row in the delivery-attempt log per notification the shell surfaced, in the shape owned by `TAC-2102.interfaces.deliveryRowShape`",
   "soThat": "I can reconcile what the shell said with what my operators saw and acknowledged",
   "acceptanceCriteria": [
     {
       "id": "AC-20105-1",
-      "description": "Given a shipped surface that has surfaced N notifications, `GET /api/delivery-log` returns HTTP 200 with body `{ rows: [...] }` and `rows.length === N`; each row carries `notificationId` (string), `category` (string), `priority` (`\"info\"` or `\"error\"`), `deliveredAt` (ISO-8601 timestamp); a row for a dismissed toast additionally carries `dismissedAt`; a row for an acknowledged centre item additionally carries `acknowledgedAt`. Rows are append-only; a `notificationId` never appears twice on the same page load. The pack does not itself enumerate every row (the delivery log's persistence is delegated to the applied `logging` companion); the AC is a mechanism-reach gap for a v1.1 minor bump when the pack gains a log-shape probe.",
+      "description": "Given a shipped surface that has surfaced N notifications, `GET /api/delivery-log` returns HTTP 200 with body `{ rows: [...] }` and `rows.length === N`; each row honours the shape owned by `TAC-2102.interfaces.deliveryRowShape`. Rows are append-only; the same delivery event never appears twice on the same page load. The pack does not itself enumerate every row (the delivery-log persistence is delegated to the applied `logging` companion); the AC is a mechanism-reach gap for a v1.1 minor bump when the pack gains a log-shape probe.",
       "given": "a shipped surface after N notifications",
       "when": "the delivery-log endpoint is read",
       "then": "N rows with the operator-readable fields are returned",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.deliveryRowShape"
+      }
     },
     {
       "id": "AC-20105-2",
@@ -25,11 +30,48 @@
       "when": "a toast or centre event surfaces a notification",
       "then": "a row lands through the applied logging companion",
       "testable": true,
-      "scope": "library"
+      "scope": "library",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.writeDeliveryRow"
+      }
+    },
+    {
+      "id": "AC-20105-3",
+      "description": "A delivery-attempt log row honours exactly the field set owned by `TAC-2102.interfaces.deliveryRowShape`; a row missing any owner-required field refuses the write with DELIVERY_ROW_INCOMPLETE naming the missing owner-required field (per the owner shape).",
+      "given": "a delivery attempt whose row is missing an owner-required field owned by `TAC-2102.interfaces.deliveryRowShape`",
+      "when": "the row write fires",
+      "then": "the write refuses with DELIVERY_ROW_INCOMPLETE naming the missing owner-required field and no partial row is persisted",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.deliveryRowShape"
+      }
+    },
+    {
+      "id": "AC-20105-4",
+      "description": "When no applied blueprint provides the `logging` companion (no writeDeliveryRow factory on the applied set), apply refuses with LOGGING_COMPANION_MISSING naming the required remedy (apply the logging companion so the delivery-log rows can persist); no delivery-log entries are written and the toast and centre factories refuse to construct.",
+      "given": "a project applying application-notifications-in-app with no logging companion applied",
+      "when": "apply runs",
+      "then": "apply exits with a non-zero code and LOGGING_COMPANION_MISSING is emitted naming the remedy (apply the logging companion)",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-2102-application-notifications-in-app-centre",
+        "field": "interfaces.writeDeliveryRow"
+      }
     }
   ],
-  "tacIds": ["TAC-2102-application-notifications-in-app-centre"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2102-application-notifications-in-app-centre"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20106.json

@@ -16,11 +16,26 @@
       "when": "the initial DOM and the live-region wrappers are read",
       "then": "the backlog is rendered on the surface and neither live-region wrapper carries a load-time announcement",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-20106-2",
+      "description": "When the backlog fetch on page load returns a non-2xx or times out, the inbox renders the last cached rows (if any) with a fetch-failed banner and an inline retry; no rows are shown as read that were not previously acknowledged.",
+      "given": "a page load whose backlog fetch fails",
+      "when": "the inbox route renders",
+      "then": "the last cached rows appear with a fetch-failed banner and inline retry; no false read state is shown",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
-  "tacIds": ["TAC-2102-application-notifications-in-app-centre"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2102-application-notifications-in-app-centre"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20107.json

@@ -16,11 +16,26 @@
       "when": "the toast DOM is read",
       "then": "the priority-to-role mapping and the one-shot announcement match an operator-driven toast",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-20107-2",
+      "description": "A background-driven toast that lacks a priority field or a category outside the elicited enum refuses the toast render with TOAST_PAYLOAD_INVALID naming the missing or invalid field, and never surfaces to the DOM.",
+      "given": "a background event that emits a toast payload with a missing priority or unknown category",
+      "when": "the event fires",
+      "then": "no toast renders, TOAST_PAYLOAD_INVALID names the field and the event is logged",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
-  "tacIds": ["TAC-2101-application-notifications-in-app-live-region"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2101-application-notifications-in-app-live-region"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/contributions/user-stories/application-notifications-in-app-us-20108.json

@@ -16,11 +16,26 @@
       "when": "both live-region wrappers are read simultaneously",
       "then": "the body text appears in exactly one wrapper",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-20108-2",
+      "description": "When the priority-to-role contract fires with an invalid priority, the announcement is dropped and a console log records the invalid value; no accidental double-announce lands in the alternate live region as a fallback.",
+      "given": "an announcement carrying a priority outside the closed enum",
+      "when": "the announcement is dispatched",
+      "then": "no live region receives the announcement, the console log records the invalid priority and no fallback double-announce fires",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
-  "tacIds": ["TAC-2101-application-notifications-in-app-live-region"],
-  "tags": ["blueprint:application-notifications-in-app"],
+  "tacIds": [
+    "TAC-2101-application-notifications-in-app-live-region"
+  ],
+  "tags": [
+    "blueprint:application-notifications-in-app"
+  ],
   "createdAt": "2026-09-04T23:59:00Z",
-  "updatedAt": "2026-09-04T23:59:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-notifications-in-app/docs/topics.md

@@ -28,7 +28,7 @@ The `application-notifications-` prefix is reserved for the sibling channel blue
 | 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` |