rcf-lite 0.26.0 → 0.27.0

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

@@ -13,7 +13,22 @@
       "id": "AC-24106-1",
       "testable": true,
       "scope": "runtime",
-      "description": "On the ?nav=linear branch, task-list rows whose [data-step-state] is Cannot start yet render as non-anchor spans (no clickable href) and the pack asserts a click on the row does not change the URL. On the ?nav=free branch every row renders as an anchor and a click on any row navigates to that step's route. ADR-2501 records the elicit and the shipped default is linear."
+      "description": "On the ?nav=linear branch, task-list rows whose [data-step-state] is Cannot start yet render as non-anchor spans (no clickable href) and the pack asserts a click on the row does not change the URL. On the ?nav=free branch every row renders as an anchor and a click on any row navigates to that step's route. ADR-2501 records the elicit and the shipped default is linear.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-24106-2",
+      "description": "Alternative step-indicator contracts drawn from the closed set owned by `ADR-2503.decision` each render exactly the contract for the elicited option; a value outside the owned set refuses at apply with STEP_INDICATOR_UNKNOWN naming the value.",
+      "given": "a project elicits a step-indicator outside the closed set",
+      "when": "apply runs",
+      "then": "apply exits with a non-zero code and STEP_INDICATOR_UNKNOWN names the value; each option in the set owned by `ADR-2503.decision` renders its own contract",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "adrId": "ADR-2503-application-forms-wizard-step-indicator",
+        "field": "decision"
+      }
     }
   ],
   "tacIds": [
@@ -24,5 +39,5 @@
     "case:linear-vs-free-navigation"
   ],
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
-}
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

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

@@ -13,7 +13,28 @@
       "id": "AC-24107-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given at least one draft persisted per REQ-005, /in-progress renders [data-surface=\"in-progress-list\"] with one [data-wizard-row] per draft carrying the wizard title, the step slug the operator was on and a [data-recovery=\"resume\"] link whose href routes back to the wizard's task-list surface. The row count matches the number of drafts held in the draft store."
+      "description": "Given at least one draft persisted per REQ-005, /in-progress renders [data-surface=\"in-progress-list\"] with one [data-wizard-row] per draft carrying the wizard title, the step slug the operator was on and a [data-recovery=\"resume\"] link whose href routes back to the wizard's task-list surface. The row count matches the number of drafts held in the draft store.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-24107-2",
+      "description": "When the in-progress list read returns a non-2xx or times out, the surface renders the last cached list (if any) with a fetch-failed banner and an inline retry; drafts owned by other principals never appear in the list even on a stale cache.",
+      "given": "a server-side draft list whose read returns a non-2xx or times out",
+      "when": "the in-progress list surface renders",
+      "then": "the last cached list renders with a fetch-failed banner, an inline retry is keyboard-reachable and no cross-principal draft appears",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-24107-3",
+      "description": "A draft in the list is only shown to its owning principal; a request from another principal for the same draft id refuses at the applied auth boundary and never renders the draft on the list.",
+      "given": "a draft owned by principal A and a request from principal B",
+      "when": "the list surface renders for principal B",
+      "then": "the draft is not present in the list and any direct URL for principal B refuses at the auth boundary",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -24,5 +45,5 @@
     "case:in-progress-list"
   ],
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

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

@@ -13,7 +13,18 @@
       "id": "AC-24108-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given zero drafts in the draft store, /in-progress renders [data-surface=\"empty-list\"] (the empty-list wrapper contributed by application-empty-error-states) with a [data-recovery=\"create\"] control whose href routes to the first step of a fresh wizard. The pack asserts the wrapper and the control are present on the honest render and refuses when either is missing."
