android-polishlisted

# Android Polish & Ship Gate This is the **final stage** of the Android app pipeline. The app exists and builds; this pass closes the gap between "functionally complete" and "passes Google Play review and feels finished." It is the last gate, so it carries the strictest rule in the whole pipeline: **every item is verified with a command, a tool, or a snapshot - never an eyeball.** Pipeline position: ``` research -> planning -> monetization -> design -> MCP code -> > POLISH / SHIP GATE < ``` ## Core philosophy 1. **The happy path was the easy 80%.** The polish is in the empty screens, the error states, the slow network, the rotated phone, the *backgrounded-and-killed* process, the screen reader, the 200%-font user, and the aggressive-battery OEM. 2. **Verifiable, not vibes - enforced.** This skill's #1 failure mode is eyeballing the home screen and declaring victory. So every check names *how* to verify it: a gradle task, a tool, a snapshot test, or a measured number. If you cannot verify it, it is not done. A polish report without command output / tool results / snapshots is not a polish report. 3. **Ship-blockers before polish.** A beautiful app Play rejects is not shippable. Clear the P0 compliance and crash checks before spending budget on screenshot framing. 4. **Match the design system.** Reuse the tokens, motion, and components the design skill chose. Don't introduce a new accent or radius in the polish pass. ## How to run it Work strictly by severity. Each item