fix(offline): hotseat review fixes + PWA stale-shell (SW route order)

Owner review of the pass-and-play PR:
- Roster delete (bug): a correct host PIN now ARMS a delete cross next to
  the row (mirroring the lobby delete) instead of removing it silently;
  tapping the kebab again clears the host authorisation.
- Variant picker (UX): replace the dropdown with the Quick-Match variant
  plaques + the multiple-words toggle, one-to-one.
- Keyboard layout (UX): the roster sits in a scroll region with the Start
  button pinned (friends-form pattern), so a name input's soft keyboard
  shrinks the region instead of leaving a full-height blank spacer painted
  behind the keyboard.
- e2e: variant via plaque + a row-delete (arm then cross) regression step.

PWA stale-version (pre-existing, same PR):
- sw.ts: register the network-first NavigationRoute BEFORE precacheAndRoute.
  Workbox matches in registration order and the precache route (directoryIndex
  index.html) shadowed the shell navigation, serving it cache-first — the old
  build's __APP_VERSION__ until a second load. Fixes both the maintenance
  self-reload and a cold open after a deploy. Doc updated (ARCHITECTURE).

docs/ARCHITECTURE.md

@@ -1242,10 +1242,15 @@ browser-language detection — crawlers render with arbitrary languages). The fa
 built from `ui/src/sw.ts` by **vite-plugin-pwa** (injectManifest strategy) — the client registers it
 **web-only**, never inside a Mini App or the mock build (the plugin is disabled there entirely). It
 **precaches the app shell and the hashed assets** (Workbox) so an installed PWA cold-launches with
-no network, and falls every in-scope navigation back to the precached shell (the hash router
-resolves the route client-side); the landing page and the conditional polyfill bundle are excluded,
-and the Connect stream and runtime API POSTs are never precached nor intercepted, so the live app is
-never served stale. This satisfies Chromium's installability requirement (a registered SW, needed
+no network. Shell **navigations are network-first** — the fresh `no-cache` shell is fetched from the
+server (so a new deploy is picked up on the very next launch, not the one after), falling back to the
+precached shell only when the network is unreachable or too slow; the immutable hashed assets stay
+cache-first, and the hash router resolves the route client-side. This navigation route is registered
+**before** the precache route on purpose: Workbox matches in registration order, and the precache
+route (its `directoryIndex` is `index.html`) would otherwise shadow it and serve the shell
+cache-first — the old build's version until a second load. The landing page and the conditional
+polyfill bundle are excluded, and the Connect stream and runtime API POSTs are never precached nor
+intercepted, so the live app is never served stale. This satisfies Chromium's installability requirement (a registered SW, needed
 for install on Android) and powers the opt-in **offline mode** (in progress): a deliberate, device-scoped Settings
 toggle — distinct from the transient gateway-reachability signal — that tints the header blue with
 an *Offline* chip and confines play to on-device `vs_ai` games. The **offline lobby lists only those