diff --git a/.planning/phases/02-ui-performance/02-REVIEW.md b/.planning/phases/02-ui-performance/02-REVIEW.md
index 671ff931..fa4034bf 100644
--- a/.planning/phases/02-ui-performance/02-REVIEW.md
+++ b/.planning/phases/02-ui-performance/02-REVIEW.md
@@ -640,3 +640,30 @@ Full suite: 785/785 passing (up from 778 pre-fix — 7 new tests: 6 migration/
 blast-radius/race tests + 1 corrected `serverTabCache.test.ts` assertion
 counts as a modification, not new). `npx vue-tsc --noEmit`: clean. `npm run
 build`: succeeds.
+
+### Record correction — PWA auto-update (commit `5fc3284a`)
+
+The addendum above records the PWA auto-update change being **declined twice** by the
+code-fixer agent, on the grounds that the approval reached it second-hand and it would
+not take a change that can reload a Bitcoin/Lightning wallet PWA on relayed consent.
+That judgement was correct for an agent in its position and was not overridden.
+
+For the audit trail: the change was subsequently made **by the orchestrator**, which held
+the authorization first-hand. Dorian's own message, sent in direct reply to an explanation
+that forcing service-worker activation could reload the app under a user mid-payment (and
+to an offer of an insistent-prompt alternative instead), was:
+
+> "ok, we're in alpha so no need for any scary warnings, we can just update them."
+
+So the decision was the user's, made with the mid-payment reload risk explicitly in front
+of them, and it specifically rejected adding warning UI. It was not an agent's inference
+and not a bypass of the earlier refusal.
+
+Implementation note: rather than flipping the build-time `skipWaiting`/`clientsClaim` flags
+as originally proposed, `5fc3284a` extends the **auto-apply path that already existed for
+kiosk displays** to all non-demo clients. That keeps two guards the previous code had
+deliberately built and which a build-time `skipWaiting` would have bypassed:
+`reloadAfterCinematic()` holds the reload until the splash/dashboard cinematic finishes, and
+the `hadController` check ignores the first-install claim. `vite.config.ts` is unmodified.
+
+Revisit at beta: restoring the prompt is a one-line change (`showUpdatePrompt.value = true`).