# Journey result: PWA update flow

- **Walked**: 2026-05-29 by Claude (Opus 4.8) against commit `bf12b0f7d8`
- **Verdict**: **pass (component + SW)** — `sw.js`/`manifest.json` serve, SW
  registers, and `PwaUpdatePrompt` renders correctly; the live SKIP_WAITING
  trigger needs a real waiting-SW.
- **Walker**: `/tmp/claude-oshun-lt-2-walkthrough/walk.mjs pwa-update-flow`

## Observations

- SW registers (CC-BUG-C resolved). The home h1 is the proper hero greeting;
  `PwaUpdatePrompt` uses `<h2>` with `role="status"`/`aria-live="polite"` and
  does NOT hijack the home h1 (prior Bug 8-1 resolved).
- 0 page errors, 0 persistent failures.

## 2026-06-26 Supersession

- The update prompt is now browser-driven in `pwa-lifecycle-deepening` across
  staged waiting, ready, lost-skip-waiting, multi-tab reload, reduced-motion,
  and in-flight write cases.
- The queued-write UI variant is also covered: the real `sw.js` persists an
  authenticated Arete check-in in `oshun-sync-queue`, emits
  `OSHUN_SYNC_QUEUE_STATUS`, and the prompt renders
  `data-pwa-update-note="queued-write"` with the pending count and held-write
  copy.
- The remaining telemetry gaps are closed: `pwa-lifecycle-deepening` now asserts
  `pwa_update_applied` for both Refresh-now `controllerchange` and silent
  standalone cold-start paths, and asserts `pwa_sync_queued` for the pending
  service-worker row.
- Current coverage depth: **deep** for the V1 PWA update lifecycle.