From f9e204c301c6789718553c0cd10cd59ef315792c Mon Sep 17 00:00:00 2001
From: Quintine <15965533+Quintine@users.noreply.github.com>
Date: Sat, 24 Oct 2026 12:54:57 +1100
Subject: [PATCH] Verify persistent notices and record the deployed version gap

---
 docs/CURRENT_STATUS.md   | 19 +++++++++++++++++++
 docs/READABLE_NOTICES.md | 20 ++++++++++++++++++++
 2 files changed, 39 insertions(+)

diff --git a/docs/CURRENT_STATUS.md b/docs/CURRENT_STATUS.md
index d2088aa1..fd7cb74a 100644
--- a/docs/CURRENT_STATUS.md
+++ b/docs/CURRENT_STATUS.md
@@ -16,6 +16,25 @@ open mode gates.
 
 
 ## Current checkpoint and work
+**Readable notices — 24 October follow-up.** Current source already keeps room
+and seat confirmations/action notices until Continue, and toasts until Dismiss.
+The new local create check retained its confirmation for 30 seconds through
+polling and a lobby action; Continue left the room intact. Focused tests pass
+23/23 and the bounded source audit found no remaining automatic text dismissal.
+The live site still reports older revision `716304b`; the fix is pushed but
+awaits deployment. [Exact evidence and limits](READABLE_NOTICES.md#verification).
+
+**Queued next — Tleilaxu income from Ambassador revivals, 24 October.** Connect
+positive free force/leader returns to the existing per-beneficiary/turn free
+income ledger under the explicit provisional interpretation. Decline earns0;
+Ghola stays independent. A committed-return receipt and distinct revival marker
+bind the native income response so allow/cancel resumes the original Ambassador
+once without repeating the revival. Root owns engine, response-context, controls,
+regressions and docs/reference; proposed disjoint lanes own only a pure receipt
+helper/test and original-action source fixture. The source review is complete;
+implementation was deferred for the user's notice report. No new module or
+assurance campaign.
+
 **Ecaz's Ambassador Duke revival — 24 October. Prototyped / Partial.** The
 original Tleilaxu grant now offers Ecaz the real shared dead Duke, including his
 existing independent death histories. Native and BG-copy effects use canonical
diff --git a/docs/READABLE_NOTICES.md b/docs/READABLE_NOTICES.md
index f5ebe251..837c7431 100644
--- a/docs/READABLE_NOTICES.md
+++ b/docs/READABLE_NOTICES.md
@@ -49,6 +49,26 @@ countdowns keep their existing behavior.
 
 ## Verification
 
+24 October user-report follow-up: a fresh local create at source revision
+`59aa56af2bd2b98f5996fadb888019b3ebb53498` showed only concise progress, then
+**Room created** with **Continue**. The confirmation remained readable for at
+least 30 seconds through background polling and a player-circle change.
+Continue removed only the notice; the same room and selected circle remained.
+The dedicated QA room and screenshot are preserved. The three focused
+notice/entry/seat test files pass **23/23**. A bounded source audit found no
+remaining automatic dismissal of actionable text: action notices and room/seat
+confirmations use Continue, standard toasts use Dismiss, and uncertain request
+instructions retain their recovery controls. No application callers override
+the toast provider's no-timeout default.
+
+The same follow-up read the live homepage at **dune.procrastination.games**:
+it still identifies `716304bb9ed7bcf73202e07712de7c6d857ddc0c`, predating the
+room-confirmation fix in `999edb6`. This is an outstanding deployment gap;
+no new application change or deployment was made for this recheck. The local
+development server had been stopped and was started for this dedicated QA;
+existing saved games were preserved. Private evidence is in
+`/home/quintine/.local/share/dune/checkpoints/20261024-readable-notices-followup/`.
+
 24 October deployed recheck: the public site displayed revision
 `716304bb9ed7bcf73202e07712de7c6d857ddc0c`. A dedicated QA create request showed
 the concise progress screen, then opened its lobby without a persistent room