rcf-lite 0.25.0 → 0.27.0

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

@@ -39,7 +39,7 @@ Every route the applying project ships preseeds both live-region wrappers in the
 - The two live-region wrappers must be preseeded before the first notification. A lazy-mount defect is silent at the DOM (the wrapper appears "eventually") but loses the first announcement at the assistive-technology layer. The pack refuses ship on this shape.
 - The priority-to-role mapping is fixed at v1.0.0 (info to polite/status, error to assertive/alert). A third priority (`warning`) is a v1.1 minor bump because it changes the role vocabulary; free-form priorities are refused at project-side review.
 - The toast timeout floor is a floor, not a ceiling. Six seconds is the default; an operator-elicited value above the floor is honoured (thirty seconds), a value below the floor is refused at apply. The pack measures the actual elapsed time against the shell root's declared floor and against the six-second baseline; both must clear.
-- The centre enumerates items by `data-notification-id`, per the T-3 gate discipline. A centre implementation that uses only `role="listitem"` on the children (without a per-element id attribute) passes the accessibility contract but does not let the pack enumerate individual items reliably; ship both.
+- The centre enumerates items by `data-notification-id`, per the gate discipline. A centre implementation that uses only `role="listitem"` on the children (without a per-element id attribute) passes the accessibility contract but does not let the pack enumerate individual items reliably; ship both.
 - The family-prefix reservation is documented; naming a future notifications blueprint outside the family (`application-alerts-email`) reads against the reservation and stops at author-side review.
 
 ## Cost honesty

package/blueprints/application-notifications-in-app/probe-packs/application-notifications-in-app.pack.mjs

@@ -11,16 +11,16 @@
 //   AC-20103-1 centre acknowledge round-trip (Tab-reachable acknowledge
 //              control POSTs to the server, the server responds, the
 //              DOM updates in response; enumerated by data-notification-id
-//              per the T-3 gate discipline, never by role alone)
+//              per the gate discipline, never by role alone)
 //
-// Every check drives the real Playwright browser the T-0 runner
+// Every check drives the real Playwright browser the runner
 // injects (packages/rcf-lite/src/browser-verify/pack-browser.js) and
 // asserts on the DOM the applying project renders under TAC-2101
 // (live-region wrappers and toast factory), TAC-2102 (centre inbox
 // and acknowledge round-trip) and the priority-to-role mapping per
 // ADR-2101.
 //
-// The pack has no network-interception seam (T-0 shipped none); the
+// The pack has no network-interception seam (shipped none); the
 // acknowledge round-trip is captured through the request log the
 // sample app exposes on window.__notificationFetches and at
 // GET /__requests. The toast timeout is measured with browser.evaluate
