SXSW Panel Vote Assistant

@@ -0,0 +1,166 @@+---+name: sxsw-vote+user-invocable: true+description: >+  Cast the user's SXSW PanelPicker community vote for the Adom panel "The+  Million-Dollar Markets Hiding in Plain Sight" (voting closes Sunday, Aug 23,+  2026, 11:59pm PT), fully automated: check/guide install of Adom Bridge (ab)+  and pup on their laptop, create their SXSW ID with their @adom.inc email,+  handle the confirmation email, click the vote heart, verify it stuck, and+  show proof. Newbie-aware: many Adom employees have NEVER installed ab or pup;+  this skill walks them through it and doubles as their first taste of the AI+  driving their own machine. Trigger words: sxsw, sxsw vote, panelpicker, panel+  picker, vote for the panel, vote for the adom panel, sxsw panel, community+  voting, vote for john's panel, million dollar markets, hiding in plain sight,+  sxsw id, cast my vote, sxsw signup, sxsw voting site.+---++# sxsw-vote: cast the user's vote for the Adom SXSW panel++John Lauer (Adom's founder) is a speaker on the SXSW 2027 panel **"The+Million-Dollar Markets Hiding in Plain Sight"**, moderated by Jason Roys (CEO+of MotionSafe, an Adom customer and advocate). SXSW picks panels partly by+community vote. Your job: get THIS user's one vote cast with as close to zero+human effort as possible, and leave them delighted that their AI just drove+their own computer.++- **Deadline: Sunday, August 23, 2026, 11:59pm PT.** After that, stop offering+  this skill.+- **One person, one vote, one account.** Never create a second account or vote+  twice for the same human. That can hurt the submission. The AI casting the+  user's OWN vote at their request is fine; inventing voters is not.+- Panel deep link (share this one; it works logged-out as a landing page):+  `https://participate.sxsw.com/flow/sxsw/sxsw27/community-voting-sxsw/page/communityvoting/session/1785345735591001Dxe9`+- Panel details site: `https://plain-sight-insight.lovable.app`++## Step 0: figure out which kind of user you have++Run `adom-bridge-cli targets` (in the container).++- **CLI missing or no bridge connected → NEWBIE PATH (below).** Do not skip+  them to manual voting; the whole point is they experience Hydrogen + ab + pup.+- **One target connected →** use it. **Several →** ask which machine they're at,+  then pass `--target <name>` on every call.+- Set your caller identity once per session: every `adom-bridge-cli` call in+  this flow should carry `--ai-thread "sxsw-vote"` (or export+  `ADOM_AI_THREAD="sxsw-vote"`).++## Newbie path: install Adom Bridge + pup first++Tell the user what's about to happen in one friendly sentence: "I'll help you+install Adom Bridge so I can drive a browser on your laptop and cast your vote+for you; you'll watch it happen."++1. Have them open `https://wiki.adom.inc/adom/adom-bridge` on the laptop they+   are physically using, download the installer for their OS from the page, and+   run it. (They must do this one step by hand; you cannot install onto a+   machine you can't reach yet.)+2. Wait, then poll `adom-bridge-cli targets` until their machine appears.+3. pup normally ships with Bridge. Probe with `pup_status {}`; if you get+   `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. First pup window may take ~30s (Chrome-for-testing download). Warn the user.++## The voting flow (exact verbs, learned the hard way on 2026-08-11)++All windows open in the BACKGROUND. Never foreground or resize a window the+user is working in; signal with a taskbar flash (`desktop_flash_window`) and+let them come to it. Maximize the pup window ONCE right after opening it.++### 1. Open the signup page++```+pup_open_window {"sessionId":"sxsw-vote","profile":"sxsw","url":"https://id.sxsw.com/sign_up"}+```++If the user already has a SXSW ID (ask, or check their password manager /+contacts), go to `https://id.sxsw.com/sign_in` instead, fill+`#user_email` / `#user_password`, submit, and jump to step 5.++### 2. Kill the cookie banner FIRST++A cookie-consent banner ("Accept / Deny Non-Essential") appears and will eat+your submit click. Find the Accept button's coordinates with `pup_eval` ++`getBoundingClientRect`, then `pup_input_dispatch {type:"click", x, y}`.++### 3. Fill the form++Fields (stable Rails ids): `#user_first_name`, `#user_last_name`,+`#user_email`, `#user_email_confirmation`, `#user_password`,+`#user_password_confirmation`, checkbox `#user_agree_to_terms`.++- Get the user's real first/last name and their **@adom.inc email** (from+  `adom-cli` profile or by asking). Never invent an identity.+- Generate a random **16-char alphanumeric** password (SXSW requires 12+).+- Type each field with+  `pup_input_dispatch {"type":"type","selector":"#user_first_name","text":"..."}`.+- **Quirk:** selector-based CLICKS (`type:"click","selector":...`) frequently+  time out on this site. Coordinate clicks are reliable: `pup_eval` the+  element's `getBoundingClientRect()` center, then+  `pup_input_dispatch {type:"click", x, y}`. Use that for the checkbox and the+  `input[type=submit]` button. Verify the checkbox with+  `document.querySelector("#user_agree_to_terms").checked === true`.+- **Immediately tell the user their new password in chat** and where it got+  saved (next step). It is THEIR account.++### 4. Submit, save the password, confirm the email++- Submit (coordinate click). Success = redirected to `/sign_in` with "Please+  confirm your email address by clicking on the link we just sent you."+- **Chrome will show a native "Save password?" bubble.** ALWAYS click **Save**.+  The bubble is browser chrome, not page DOM: use UIA, which works in the+  background without stealing focus:+  `desktop_find_control {"hwnd":<pup hwnd>,"name":"Save","controlType":"Button"}`+  then `desktop_ui_click` the same. (Get the hwnd via `desktop_find_window` on+  the pup window's title.) This stores the login in the laptop's password+  manager. Standing rule from John: whenever this bubble appears in a pup flow,+  store it.+- Confirmation email, two paths:+  - **adom-google configured** (most Adom employees): poll+    `adom-google api .../gmail/v1/users/me/messages -q 'q=from:sxsw confirmation newer_than:1d'`,+    pull the `https://id.sxsw.com/users/confirm/<token>` link out of the body,+    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.++### 5. Cast the vote++- Navigate to the LOGGED-IN session URL. **It is NOT the URL from the+  invite email.** The public link's path segment `communityvoting` renders a+  blank page when authenticated. The working one is hyphenated, under the+  `auth-` flow:++```+https://participate.sxsw.com/flow/sxsw/sxsw27/auth-community-voting-sxsw/page/community-voting/session/1785345735591001Dxe9+```++- The vote control is a heart button:+  `button[data-test="rf-icon-interest"]` (class `favorite-session`,+  `aria-pressed` reflects state, inner svg `data-test="heart-open-icon"` when+  unvoted).+- **Quirk:** trusted CDP clicks (both selector and coordinate) do NOT toggle+  this Rainfocus widget. A plain JS click DOES:++```+pup_eval {"expr":"document.querySelector('button[data-test=\"rf-icon-interest\"]').click()"}+```++### 6. Verify, prove, clean up++- Check `aria-pressed === "true"` and that `heart-open-icon` is gone (filled+  heart). Then `pup_reload` and check AGAIN; only a state that survives reload+  is a counted vote. Do not report success without the post-reload check.+- `pup_screenshot`, show the user the filled heart (shotlog channel or send+  the file), and flash the pup window's taskbar so they can admire it.+- Encourage them to share the public panel link with friends (every SXSW+  account holder can vote), then `pup_close_window` when they're done.++## Report back++Tell the user, in plain words: their SXSW ID email, where the password lives+(chat + Chrome password manager on their laptop), that their vote is cast and+verified, and the deadline so they can nudge friends. Suggest they reply "voted"+on the team thread so we can track coverage.