docs: note deploy-not-live follow-up for 2026-08-18 UX fixes (force webhook re-trigger)

docs/engineering-log/2026-08-18-live-qa-ux-fixes.md

@@ -71,3 +71,14 @@ User tested the hardest-tier personas and reported three UX bugs from a live scr
 - Sessions the customer has not decided on stay `active` and are resumable (per existing
   resume-without-re-pick behavior); they only close when a decision is reached.
 - Deploy remains the repo's normal Gitea→EasyPanel webhook path (≈3 min rebuild) — operator runs it.
+
+## Deployment follow-up (same day)
+
+After the commit+push (`ffb7cdd`), a live check showed the deployed site still served the **old**
+bundle: the frontend `index-*.js` hash was unchanged and still contained the OLD guide text
+("พอใจแล้วกด \"สรุปผล\"") and the old finish button, with none of the new strings. The Gitea→EasyPanel
+deploy webhook (hook id 3, `active:true`, push event) is configured, but the push did **not** propagate
+within ~10+ min. The exact reported leak payload was re-run through the NEW parser and extracts a clean
+reply (no leak), so the code fix is correct — the leak seen was the stale deploy. Action: force a
+redeploy (re-push to re-trigger the webhook, or redeploy from the EasyPanel console) and re-verify the
+live bundle contains the new auto-close guide text.