@@ -34,7 +34,7 @@ export default {
   blueprintSlug: 'application-notifications-in-app',
   // Applies to any FBS that realises the live-region TAC or whose
   // navModel routes include a notifications-centre path. The source
-  // references BOTH `tacIds` and `route` so the T-0 loader's
+  // references BOTH `tacIds` and `route` so the loader's
   // applicability source-scan sees the two legal seams (route is one
   // of the three legal predicates).
   appliesTo: ({ fbs }) => {

package/blueprints/application-onboarding-tour/CHANGELOG.md

@@ -1,6 +1,37 @@
 # application-onboarding-tour CHANGELOG
 
-## 1.0.0 (visual round T-5, spec 2026-09-06 section 5.5)
+## 1.1.2 (2026-09-10)
+
+### Changed
+
+- AC-26109-1 requires `<details open>` per ADR-2703 and references the ADR via ownerRef.
+- ADR-2702 refusal-only decision: `server-side-per-principal` without an applied persistence blueprint refuses with `COMPLETION_STORE_MISSING_PROVIDER` and never falls back; TAC-2703 aligned.
+- AC-26108-4 references `TAC-2703.interfaces.completionStore` via ownerRef; drops the principalId/tourVersion/dismissedAt restatement.
+- AC-26104-2 names `server-side-per-principal` inline and its refusal `COMPLETION_STORE_MISSING_PROVIDER`.
+- REQ-002.deliveredBy retargeted to `TAC-2701.interfaces.renderTourRunner`.
+- Vendor citations on AC-26101-1 (WCAG keyboard) and AC-26102-1 (ARIA APG dialog-modal); AC-26102-2 URL naming tidied.
+
+## 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
+
+- REQ-005 (dismissal-policy option coverage) and US-26108: dismiss-permanently, dismiss-until-next-major and dismiss-until-next-minor each carry a runtime clause tied to the completion store record shape. This is the section 7c worked example landed as written. Closes review finding [application-onboarding-tour] F-1.
+- REQ-006 (checklist-anchor option coverage) and US-26109: dashboard-top, settings-page and custom-anchor each mount at a resolved slot with a defined default open state; custom-anchor falls back to the settings route on an unresolved/invisible/clipped selector with data-error=CHECKLIST_ANCHOR_UNRESOLVED. Closes review finding [application-onboarding-tour] F-2.
+- Failure-path acceptance criteria on US-26101 (unresolved and clipped anchors, out-of-range step count), US-26102 (dialog-modal role/aria and focus trap with WCAG citation), US-26103 (settings-route fallback), US-26104 (missing-provider refusal, failed write and failed read on the completion store), US-26105 (unparseable completion record), US-26106 (failed clear on restart), US-26107 (polite live-region close announcement). Closes findings F-3 and F-4.
+- Vendor citations on the ARIA APG dialog-modal, focus-trap and WCAG live-region acceptance criteria (verified 2026-09-10).
+
+### Changed
+
+- Every REQ now carries a deliveredBy link into TAC-2701 (step-runner), TAC-2702 (checklist-slot) or TAC-2703 (completion-store).
+- Every AC on every user story now carries an explicit disposition (fixed or template).
+- TAC-2702 responsibilities extended with resolveAnchor so REQ-006 delivery resolves.
+- Review fix pass (2026-09-10): REQ-001 extended with runtime clauses naming the three string elicits `tour-step-manifest`, `anchor-selectors` and `per-step-content-voice` and their refusal branches; US-26101 gained three template ACs (AC-26101-5, AC-26101-6, AC-26101-7) each carrying an `Applying agent sets: <elicit-id>.` clause; README, guide and CHANGELOG register scrubbed (no work-item ids). Closes review-fix-pass findings F-3, O-4.
+
+## 1.0.0 (visual round, spec 2026-09-06 section 5.5)
 
 - First shipped version. Introduces the tour step runner (ARIA APG dialog-modal per step, focus lifecycle, `role="dialog"`, `aria-labelledby`, `aria-describedby`, keyboard trap inside the tooltip with Escape as the exit, focus-not-obscured at 1440 and 360 breakpoints via `browser.resize`), the checklist slot (dashboard-top open collapse on `application-dashboard` applied; settings-page closed collapse when not; `<details>` browser-native for keyboard-native keyboard behaviour and screen-reader-native semantics), and the completion-state store contract (three backend shapes selected at apply time from the elicited answer or the Q4 fallback `spa-local-storage` when no persistence blueprint is applied).
 - Ships six elicits: `tour-step-manifest`, `anchor-selectors`, `per-step-content-voice` (all project-owned strings the blueprint contributes the WHAT for), `dismissal-policy` (default `dismiss-permanently`), `completion-state-store` (default `spa-local-storage` per Q4), `checklist-anchor` (default derived at apply time from the applied-blueprint set).
@@ -8,5 +39,5 @@
 - Ships a dependency-free sample-app fixture at `packages/rcf-lite/test/fixtures/probe-pack-application-onboarding-tour/` realising the tour surface honestly across both checklist branches and multiple completion-store shapes, plus four break switches (`?break=no-role`, `?break=focus-escape`, `?break=no-collapse`, `?break=no-persist`) driving the negative runs.
 - Composes on `application-spa` (routing and iconography), `application-dashboard` (dashboard-top anchor slot; settings-page fallback), `application-notifications-in-app` (polite `aria-live` completion announce), `application-account-settings` (restart-tour control home; any settings-shaped surface as fallback), and any `security-auth-*` blueprint (per-principal completion state; per-browser under a bare namespace as fallback).
 - Q4 default: when no persistence blueprint is applied AND the operator does not answer `completion-state-store`, the store defaults to `spa-local-storage`. Rationale in ADR-2702 and the README's Q4 fallback section.
-- Two documented mechanism-reach gaps: `AC-26105-1` first-run detection is fixture-verified via the manual boot line; `AC-26107-1` screen-reader traversal is asserted at the DOM contract level and verified manually via the fixture READMEs VoiceOver smoke. Runner cleanup rides `w-2026-09-04-dave-020`.
+- Two documented mechanism-reach gaps: `AC-26105-1` first-run detection is fixture-verified via the manual boot line; `AC-26107-1` screen-reader traversal is asserted at the DOM contract level and verified manually via the fixture READMEs VoiceOver smoke.
 - No new global topics claimed. Extends the section 5 shelf id band registry with `application-onboarding-tour` at 26101 to 26899 (US) and 27xx (ADR/TAC).

package/blueprints/application-onboarding-tour/README.md

@@ -8,7 +8,7 @@ Vendor-neutral onboarding-tour surface for an rcf-lite application. Composes on
 rcf define blueprint add <path-to>/blueprints/application-onboarding-tour
 ```
 
-No `requiresAppliedCapabilities`: T-5 has no hard dependency, and the compose targets (SPA, dashboard, notifications-in-app, account-settings, any auth) are all optional. Prompts the elicitation phase for six parameters: the step manifest (3 to 5 steps with per-step anchor and content), the anchor selectors, the per-step content voice, the dismissal policy (default `dismiss-permanently`), the completion-state store shape (default `spa-local-storage`, the Q4 fallback), and the checklist anchor slot (default derived at apply time from what is applied). Writes a sidecar `rcf/blueprints/application-onboarding-tour.applied.json` capturing the answered elicits and the discovered `appliedBlueprints[]` (dashboard, notifications-in-app, account-settings, spa presence). Consumes the `logging` and `errorHandling` companions when they resolve to an applied provider or a registered library.
+No `requiresAppliedCapabilities`: the blueprint has no hard dependency, and the compose targets (SPA, dashboard, notifications-in-app, account-settings, any auth) are all optional. The apply step prompts the elicitation phase for six parameters: the step manifest (3 to 5 steps with per-step anchor and content), the anchor selectors, the per-step content voice, the dismissal policy (default `dismiss-permanently`), the completion-state store shape (default `spa-local-storage`, the Q4 fallback), and the checklist anchor slot (default derived at apply time from what is applied). The apply step writes a sidecar `rcf/blueprints/application-onboarding-tour.applied.json` capturing the answered elicits and the discovered `appliedBlueprints[]` (dashboard, notifications-in-app, account-settings, spa presence). Consumes the `logging` and `errorHandling` companions when they resolve to an applied provider or a registered library.
 
 ## Anatomy
 
@@ -48,7 +48,7 @@ Spec `standardsTrace` empty at the blueprint level; each ADR contribution carrie
 ## Known mechanism-reach gaps
 
 - `AC-26105-1` (first-run detection): the runner cannot fully prove the first-run vs returning-principal branch in one browser session without a persisted state seed; the pack drives the first-run branch via `?first-run=1` and the returning branch is verified by the fixture READMEs manual boot line (walk `/tour` twice, confirm the tour auto-opens on run 1 and does not on run 2).
-- `AC-26107-1` (screen-reader traversal): the pack asserts the DOM contract (`aria-labelledby`, `aria-describedby`) but does not drive a real screen reader in CI. The fixture README names the manual VoiceOver smoke. Runner cleanup rides `w-2026-09-04-dave-020`.
+- `AC-26107-1` (screen-reader traversal): the pack asserts the DOM contract (`aria-labelledby`, `aria-describedby`) but does not drive a real screen reader in CI. The fixture README names the manual VoiceOver smoke. Runner cleanup planned for a follow-up minor.
 - `AC-26106-1` (restart-tour clears state and re-opens): fully exercised inside the AC-26104-1 pack check end-to-end (the check clicks restart, then navigates to `/tour` and asserts the tooltip re-appears).
 
 ## Elicited parameters

package/blueprints/application-onboarding-tour/blueprint.json

@@ -1,6 +1,6 @@
 {
   "slug": "application-onboarding-tour",
-  "version": "1.0.0",
+  "version": "1.1.2",
   "category": "application",
   "elicits": [
     {
@@ -86,6 +86,16 @@
       "kind": "req",
       "path": "requirements/application-onboarding-tour-req-004.json"
     },
+    {
+      "id": "application-onboarding-tour-REQ-005",
+      "kind": "req",
+      "path": "requirements/application-onboarding-tour-req-005.json"
+    },
+    {
+      "id": "application-onboarding-tour-REQ-006",
+      "kind": "req",
+      "path": "requirements/application-onboarding-tour-req-006.json"
+    },
     {
       "id": "application-onboarding-tour-US-26101",
       "kind": "us",
@@ -121,6 +131,16 @@
       "kind": "us",
       "path": "user-stories/application-onboarding-tour-us-26107.json"
     },
+    {
+      "id": "application-onboarding-tour-US-26108",
+      "kind": "us",
+      "path": "user-stories/application-onboarding-tour-us-26108.json"
+    },
+    {
+      "id": "application-onboarding-tour-US-26109",
+      "kind": "us",
+      "path": "user-stories/application-onboarding-tour-us-26109.json"
+    },
     {
       "id": "TAC-2701-application-onboarding-tour-step-runner",
       "kind": "tac",
@@ -161,4 +181,4 @@
       "standardsTraceClause": "generic enterprise practice"
     }
   ]
-}
+}

package/blueprints/application-onboarding-tour/contributions/adrs/adr-2702-application-onboarding-tour-completion-store-shape.json

@@ -2,12 +2,12 @@
   "adrId": "ADR-2702-application-onboarding-tour-completion-store-shape",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "accepted",
   "title": "Completion-state store shape: spa-local-storage default (Q4 fallback), spa-session-storage or server-side-per-principal",
   "context": "The completion state needs a store. Three shapes are legal. spa-local-storage keeps the completion state per browser and per principal identifier; a returning principal on the same browser is not re-onboarded, and a different browser (or a private window) is re-onboarded. spa-session-storage keeps the completion state per session and re-plays the tour on every new session; useful only for a project that deliberately wants a per-session refresher. server-side-per-principal keeps the completion state on the principals record so it follows the user across devices; requires an applied persistence blueprint and the projects own writer adapter. The spec section 5.5 and section 10 Q4 ratify spa-local-storage as the fallback when no persistence blueprint is applied because a per-session tour that re-plays on every new session is worse than a one-time tour that persists across sessions on that browser.",
-  "decision": "completion-state-store is elicited (enum: spa-local-storage | spa-session-storage | server-side-per-principal). Recommended default: spa-local-storage. At apply time the elicit surface offers all three; a project that answers server-side-per-principal without an applied persistence blueprint hits a documented refusal (the elicit's when predicate refuses per the mechanism minor T-5 does not extend; the refusal is enforced at the surface load by TAC-2703 which refuses to construct a server-side backend without a resolved persistence adapter and falls back to spa-local-storage with a documented note on the sidecar).",
-  "consequences": "A project with no persistence blueprint applied gets the spa-local-storage backend automatically per the Q4 fallback; a project with a persistence blueprint and the server-side-per-principal answer gets a cross-device tour completion; a project answering spa-session-storage accepts a per-session re-onboarding. The dismiss-until-next-major and dismiss-until-next-minor policies (ADR-2701) still work under any of the three shapes because the CompletionRecord.blueprintSetVersion travels with the record.",
+  "decision": "completion-state-store is elicited (enum: spa-local-storage | spa-session-storage | server-side-per-principal). Recommended default: spa-local-storage. A project that answers server-side-per-principal without an applied persistence blueprint hits a hard refusal (error class COMPLETION_STORE_MISSING_PROVIDER) at surface load; TAC-2703 refuses to construct a server-side backend and does not fall back to any other store. spa-local-storage and spa-session-storage need no persistence blueprint and construct their backend directly.",
+  "consequences": "A project with no persistence blueprint applied that answers spa-local-storage or spa-session-storage gets that backend directly; a project answering server-side-per-principal without a persistence blueprint hits COMPLETION_STORE_MISSING_PROVIDER and does not silently downgrade. The dismiss-until-next-major and dismiss-until-next-minor policies (ADR-2701) still work under any of the three shapes because the CompletionRecord.blueprintSetVersion travels with the record.",
   "alternativesConsidered": [
     {
       "name": "Alternative approach considered",
@@ -16,5 +16,5 @@
     }
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-001.json

@@ -2,7 +2,11 @@
   "reqId": "application-onboarding-tour-REQ-001",
   "prdId": "PRD-001",
   "title": "Step-manifest contract: 3 to 5 steps per tour with per-step anchor selector and per-step content voice slot",
-  "description": "The blueprint contributes a step-manifest contract for a 3 to 5 step onboarding tour. Each step declares a step id, an anchor selector (CSS resolved at step-open time to place the tooltip against a live element in the DOM), a heading and a body slot the project fills with its own voice. The step runner walks the manifest in order and refuses to open a step whose anchor does not resolve to a visible element rather than rendering a floating tooltip. The blueprint contributes the WHAT (the manifest shape and the resolver contract), not the words.",
+  "description": "The blueprint contributes a step-manifest contract for a 3 to 5 step onboarding tour. Each step declares a step id, an anchor selector (CSS resolved at step-open time to place the tooltip against a live element in the DOM), a heading and a body slot the project fills with its own voice. The step runner walks the manifest in order and refuses to open a step whose anchor does not resolve to a visible element rather than rendering a floating tooltip. The blueprint contributes the WHAT (the manifest shape and the resolver contract), not the words. The three string elicits carry a runtime clause each: `tour-step-manifest` is the ordered 3 to 5 entry list the runner walks (a count below 3 or above 5 refuses at apply with STEP_MANIFEST_OUT_OF_RANGE); `anchor-selectors` supplies the per-step CSS selector the runner passes to document.querySelector at step-open time and refuses the step render when the selector resolves to no element or to a clipped element; `per-step-content-voice` supplies the heading and body strings the tooltip surfaces verbatim (blank strings refuse at apply with STEP_CONTENT_MISSING naming the step id).",
+  "deliveredBy": {
+    "tacId": "TAC-2701-application-onboarding-tour-step-runner",
+    "field": "interfaces.renderTourRunner"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
@@ -14,5 +18,5 @@
   "version": "1.0.0",
   "status": "approved",
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-002.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Tooltip-as-dialog contract per the ARIA APG dialog-modal pattern",
   "description": "Each step's tooltip carries role=\"dialog\", aria-labelledby to the step heading, aria-describedby to the step body. Focus moves to the tooltip on open, focus returns to the anchor on close. The dialog traps focus between the tour controls (previous, next, dismiss) and refuses to let Tab escape to the underlying surface (WCAG 2.1.2 No Keyboard Trap satisfied because Escape always exits). Escape dismisses the tour. Focus is not obscured on any breakpoint (WCAG 2.4.11 Focus Not Obscured Minimum). Follows the ARIA APG dialog-modal pattern for the tooltip surface.",
+  "deliveredBy": {
+    "tacId": "TAC-2701-application-onboarding-tour-step-runner",
+    "field": "interfaces.renderTourRunner"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",
@@ -11,8 +15,8 @@
     "blueprint:application-onboarding-tour",
     "category:02-dialog-modal"
   ],
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-003.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Checklist surface: on the dashboard when application-dashboard is applied, on the settings page when not",
   "description": "A first-run checklist renders on the dashboard-top anchor when application-dashboard is applied (open by default, so a new principal sees the outstanding items at a glance) and collapses to a settings-page anchor when application-dashboard is not applied (closed by default, so an existing principal reaching the settings surface can expand it). The collapse contract is a <details> element whose open state mirrors the anchor choice: dashboard-top -> open, settings-page -> closed. The checklist enumerates the applied tour surfaces with a link back to the restart-tour affordance on the settings surface. The blueprint contributes the anchor slot contract (ADR-2703) and the surface conditionality, not the checklist items.",
+  "deliveredBy": {
+    "tacId": "TAC-2702-application-onboarding-tour-checklist-slot",
+    "field": "responsibilities.resolveAnchor"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-004.json

@@ -3,6 +3,10 @@
   "prdId": "PRD-001",
   "title": "Completion-state persistence per principal in the applied persistence blueprint with an spa-local-storage fallback per Q4",
   "description": "The completion state persists per principal in the applied persistence blueprint (server-side-per-principal when a persistence blueprint is applied and the operator picks that store) or per browser in spa-local-storage as the Q4 fallback when no persistence blueprint is applied. spa-session-storage is a third option the operator can pick when a per-session tour is deliberately wanted. A restart-tour control renders on the settings surface (composing on application-account-settings when applied; on any settings-shaped surface as a fallback) and clears the completion state so the tour re-opens on the next principal load.",
+  "deliveredBy": {
+    "tacId": "TAC-2703-application-onboarding-tour-completion-store",
+    "field": "interfaces.completionStore"
+  },
   "category": "functional",
   "domain": "application",
   "priority": "must",

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-005.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "application-onboarding-tour-REQ-005",
+  "prdId": "PRD-001",
+  "title": "Dismissal policy: dismiss-permanently, dismiss-until-next-major and dismiss-until-next-minor each have a defined runtime clause",
+  "description": "The completion store honours the elicited dismissal-policy with a runtime clause per option. `dismiss-permanently` writes a terminal completion record and refuses re-surfacing regardless of any subsequent version bump: a principal who dismisses the tour never sees it again until the restart-tour control fires. `dismiss-until-next-major` writes a completion record carrying the current tour version and compares stored and current versions on the major segment on principal load: the tour re-surfaces when the majors differ, otherwise it stays dismissed. `dismiss-until-next-minor` writes a completion record carrying the current tour version and re-surfaces the tour when either the major or the minor segment differs on principal load. The record shape is identical across the three policies; only the comparison on load differs.",
+  "deliveredBy": {
+    "tacId": "TAC-2703-application-onboarding-tour-completion-store",
+    "field": "interfaces.completionStore"
+  },
+  "category": "functional",
+  "domain": "onboarding",
+  "priority": "must",
+  "rationale": "The elicit offers three dismissal policies but no requirement described what each option does. A principal on a project that chose `dismiss-until-next-major` inherited `dismiss-permanently` behaviour silently. Requiring a per-option clause turns the elicit into a chain-linked behaviour the completion store's read on load proves.",
+  "tags": [
+    "blueprint:application-onboarding-tour",
+    "category:05-dismissal-policy"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-10T00:00:00Z",
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-onboarding-tour/contributions/requirements/application-onboarding-tour-req-006.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "application-onboarding-tour-REQ-006",
+  "prdId": "PRD-001",
+  "title": "Checklist anchor: dashboard-top, settings-page and custom-anchor each resolve to a rendered slot or a defined fallback",
+  "description": "The checklist slot honours the elicited checklist-anchor with a runtime clause per option. `dashboard-top` mounts the checklist at the top of the dashboard route provided by application-dashboard and refuses the mount (a WCAG 3.3.1 refusal announced on the settings surface) when application-dashboard is not applied. `settings-page` mounts the checklist at the settings route provided by application-account-settings and behaves as `dashboard-top` regarding refusal when the settings surface is unavailable. `custom-anchor` resolves an elicited CSS selector against the live DOM at load: on resolution the checklist mounts inside the resolved element with a default collapsed state (a <details> element with data-role=onboarding-tour-checklist and open=false); when the selector resolves to nothing or to an invisible or clipped element, the checklist mounts at the settings route as a fallback and the console log carries data-error=CHECKLIST_ANCHOR_UNRESOLVED naming the selector. In every branch, the checklist suppresses entirely when neither the dashboard nor the settings surface is applied and no usable custom anchor is set.",
+  "deliveredBy": {
+    "tacId": "TAC-2702-application-onboarding-tour-checklist-slot",
+    "field": "responsibilities.resolveAnchor"
+  },
+  "category": "functional",
+  "domain": "onboarding",
+  "priority": "must",
+  "rationale": "The elicit offers three checklist anchors but the shipped requirement covered dashboard-top and settings-page only. A project that chose custom-anchor inherited unspecified behaviour: no requirement described the default collapse state or what happens when the selector resolves to nothing. Requiring a per-option clause makes the fallback and the refusal observable.",
+  "tags": [
+    "blueprint:application-onboarding-tour",
+    "category:06-checklist-anchor"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-10T00:00:00Z",
+  "updatedAt": "2026-09-10T00:00:00Z"
+}

package/blueprints/application-onboarding-tour/contributions/tacs/tac-2702-application-onboarding-tour-checklist-slot.json

@@ -10,7 +10,8 @@
     "Read the elicited checklist-anchor (ADR-2703) at load and mount the checklist at the resolved slot (AC-26103-1).",
     "Render the checklist as a <details> element carrying data-role=\"onboarding-tour-checklist\" whose open state mirrors the anchor: open on dashboard-top, closed on settings-page (AC-26103-1).",
     "Enumerate the applied tour surfaces as list items with a link to the restart-tour control on the settings surface.",
-    "Suppress the checklist entirely when neither the dashboard nor the settings surface is applied and no custom-anchor is supplied."
+    "Suppress the checklist entirely when neither the dashboard nor the settings surface is applied and no custom-anchor is supplied.",
+    "resolveAnchor: resolve the elicited checklist-anchor (dashboard-top, settings-page or custom-anchor) to a mounted <details> slot, or fall back to the settings surface with data-error=CHECKLIST_ANCHOR_UNRESOLVED (AC-26109-1 through AC-26109-5)."
   ],
   "internalStructure": "One checklist module that reads the applied capability set from the sidecar-adjacent applied-blueprint list, picks the anchor per the elicited value or the default derived at apply time, and mounts the <details> element into the resolved slot. The framework is not prescribed.",
   "interfaces": [

package/blueprints/application-onboarding-tour/contributions/tacs/tac-2703-application-onboarding-tour-completion-store.json

@@ -2,17 +2,17 @@
   "tacId": "TAC-2703-application-onboarding-tour-completion-store",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "status": "approved",
   "name": "Onboarding-tour completion-state store",
-  "purpose": "Owns the completion-state store contract: the writer the step runner calls on the last step, the reader first-run detection calls on principal load, and the clearer the restart-tour control calls. Delegates to the applied persistence blueprint when server-side-per-principal is elicited (and refuses at apply if no persistence blueprint is applied); falls back to spa-local-storage per Q4 or spa-session-storage per the elicit.",
+  "purpose": "Owns the completion-state store contract: the writer the step runner calls on the last step, the reader first-run detection calls on principal load, and the clearer the restart-tour control calls. The refusal semantics for the server-side-per-principal backend without an applied persistence blueprint are owned by `ADR-2702.decision`.",
   "responsibilities": [
     "Write the completion record on the last step (AC-26104-1).",
     "Read the completion record on principal load so first-run detection can gate the tour auto-open (AC-26105-1).",
     "Clear the completion record when the restart-tour control fires (AC-26104-1, AC-26106-1).",
-    "Refuse at apply when server-side-per-principal is elicited without an applied persistence blueprint."
+    "Enforce the refusal semantics owned by `ADR-2702.decision`."
   ],
-  "internalStructure": "One completion-store module with three backends (spa-local-storage, spa-session-storage, server-side-per-principal) selected at apply time from the elicited completion-state-store answer or the Q4 fallback (spa-local-storage). The server-side backend calls the applied persistence blueprint's writer through the projects own adapter interface; the two SPA backends read and write window.localStorage / window.sessionStorage under a namespaced key derived from the applied blueprint set version.",
+  "internalStructure": "One completion-store module with three backends (selected at apply time from the elicited `blueprint.json.elicits[id=completion-state-store]` answer). The server-side backend calls the applied persistence blueprint's writer through the projects own adapter interface; the missing-provider refusal semantics for that branch are owned by `ADR-2702.decision`. The SPA backends read and write from the browser storage the elicit selects under a namespaced key derived from the applied blueprint set version.",
   "interfaces": [
     {
       "name": "completionStore",
@@ -27,8 +27,8 @@
       "description": "Optional composition: only the server-side-per-principal backend delegates to an applied persistence blueprint writer. spa-local-storage and spa-session-storage need no persistence blueprint. The rcf-schemas 0.6.1 TAC dependency kind enum is limited to tac and external, so the composition-optional relation is recorded as external and made explicit in the description and notes."
     }
   ],
-  "tradeoffs": "spa-local-storage is chosen as the Q4 default because a per-session tour that re-plays on every new session is worse than a one-time tour that persists across sessions on that browser; spa-session-storage remains an option for a project that deliberately wants a per-session tour. server-side-per-principal is chosen when the tour completion is a real profile fact (a cross-device onboarding) rather than a per-browser convenience.",
-  "notes": "The blueprintSetVersion in the CompletionRecord is what lets ADR-2701's dismiss-until-next-major and dismiss-until-next-minor policies re-open the tour on the right bump. Known mechanism-reach gap: the server-side-per-principal backend cannot prove a round-trip in a unit test without an applied persistence blueprint; the pack skips the persistence round-trip check for spa-* stores (inspects the storage directly) and drives it for server-side-per-principal on the fixture branch that stands up an in-fixture writer. The Persistence blueprint dependency is recorded with kind external per the rcf-schemas 0.6.1 enum and is optional-composition semantically: server-side-per-principal delegates to the applied persistence blueprint writer, and the spa-local-storage and spa-session-storage backends need no persistence blueprint applied. Refusal at apply for the server-side-per-principal branch is enforced in the store module.",
+  "tradeoffs": "The three-backend choice and the default selection are owned by `ADR-2702.decision` and the manifest elicit `blueprint.json.elicits[id=completion-state-store]`; this TAC carries only the store contract, not the option-level rationale.",
+  "notes": "The blueprintSetVersion in the CompletionRecord is what lets ADR-2701's dismiss-until-next-major and dismiss-until-next-minor policies re-open the tour on the right bump. Known mechanism-reach gap: the server-side-per-principal backend cannot prove a round-trip in a unit test without an applied persistence blueprint; the pack skips the persistence round-trip check for the SPA stores (inspects the storage directly) and drives it for the server-side backend on the fixture branch that stands up an in-fixture writer. The Persistence blueprint dependency is recorded with kind external per the rcf-schemas 0.6.1 enum and is optional-composition semantically. The refusal path is enforced per `ADR-2702.decision`.",
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-07T00:45:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/user-stories/application-onboarding-tour-us-26101.json

@@ -13,7 +13,72 @@
       "id": "AC-26101-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given a first-run principal on the SPA, the tour opens on the highest-value surface with the first step; Escape dismisses the tour and hides the tooltip; keyboard-only users reach every tour control (previous, next, dismiss) via Tab in DOM order and activate the next control with Enter (WCAG 2.1.1 Keyboard, WCAG 2.1.2 No Keyboard Trap, WCAG 2.4.3 Focus Order). Anchors to TAC-2701-application-onboarding-tour-step-runner; probed by application-onboarding-tour.pack.mjs check AC-26101-1."
+      "description": "Given a first-run principal on the SPA, the tour opens on the highest-value surface with the first step; Escape dismisses the tour and hides the tooltip; keyboard-only users reach every tour control (previous, next, dismiss) via Tab in DOM order and activate the next control with Enter (WCAG 2.1.1 Keyboard, WCAG 2.1.2 No Keyboard Trap, WCAG 2.4.3 Focus Order). Anchors to TAC-2701-application-onboarding-tour-step-runner; probed by application-onboarding-tour.pack.mjs check AC-26101-1. (WCAG 2.1.2 verified against https://www.w3.org/TR/WCAG22/#no-keyboard-trap and WCAG 2.4.3 verified against https://www.w3.org/TR/WCAG22/#focus-order, 2026-09-10.)",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/TR/WCAG22/#keyboard",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-26101-2",
+      "description": "When the current step's anchor selector resolves to nothing at open, the runner refuses the step render, focus stays on the last known anchor (or on the tour launcher for the first step), and the console log carries data-error=TOUR_ANCHOR_UNRESOLVED naming the selector; no floating dialog surfaces.",
+      "given": "the current step has an anchor that resolves to no element",
+      "when": "the runner attempts to open the step",
+      "then": "the step is skipped or the tour is closed with a defined error, no floating dialog appears, and data-error=TOUR_ANCHOR_UNRESOLVED is logged",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26101-3",
+      "description": "When the current step's anchor resolves to an invisible or clipped element that cannot fit the tooltip at the current breakpoint, the runner refuses the render and emits data-error=TOUR_ANCHOR_UNFIT; the dialog never renders floating or off-screen.",
+      "given": "the current step's anchor is present but hidden or clipped for the current viewport",
+      "when": "the runner attempts to open the step",
+      "then": "no tooltip renders, data-error=TOUR_ANCHOR_UNFIT is logged with the anchor and breakpoint, and the tour offers the next step or a defined close",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26101-4",
+      "description": "The tour opens on the highest-value surface as named by the elicited step manifest (the first step's anchor selector determines the surface); a manifest with fewer than 3 steps or more than 5 refuses at apply with STEP_MANIFEST_OUT_OF_RANGE naming the count.",
+      "given": "a project applying application-onboarding-tour",
+      "when": "apply runs against a step manifest with an out-of-range count",
+      "then": "apply exits with a non-zero code and STEP_MANIFEST_OUT_OF_RANGE names the count and the required range",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26101-5",
+      "description": "The elicited `tour-step-manifest` value is the ordered step list the runner walks; each entry names a step id, an anchor selector, a heading and a body. A manifest with fewer than 3 or more than 5 entries refuses at apply with STEP_MANIFEST_OUT_OF_RANGE naming the count. Applying agent sets: tour-step-manifest.",
+      "given": "a project applying application-onboarding-tour with a tour-step-manifest of N entries",
+      "when": "apply runs",
+      "then": "apply exits 0 with 3<=N<=5 and refuses with STEP_MANIFEST_OUT_OF_RANGE otherwise, naming N and the required range",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-26101-6",
+      "description": "The elicited `anchor-selectors` value supplies the per-step CSS selector the runner passes to document.querySelector at step-open time; a step whose selector resolves to no element or to a clipped element refuses the render with data-error=TOUR_ANCHOR_UNRESOLVED or TOUR_ANCHOR_UNFIT respectively (see AC-26101-2 and AC-26101-3). Applying agent sets: anchor-selectors.",
+      "given": "a project applying application-onboarding-tour with anchor-selectors set per manifest step",
+      "when": "the runner opens a step",
+      "then": "the runner queries the DOM with the elicited selector for that step and refuses the render with the named data-error when the selector does not resolve to a visible unclipped element",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-26101-7",
+      "description": "The elicited `per-step-content-voice` value supplies the heading and body strings the tooltip surfaces verbatim for each step; a step whose heading or body resolves to an empty string refuses at apply with STEP_CONTENT_MISSING naming the step id. Applying agent sets: per-step-content-voice.",
+      "given": "a project applying application-onboarding-tour with per-step-content-voice set for each manifest step",
+      "when": "apply runs",
+      "then": "apply refuses with STEP_CONTENT_MISSING naming the offending step id when any heading or body is empty, and exits 0 with the strings surfaced verbatim in the tooltip DOM at runtime otherwise",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template"
     }
   ],
   "tacIds": [
@@ -23,5 +88,5 @@
     "blueprint:application-onboarding-tour"
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/user-stories/application-onboarding-tour-us-26102.json

@@ -13,7 +13,40 @@
       "id": "AC-26102-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given a step showing a tooltip anchored to a UI element, focus moves to the tooltip on open; the tooltip carries role=\"dialog\" with aria-labelledby pointing at the step heading; focus returns to the anchor on close (Escape or the dismiss control) per the ARIA APG dialog-modal pattern; focus is not obscured on the 1440 wide breakpoint or the 360 narrow breakpoint (WCAG 2.4.11 Focus Not Obscured Minimum). Anchors to TAC-2701-application-onboarding-tour-step-runner; probed by application-onboarding-tour.pack.mjs check AC-26102-1."
+      "description": "Given a step showing a tooltip anchored to a UI element, focus moves to the tooltip on open; the tooltip carries role=\"dialog\" with aria-labelledby pointing at the step heading; focus returns to the anchor on close (Escape or the dismiss control) per the ARIA APG dialog-modal pattern; focus is not obscured on the 1440 wide breakpoint or the 360 narrow breakpoint (WCAG 2.4.11 Focus Not Obscured Minimum). Anchors to TAC-2701-application-onboarding-tour-step-runner; probed by application-onboarding-tour.pack.mjs check AC-26102-1. (WCAG 2.4.11 verified against https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum, 2026-09-10.)",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-26102-2",
+      "description": "The tooltip carries role=\"dialog\", aria-modal=\"true\" and aria-labelledby resolving to the step heading id (WCAG 1.3.1 and 4.1.2 via the ARIA APG dialog-modal pattern).",
+      "given": "a tour step opens",
+      "when": "the DOM is inspected",
+      "then": "the tooltip element carries role=\"dialog\", aria-modal=\"true\" and aria-labelledby resolving to a heading id present in the tooltip",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/",
+        "verifiedOn": "2026-09-10"
+      }
+    },
+    {
+      "id": "AC-26102-3",
+      "description": "Focus is trapped between the tour controls (previous, next, dismiss) while the dialog is open; Tab from the last control returns to the first, Shift+Tab from the first goes to the last, and Escape closes the dialog and returns focus to the anchor.",
+      "given": "a tour step is open",
+      "when": "the keyboard walks Tab / Shift+Tab / Escape",
+      "then": "focus stays within the tour controls until Escape or dismiss fires, then returns to the anchor",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "vendorCitation": {
+        "url": "https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/",
+        "verifiedOn": "2026-09-10"
+      }
     }
   ],
   "tacIds": [
@@ -23,5 +56,5 @@
     "blueprint:application-onboarding-tour"
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/user-stories/application-onboarding-tour-us-26103.json

@@ -13,7 +13,18 @@
       "id": "AC-26103-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given the applied capability set includes application-dashboard, the checklist renders inside a <details open> element on the dashboard-top anchor slot; given the applied capability set does NOT include application-dashboard, the checklist renders inside a <details> (closed) element on the settings-page anchor slot; the <details> element carries data-role=\"onboarding-tour-checklist\" in both branches. Anchors to TAC-2702-application-onboarding-tour-checklist-slot; probed by application-onboarding-tour.pack.mjs check AC-26103-1 on both application-dashboard and settings-page branches."
+      "description": "Given the applied capability set includes application-dashboard, the checklist renders inside a <details open> element on the dashboard-top anchor slot; given the applied capability set does NOT include application-dashboard, the checklist renders inside a <details> (closed) element on the settings-page anchor slot; the <details> element carries data-role=\"onboarding-tour-checklist\" in both branches. Anchors to TAC-2702-application-onboarding-tour-checklist-slot; probed by application-onboarding-tour.pack.mjs check AC-26103-1 on both application-dashboard and settings-page branches.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26103-2",
+      "description": "When application-dashboard is not applied, the checklist mounts on the settings route rather than falling through to nothing.",
+      "given": "application-dashboard is not applied",
+      "when": "the settings route renders",
+      "then": "the checklist appears on the settings route with data-role=onboarding-tour-checklist",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -23,5 +34,5 @@
     "blueprint:application-onboarding-tour"
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/user-stories/application-onboarding-tour-us-26104.json

@@ -13,7 +13,38 @@
       "id": "AC-26104-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given a completed tour, the completion state persists per principal in the applied persistence blueprint (or in spa-local-storage as the Q4 fallback per ADR-2702 when no persistence blueprint is applied); a restart-tour control is reachable from the settings surface (composing on application-account-settings when applied; on any settings surface as a fallback); activating the control clears the completion state and re-opens the tour on the next principal load. Anchors to TAC-2703-application-onboarding-tour-completion-store; probed by application-onboarding-tour.pack.mjs check AC-26104-1."
+      "description": "Given a completed tour, the completion state persists per principal in the applied persistence blueprint (or in spa-local-storage as the Q4 fallback per ADR-2702 when no persistence blueprint is applied); a restart-tour control is reachable from the settings surface (composing on application-account-settings when applied; on any settings surface as a fallback); activating the control clears the completion state and re-opens the tour on the next principal load. Anchors to TAC-2703-application-onboarding-tour-completion-store; probed by application-onboarding-tour.pack.mjs check AC-26104-1.",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26104-2",
+      "description": "When completion-state-store is `server-side-per-principal` and no persistence blueprint is applied, apply refuses with COMPLETION_STORE_MISSING_PROVIDER naming the required capability and no completion record is written.",
+      "given": "completion-state-store=server-side-per-principal with no persistence blueprint applied",
+      "when": "apply runs",
+      "then": "apply exits with a non-zero code, COMPLETION_STORE_MISSING_PROVIDER is emitted and no completion record is written to any store",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26104-3",
+      "description": "When the write of the completion record fails (a rejected persistence write or a full quota on spa-local-storage), the tour does not mark itself completed: the last step remains active or the dialog closes with data-error=COMPLETION_WRITE_FAILED, and the next principal load re-opens the tour.",
+      "given": "a tour completing while the store rejects the write",
+      "when": "the last step confirm fires",
+      "then": "no completed-success announcement is emitted, data-error=COMPLETION_WRITE_FAILED is logged, and a subsequent principal load re-opens the tour",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26104-4",
+      "description": "When the read of the completion record fails on principal load (an unreachable persistence backend or a corrupted spa-local-storage entry), the tour defaults to first-run behaviour and the console log carries data-error=COMPLETION_READ_FAILED; the tour never claims dismissed status on an unreadable record.",
+      "given": "a store that raises on read at principal load",
+      "when": "the principal loads",
+      "then": "the tour surfaces as first-run and data-error=COMPLETION_READ_FAILED is logged with the store kind",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -23,5 +54,5 @@
     "blueprint:application-onboarding-tour"
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }

package/blueprints/application-onboarding-tour/contributions/user-stories/application-onboarding-tour-us-26105.json

@@ -13,7 +13,18 @@
       "id": "AC-26105-1",
       "testable": true,
       "scope": "runtime",
-      "description": "Given a principal whose completion-state store contains no completion record for the applied blueprint set version, the tour auto-opens on the highest-value surface; given a principal whose completion-state store contains a completion record for the applied blueprint set version, the tour does NOT auto-open and only the checklist and the restart-tour control render. The check is documented as a mechanism-reach gap in the README (not directly probed at runtime; enforced by the fixture branch under manual boot for the gate reviewer)."
+      "description": "Given a principal whose completion-state store contains no completion record for the applied blueprint set version, the tour auto-opens on the highest-value surface; given a principal whose completion-state store contains a completion record for the applied blueprint set version, the tour does NOT auto-open and only the checklist and the restart-tour control render. The check is documented as a mechanism-reach gap in the README (not directly probed at runtime; enforced by the fixture branch under manual boot for the gate reviewer).",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-26105-2",
+      "description": "A completion record with an unknown or unparseable tourVersion is treated as absent: the tour surfaces as first-run and the console log carries data-error=COMPLETION_RECORD_UNPARSEABLE naming the record id; no false dismissal is inherited.",
+      "given": "a completion record whose tourVersion cannot be parsed",
+      "when": "the principal loads",
+      "then": "the tour opens as first-run and data-error=COMPLETION_RECORD_UNPARSEABLE is logged",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed"
     }
   ],
   "tacIds": [
@@ -23,5 +34,5 @@
     "blueprint:application-onboarding-tour"
   ],
   "createdAt": "2026-09-06T23:15:00Z",
-  "updatedAt": "2026-09-06T23:15:00Z"
+  "updatedAt": "2026-09-10T00:00:00Z"
 }