SXSW Panel Vote Assistant

@@ -60,15 +60,24 @@ for you; you'll watch it happen."    `unknown_verb` or a bridge-not-installed error, follow the `_hint` in that    response (ab responses are self-teaching; typically `bridge_list` +    `refresh_bridges` or an install hint from `https://wiki.adom.inc/adom/pup-bridge`).-4. **Require a current pup (2.0.112+).** Run-   `bridge_check_updates {"name":"puppeteer"}`; if `updateAvailable` is true,-   run `refresh_bridges {"name":"puppeteer"}` before starting. 2.0.112 added-   the credential vault's automatic login capture (`captureLogins:"on"`) and-   anti-phishing credential hints, which this flow wants: the user's SXSW-   login gets captured into the OS-keychain vault when they sign IN, so-   their future AI sessions can reuse it. (Note: SIGNUP typing is not-   captured, which is why the Chrome Save-password bubble step and telling-   the user their password both still matter.)+4. **Probe with `pup_readiness {}`, NOT `pup_status`.** `ready:true` means+   you can drive. Also run `bridge_check_updates {"name":"puppeteer"}` and+   `refresh_bridges {"name":"puppeteer"}` if an update is available: get on+   **2.0.160+**, which is where this flow was verified end to end.+   **Expect the upgrade to restart pup**: verbs briefly fail with+   "Browser bridge request failed", "Protocol error (Target.createTarget)",+   or windows vanishing. That is NORMAL during an update. Wait ~15s, poll+   `pup_readiness` until ready, re-open your window with the same sessionId,+   and carry on. Do the update FIRST so it never lands mid-signup.+5. **The vault verbs (for a user who already has a SXSW account):**+   `pup_credentials {}` lists saved logins (host + username only; NOT+   `credential_list`, which is a different, empty stub). If the user's SXSW+   login is there, `pup_login {sessionId, submit:true, submitReason:"..."}`+   fills and submits it in the background from the vault: verified working.+   Auto-capture stores a login when the user signs IN with real keystrokes;+   it does NOT fire on a signup, nor when fields are set via JS, which is+   why the Chrome Save-password bubble step and telling the user their+   password both still matter. 5. First pup window may take ~30s (Chrome-for-testing download). Warn the user. 6. **The bridge can hiccup mid-flow** (a verb returns a "startup hang" or    "no longer falls back to the active window" hint, or a window loses its@@ -158,8 +167,12 @@ Fields (stable Rails ids): `#user_first_name`, `#user_last_name`,     and `pup_navigate` to it. It confirms AND logs the session in, landing on     the voting catalog.   - **No adom-google:** ask the user to open the "SXSW Account Confirmation"-    email (any device) and click the link, then tell you when done. Then sign-    in via `https://id.sxsw.com/sign_in` in the pup window.+    email (any device, phone is fine) and click the link, then tell you when+    done. Then sign in via `https://id.sxsw.com/sign_in` in the pup window.+    **Do NOT push the user to authorize adom-google just for this.** Granting+    an AI full Gmail access to save one tap on a confirmation link is a bad+    trade; offer it only if they already have it set up, or if they ask.+    The flow is fully functional without any email access.  ### 5. Cast the vote