+      "description": "Given zero drafts in the draft store, /in-progress renders [data-surface=\"empty-list\"] (the empty-list wrapper contributed by application-empty-error-states) with a [data-recovery=\"create\"] control whose href routes to the first step of a fresh wizard. The pack asserts the wrapper and the control are present on the honest render and refuses when either is missing.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-24108-2",
+      "description": "When application-empty-error-states is not applied, the empty in-progress list renders a minimal inline empty message inside the wizards own surface rather than crashing or leaving a blank region; a break that removes the fallback fails the pack.",
+      "given": "application-empty-error-states not applied and no drafts held",
+      "when": "the in-progress list surface renders",
+      "then": "a minimal inline empty message renders and no blank region appears",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -25,5 +36,5 @@
     "consumes:application-empty-error-states"
   ],
   "createdAt": "2026-09-06T18:00:00Z",
-  "updatedAt": "2026-09-06T18:00:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-forms-wizard/probe-packs/application-forms-wizard.pack.mjs

@@ -13,9 +13,9 @@
 //              on ?draft-store=local; the ?draft-store=none branch
 //              proves the missing-transport refusal on the fixture)
 //
-// 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
+// helper per the round 3 fix train; no bare string
 // concatenation.
 //
 // Sample-app fixture:
@@ -42,7 +42,7 @@ export default {
   // Applies to any FBS that realises the task-list TAC or whose
   // navModel routes name an operator-configured wizard path.
   // References BOTH tacIds AND route per the loader source-scan
-  // rule (T-0 AC-1701-3, cross-check with authoring standard 8c).
+  // rule (AC-1701-3, cross-check with authoring standard 8c).
   appliesTo: ({ fbs }) => {
     const routes = fbs?.designStage?.navModel?.routes ?? [];
     const tacIds = fbs?.contextRequirements?.tacIds ?? [];

package/blueprints/application-notifications-in-app/CHANGELOG.md

@@ -1,9 +1,41 @@
 # application-notifications-in-app CHANGELOG
 
-## 1.0.0 (visual round T-4, spec 2026-09-04)
+## 1.2.0 (2026-09-10)
+
+### Added
+
+- Five elicits (`timeout`, `retention`, `categories`, `route`, `page-size`) declared on blueprint.json; REQ-006 binds one runtime clause per apply-time answer family.
+- New AC-20105-4 refuses apply with `LOGGING_COMPANION_MISSING` when no logging companion is applied.
+
+### Changed
+
+- `TAC-2102.interfaces.deliveryRowShape` owns the row schema (`deliveryTs`, `priority`, `category`, `outcome`, `correlationId`); AC-20105-1, AC-20105-3 and REQ-005 reference the owner via ownerRef.
+- REQ-001.deliveredBy retargeted to `TAC-2101.interfaces.renderLiveRegions`.
+- REQ-004.deliveredBy retargeted to `TAC-2103.interfaces.renderPreferences`.
+- REQ-005.deliveredBy retargeted to `TAC-2102.writeDeliveryRow`.
+- AC-20102-3 and AC-20102-4 descriptions carry the W3C URL inline alongside the existing vendorCitation object.
+
+## 1.1.1 (register-sweep patch, 2026-09-10)
+
+- Register: neutral wording in shipped prose (no capability change).
+
+## 1.1.0 (2026-09-10, hardening pass)
+
+### Added
+
+- Failure-path acceptance criteria on US-20101 (live-region wrappers pre-seeded before any state-driven mount), US-20102 (sub-6s timeout apply refusal with TOAST_TIMEOUT_TOO_SHORT, focused-toast pause per WCAG 2.2.1), US-20103 (non-2xx acknowledgement error toast with unchanged data-acknowledged, paginated fetch failure), US-20104 (failed preference write error toast with toggle rollback, idempotency of retried writes), US-20105 (delivery-row incomplete refusal), US-20106 (page-load backlog failure with cached-row banner), US-20107 (invalid toast payload refusal), US-20108 (invalid priority drop). Closes review findings F-1, F-2 and F-3.
+- Vendor citations on the WCAG 2.2.1 Timing Adjustable and status-messages acceptance criteria (verified 2026-09-10).
+
+### Changed
+
+- Every REQ now carries a deliveredBy link into TAC-2101 (live-region), TAC-2102 (centre) or TAC-2103 (preferences).
+- Every AC on every user story now carries an explicit disposition (fixed or template); ACs that observe writeDeliveryRow, renderLiveRegions, renderToast or renderCentre carry ownerRef into the owning TAC field.
+- Review fix pass (2026-09-10): README, TAC-2103 and REQ-004 register scrubbed (no operator names or work-item ids). Closes review-fix-pass findings O-2, O-3.
+
+## 1.0.0 (visual round, spec 2026-09-04)
 
 - First ratified version of the shelf's application-notifications-in-app blueprint. Five REQs (live-region preseeding on every declared route; transient toast contract with priority-to-role mapping, one-shot announcement and timeout floor; notification centre inbox with retention and acknowledge round-trip; per-user preferences UI with category silence and sibling delegation; delivery-attempt log with operator-readable rows), eight USs binding runtime-observable ACs plus three cross-cutting cases (page load with backlog, background event, disjoint-content contract), three TACs (live-region wrappers with the toast factory; centre inbox with retention and acknowledge round-trip; preferences UI with sibling delegation), three ADRs (priority-to-role mapping polite/status vs assertive/alert per WCAG 4.1.3 and the ARIA APG alert pattern; six-second toast timeout floor per WCAG 2.2.1 with elicited overrides above the floor; thirty-day centre retention window with elicited overrides). No new global topics.
-- Reserves the `application-notifications-` family prefix for the sibling channel blueprints the shelf will grow into (`-email`, `-push`, `-webhook`) as a doc-only reservation on the blueprint README and every applying blueprint's `docs/topics.md` shelf band registry per Baz decision 2026-09-04 ("we might support more types of notifications - be clear in the name what these ones are").
-- Ships `probe-packs/application-notifications-in-app.pack.mjs`: three browser-verify checks anchored to blueprint AC ids, every check carrying a description field per spec section 9. `AC-20101-1` live-region preseeded on every declared route (wrappers present AND empty at load, enumerated by `[data-live-region]`). `AC-20102-1` transient toast contract with priority-to-role mapping and timeout measured against the ADR-2102 six-second floor via `data-shown-at`/`data-dismissed-at` timestamps (no six-second sleep in the pack; bounded polling). `AC-20103-1` centre acknowledge round-trip enumerated by `data-notification-id` (per-element attribute per T-3 gate discipline), reconciled through both `window.__notificationFetches` and the server-side request log. Fourth blueprint on the shelf that ships a Playwright probe pack under the T-0 runner extension.
+- Reserves the `application-notifications-` family prefix for the sibling channel blueprints the shelf will grow into (`-email`, `-push`, `-webhook`) as a doc-only reservation on the blueprint README and every applying blueprint's `docs/topics.md` shelf band registry per the 2026-09-04 shelf decision to make the transport type explicit in the blueprint name.
+- Ships `probe-packs/application-notifications-in-app.pack.mjs`: three browser-verify checks anchored to blueprint AC ids, every check carrying a description field per spec section 9. `AC-20101-1` live-region preseeded on every declared route (wrappers present AND empty at load, enumerated by `[data-live-region]`). `AC-20102-1` transient toast contract with priority-to-role mapping and timeout measured against the ADR-2102 six-second floor via `data-shown-at`/`data-dismissed-at` timestamps (no six-second sleep in the pack; bounded polling). `AC-20103-1` centre acknowledge round-trip enumerated by `data-notification-id` (per-element attribute per gate discipline), reconciled through both `window.__notificationFetches` and the server-side request log. Fourth blueprint on the shelf that ships a Playwright probe pack under the runner extension.
 - Ships a sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-notifications-in-app/` (dependency-free Node HTTP server) so the pack can be probed at the shelf's own gate; the fixture is the golden the gate reviewer drives, with `?break=preseed`, `?break=role`, `?break=timeout` and `?break=ack` query switches for the negative runs. Three routes (`/`, `/notifications-centre`, `/notifications-preferences`); every route preseeds both live-region wrappers.
 - Suggests the `logging` and `errorHandling` companions with the ratified spec's reasons. `providesRoles` absent, leaf blueprint per the loader contract (an empty array is refused, an omitted field marks the blueprint as a leaf).

package/blueprints/application-notifications-in-app/README.md

@@ -1,6 +1,6 @@
 # Notifications in-app blueprint (v1.0.0)
 
-Vendor-neutral in-app-notifications contract for a rcf-lite application. Ships the live-region preseeding discipline (polite and assertive wrappers present in the DOM before any notification fires per the WAI-ARIA 1.2 normative reference), the transient toast contract with priority-to-role mapping (info to polite/status, error to assertive/alert per WCAG 4.1.3 and the ARIA APG alert pattern), the WCAG 2.2.1 six-second toast timeout floor with operator-elicited overrides above the floor, the notification centre inbox with a thirty-day retention window and a per-item acknowledge round-trip enumerated by `data-notification-id`, the per-user preferences UI with category silence and sibling-channel digest delegation, and the delivery-attempt log write path. Ships a Playwright probe pack under `probe-packs/application-notifications-in-app.pack.mjs` whose three checks are the runtime gate the delivery-ci-workflows runner drives (visual round spec 2026-09-04, section 5.4). No new global topics; suggests the `logging` and `errorHandling` companions. Fourth blueprint on the shelf that ships a Playwright probe pack under the T-0 runner extension.
+Vendor-neutral in-app-notifications contract for a rcf-lite application. Ships the live-region preseeding discipline (polite and assertive wrappers present in the DOM before any notification fires per the WAI-ARIA 1.2 normative reference), the transient toast contract with priority-to-role mapping (info to polite/status, error to assertive/alert per WCAG 4.1.3 and the ARIA APG alert pattern), the WCAG 2.2.1 six-second toast timeout floor with operator-elicited overrides above the floor, the notification centre inbox with a thirty-day retention window and a per-item acknowledge round-trip enumerated by `data-notification-id`, the per-user preferences UI with category silence and sibling-channel digest delegation, and the delivery-attempt log write path. Ships a Playwright probe pack under `probe-packs/application-notifications-in-app.pack.mjs` whose three checks are the runtime gate the delivery-ci-workflows runner drives (visual round spec 2026-09-04, section 5.4). No new global topics; suggests the `logging` and `errorHandling` companions. Fourth blueprint on the shelf that ships a Playwright probe pack under the runner extension.
 
 ## Apply
 
@@ -24,7 +24,7 @@ Applies namespaced contributions into the project tree and records `manifest.blu
 
 Contributed: REQ, US (with inline ACs), TAC, ADR, plus one shipped probe pack. Adherence is expressed as ACs; the blueprint ships no notifications-framework source and no test files (the probe pack drives the real browser against the applying project's own runtime).
 
-Deliberately not contributed: any transport (email, push, webhook). The in-app slug is the discriminator per Baz decision 2026-09-04: "we might support more types of notifications - be clear in the name what these ones are". Sibling channel blueprints ship their own transport contracts under the reserved `application-notifications-` family prefix.
+Deliberately not contributed: any transport (email, push, webhook). The in-app slug is the discriminator per the 2026-09-04 shelf decision to make the transport type explicit in the blueprint name. Sibling channel blueprints ship their own transport contracts under the reserved `application-notifications-` family prefix.
 
 ## Family-prefix reservation
 
@@ -44,7 +44,7 @@ Every route the applying project ships renders with both live-region wrappers pr
 
 ## Known mechanism-reach gaps
 
-Every runtime-observable AC that is not bound to a pack check appears here individually per the T-1 gate discipline (`blueprint-authoring-checklist.md` section 6.g): categories are not enough. The pack has three checks; every other runtime-observable AC on this blueprint is a mechanism-reach gap named below.
+Every runtime-observable AC that is not bound to a pack check appears here individually per the gate discipline (`blueprint-authoring-checklist.md` section 6.g): categories are not enough. The pack has three checks; every other runtime-observable AC on this blueprint is a mechanism-reach gap named below.
 
 - **AC-20101-2 live-region factory identity stable across route changes**. The pack asserts the wrappers are preseeded on every declared route (AC-20101-1); it does not assert the two wrappers are the same DOM nodes across route changes (a factory that recreates the wrappers on route change passes AC-20101-1 but fails AC-20101-2). A v1.1 minor bump could persist a `data-live-region-id` on each wrapper and assert identity across a `browser.click` on a nav link.
 - **AC-20102-2 toast factory library-scope shape**. The pack drives the runtime toast surface (AC-20102-1); the library-scope AC on the factory's own signature is a project-side review concern.
@@ -60,7 +60,7 @@ Every runtime-observable AC that is not bound to a pack check appears here indiv
 
 ## Elicited parameters (ADR-2101 through ADR-2103 and REQ notes)
 
-The applying project elicits these at apply; the declarative ADR shape (`elicited: true`) records the intent on the manifest. The runner has no apply-time elicitation phase today (w-2026-09-04-dave-022, built in T-5); accept the declarative shape and gather the operator's answers by hand during the apply pass.
+The applying project elicits these at apply; the declarative ADR shape (`elicited: true`) records the intent on the manifest. The runner has no apply-time elicitation phase today (planned for a follow-up minor); accept the declarative shape and gather the operator's answers by hand during the apply pass.
 
 - **Toast timeout floor** (ADR-2102): six seconds baseline per WCAG 2.2.1; operator elicits an override above the floor (twelve seconds, thirty seconds); the elicited value lands on `manifest.blueprints[application-notifications-in-app].appliedParameters.toastTimeoutSeconds`. A value below six is refused at apply.
 - **Notification categories** (REQ-004): the operator's category list (payment, security, product, and any project-specific categories). The preferences UI renders one section per elicited category.
@@ -77,4 +77,4 @@ WCAG 4.1.3 Status Messages on the live-region contract (REQ-001, ADR-2101). ARIA
 - Consumes the applied `logging` companion (or the shelf provider `observability-logging`) for the delivery-attempt log write path (REQ-005, TAC-2102) and every acknowledge round-trip record. A project without a `logging` companion applied sees the delivery-log endpoint returning an empty rows array, which fails project-side review.
 - Consumes the applied `errorHandling` companion (or the shelf provider `application-error-handling`) for the assertive-slot alert's internal error record when an acknowledge round-trip fails at the server.
 - Reserves the `application-notifications-` family prefix for sibling channel blueprints (see above).
-- Reuses the T-3 pack-browser `resize(width, height)` seam only for future minor bumps; v1.0.0 does not exercise breakpoint reflow in the pack.
+- Reuses the pack-browser `resize(width, height)` seam only for future minor bumps; v1.0.0 does not exercise breakpoint reflow in the pack.

package/blueprints/application-notifications-in-app/blueprint.json

@@ -1,30 +1,158 @@
 {
   "slug": "application-notifications-in-app",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "category": "application",
   "suggestedCompanions": [
-    { "role": "logging", "reason": "Every acknowledge round-trip and every delivery-attempt row is written through the applied logger; a logging companion supplies the factory the notification centre, the toast surface and the delivery-attempt log write records against." },
-    { "role": "errorHandling", "reason": "The assertive-slot alert routes an internal error record whose error envelope conforms to the applied error contract; an errorHandling companion supplies the record factory and the surface boundary the alert toast renders through." }
+    {
+      "role": "logging",
+      "reason": "Every acknowledge round-trip and every delivery-attempt row is written through the applied logger; a logging companion supplies the factory the notification centre, the toast surface and the delivery-attempt log write records against."
+    },
+    {
+      "role": "errorHandling",
+      "reason": "The assertive-slot alert routes an internal error record whose error envelope conforms to the applied error contract; an errorHandling companion supplies the record factory and the surface boundary the alert toast renders through."
+    }
   ],
   "contributions": [
-    { "id": "application-notifications-in-app-REQ-001", "kind": "req", "path": "requirements/application-notifications-in-app-req-001.json" },
-    { "id": "application-notifications-in-app-REQ-002", "kind": "req", "path": "requirements/application-notifications-in-app-req-002.json" },
-    { "id": "application-notifications-in-app-REQ-003", "kind": "req", "path": "requirements/application-notifications-in-app-req-003.json" },
-    { "id": "application-notifications-in-app-REQ-004", "kind": "req", "path": "requirements/application-notifications-in-app-req-004.json" },
-    { "id": "application-notifications-in-app-REQ-005", "kind": "req", "path": "requirements/application-notifications-in-app-req-005.json" },
-    { "id": "application-notifications-in-app-US-20101", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20101.json" },
-    { "id": "application-notifications-in-app-US-20102", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20102.json" },
-    { "id": "application-notifications-in-app-US-20103", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20103.json" },
-    { "id": "application-notifications-in-app-US-20104", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20104.json" },
-    { "id": "application-notifications-in-app-US-20105", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20105.json" },
-    { "id": "application-notifications-in-app-US-20106", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20106.json" },
-    { "id": "application-notifications-in-app-US-20107", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20107.json" },
-    { "id": "application-notifications-in-app-US-20108", "kind": "us", "path": "user-stories/application-notifications-in-app-us-20108.json" },
-    { "id": "TAC-2101-application-notifications-in-app-live-region", "kind": "tac", "path": "tacs/tac-2101-application-notifications-in-app-live-region.json" },
-    { "id": "TAC-2102-application-notifications-in-app-centre", "kind": "tac", "path": "tacs/tac-2102-application-notifications-in-app-centre.json" },
-    { "id": "TAC-2103-application-notifications-in-app-preferences", "kind": "tac", "path": "tacs/tac-2103-application-notifications-in-app-preferences.json" },
-    { "id": "ADR-2101-application-notifications-in-app-live-region-role-mapping", "kind": "adr", "path": "adrs/adr-2101-application-notifications-in-app-live-region-role-mapping.json", "recommendedDefault": true, "elicited": false, "standardsTraceClause": "WCAG 4.1.3 (Status Messages); ARIA APG alert pattern" },
-    { "id": "ADR-2102-application-notifications-in-app-toast-timeout-floor", "kind": "adr", "path": "adrs/adr-2102-application-notifications-in-app-toast-timeout-floor.json", "recommendedDefault": true, "elicited": true, "standardsTraceClause": "WCAG 2.2.1 (Timing Adjustable)" },
-    { "id": "ADR-2103-application-notifications-in-app-retention-window", "kind": "adr", "path": "adrs/adr-2103-application-notifications-in-app-retention-window.json", "recommendedDefault": true, "elicited": true, "standardsTraceClause": "generic enterprise practice" }
+    {
+      "id": "application-notifications-in-app-REQ-001",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-001.json"
+    },
+    {
+      "id": "application-notifications-in-app-REQ-002",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-002.json"
+    },
+    {
+      "id": "application-notifications-in-app-REQ-003",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-003.json"
+    },
+    {
+      "id": "application-notifications-in-app-REQ-004",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-004.json"
+    },
+    {
+      "id": "application-notifications-in-app-REQ-005",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-005.json"
+    },
+    {
+      "id": "application-notifications-in-app-REQ-006",
+      "kind": "req",
+      "path": "requirements/application-notifications-in-app-req-006.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20101",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20101.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20102",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20102.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20103",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20103.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20104",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20104.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20105",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20105.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20106",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20106.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20107",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20107.json"
+    },
+    {
+      "id": "application-notifications-in-app-US-20108",
+      "kind": "us",
+      "path": "user-stories/application-notifications-in-app-us-20108.json"
+    },
+    {
+      "id": "TAC-2101-application-notifications-in-app-live-region",
+      "kind": "tac",
+      "path": "tacs/tac-2101-application-notifications-in-app-live-region.json"
+    },
+    {
+      "id": "TAC-2102-application-notifications-in-app-centre",
+      "kind": "tac",
+      "path": "tacs/tac-2102-application-notifications-in-app-centre.json"
+    },
+    {
+      "id": "TAC-2103-application-notifications-in-app-preferences",
+      "kind": "tac",
+      "path": "tacs/tac-2103-application-notifications-in-app-preferences.json"
+    },
+    {
+      "id": "ADR-2101-application-notifications-in-app-live-region-role-mapping",
+      "kind": "adr",
+      "path": "adrs/adr-2101-application-notifications-in-app-live-region-role-mapping.json",
+      "recommendedDefault": true,
+      "elicited": false,
+      "standardsTraceClause": "WCAG 4.1.3 (Status Messages); ARIA APG alert pattern"
+    },
+    {
+      "id": "ADR-2102-application-notifications-in-app-toast-timeout-floor",
+      "kind": "adr",
+      "path": "adrs/adr-2102-application-notifications-in-app-toast-timeout-floor.json",
+      "recommendedDefault": true,
+      "elicited": true,
+      "standardsTraceClause": "WCAG 2.2.1 (Timing Adjustable)"
+    },
+    {
+      "id": "ADR-2103-application-notifications-in-app-retention-window",
+      "kind": "adr",
+      "path": "adrs/adr-2103-application-notifications-in-app-retention-window.json",
+      "recommendedDefault": true,
+      "elicited": true,
+      "standardsTraceClause": "generic enterprise practice"
+    }
+  ],
+  "elicits": [
+    {
+      "id": "timeout",
+      "prompt": "Toast timeout floor in seconds (must be at least 6 per ADR-2102).",
+      "kind": "string",
+      "default": "6"
+    },
+    {
+      "id": "retention",
+      "prompt": "Notification-centre retention window in days.",
+      "kind": "string",
+      "default": "30"
+    },
+    {
+      "id": "categories",
+      "prompt": "Notification categories (comma-separated) the preferences UI enumerates.",
+      "kind": "string",
+      "default": "account,billing,security"
+    },
+    {
+      "id": "route",
+      "prompt": "Preferences route path.",
+      "kind": "string",
+      "default": "/notifications-preferences"
+    },
+    {
+      "id": "page-size",
+      "prompt": "Notification-centre page size (positive integer).",
+      "kind": "string",
+      "default": "20"
+    }
   ]
 }

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

@@ -2,14 +2,21 @@
   "reqId": "application-notifications-in-app-REQ-001",
   "prdId": "PRD-001",
   "title": "The application shell preseeds the polite and assertive live-region wrappers on every declared route before any notification fires",
-  "description": "Every route the applying project declares under its navigation model renders with the two live-region wrappers already present in the DOM at page load: a `[aria-live=\"polite\"]` wrapper for informational messages and a `[role=\"alert\"]` wrapper for assertive alerts. Both wrappers exist and are empty before any notification fires; a wrapper inserted lazily after the first event is a defect that produces a screen-reader miss per the Sara Soueidan normative guidance on ARIA live regions. The wrappers carry stable `data-live-region=\"polite\"` and `data-live-region=\"assertive\"` attributes so the pack can enumerate them by data-id (not by role attribute alone, per the T-3 gate discipline).",
+  "description": "Every route the applying project declares under its navigation model renders with the two live-region wrappers already present in the DOM at page load: a `[aria-live=\"polite\"]` wrapper for informational messages and a `[role=\"alert\"]` wrapper for assertive alerts. Both wrappers exist and are empty before any notification fires; a wrapper inserted lazily after the first event is a defect that produces a screen-reader miss per the Sara Soueidan normative guidance on ARIA live regions. The wrappers carry stable `data-live-region=\"polite\"` and `data-live-region=\"assertive\"` attributes so the pack can enumerate them by data-id (not by role attribute alone, per the gate discipline).",
+  "deliveredBy": {
+    "tacId": "TAC-2101-application-notifications-in-app-live-region",
+    "field": "interfaces.renderLiveRegions"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
   "rationale": "The WAI-ARIA 1.2 live-regions normative contract requires the container to exist in the DOM before content is inserted; a wrapper inserted at the same tick as the content races the screen-reader announcement pass and the message is silently lost. Preseeding the two wrappers on every route is the runtime discipline that turns the WCAG 4.1.3 status-message clause from a design intent into a runtime-observable check the probe pack can drive.",
-  "tags": ["blueprint:application-notifications-in-app", "category:01-live-region-preseeding"],
-  "version": "1.0.0",
+  "tags": [
+    "blueprint:application-notifications-in-app",
+    "category:01-live-region-preseeding"
+  ],
+  "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-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"
+}