Keep admin and seat recovery notices readable

Show progress during initial admin and seat-control submissions; retain exact recovery instructions for uncertain requests and explicit retries. Keep seat recovery and handover confirmations above the table until Continue without blocking gameplay. Use readable 16px text and 44px controls.

Verified isolated checkpoint: types, lint, 5381 offline tests, 52 HTTP tests and build. Local delayed/lost-response browser QA covered admin creation, durable retry, handover and seat recovery, mobile readability and saved-seat restoration. Existing 2098 rooms and 4455 seats preserved. Deployment acceptance follows separately.

README.md

@@ -74,7 +74,9 @@ New create/join requests save a private, tab-scoped retry record before sending.
 
 Normal creation/join shows brief progress; recovery instructions stay open when
 attention is needed. Completed-action notices wait for **Continue** so their text
-can be read at your pace. See [readable notices](docs/READABLE_NOTICES.md).
+can be read at your pace. Seat recovery and handover confirmations also wait for
+**Continue**; admin and seat-control requests show recovery instructions only
+when needed. See [readable notices](docs/READABLE_NOTICES.md).
 
 An uncertain saved-kit recovery keeps its exact retry details in memory and prevents conflicting navigation. If that recovery has become obsolete, deliberate abandonment releases the controls after explaining that it cannot undo a completed recovery. Keep a valid saved kit before discarding retry details.