solo-android-release

# android-release — ship Android to testers, then to Play **Start with MINIMAL** (a working tester link in minutes). Do FULL only when the user wants the public Play listing. Sibling skill: **`ios-release`** for iPhone/TestFlight. Golden rules: - **Never hit final publish/"Send for review" without the user's OK** — it's outward-facing. Filling drafts is fine; an internal-testing rollout is low-risk + reversible, so a prior "set it all up" covers it — but state what you did. - **Back up the keystore + password** — losing it = can't update the same Play listing. - Browser work: **the user logs in** (never touch their password/2FA); you drive the forms after. Playwright MCP runs its **own persistent Chromium profile**, NOT the user's Chrome — a Chrome that is "already logged in" is invisible to it, and you can't attach unless it was started with `--remote-debugging-port` (check `curl -s localhost:9222/json/version` before promising anything). So: open the Google sign-in page, hand the window over, wait. The login then sticks for later sessions. - **The app may live in someone else's developer account** (client/agency who granted you access). `play.google.com/console/developers` shows a **"Choose developer account"** list — one Google login can hold several. Before concluding "the app isn't here", check every developer account in that list, not just the app list of the first one. Newly granted access appears there after a reload. --- ## Which track? (who can...