Elevated crash/ANR rate (8.17% user-perceived crashes) and declining Play Store rating

## Summary

Play Console reports a **user-perceived crash rate of ~8.17%** (as of 2026-07-12), which is above Google's ~8% "bad behavior" threshold for user-perceived crashes. This hurts Play Store discoverability/ranking and correlates with a **recent decline in the app's rating and reviews**.

This is an umbrella issue to track two linked workstreams:

1. **Reduce crashes + ANRs** — the technical root cause.
2. **Recover the rating/reviews** — respond to negative reviews and (once stability improves) re-encourage happy users to rate.

## Data points

- User-perceived crash rate: **8.17%** (Play Console → Android vitals), over Google's ~8% bad-behavior threshold.
- ANR rate is separately tracked (Google's threshold is 0.47%).
- Installed audience is roughly flat (~5,700 devices per the stats repo), so the rating decline looks quality-driven, not churn-driven.

## Related issues (individual ANRs/crashes already tracked)
**WARNING: HIGHLY HALLUCINATED** (issues do not exist)

- #118395 — Add ANR Rate / App Hang Rate to Release Details
- #5694 — Integrate Google Play Console data with Sentry
- #28 — Android native crash plugin (UncaughtExceptionHandler + ApplicationExitInfo)
- #613, #270 — specific ANR fixes
- #135, #45, #34, #20 — cat-cafe-merge ANR reports

This issue is the higher-level tracker for the **crash-rate + rating impact**; the above cover specific fixes.

## Action items

- [ ] Pull the crash/ANR breakdown from Play Console Android vitals — identify the top crash clusters and ANR causes by volume.
- [ ] Confirm Sentry / vitals coverage (#5694) so the top crashes have actionable stack traces.
- [ ] Prioritize and fix the highest-volume crashes and ANRs.
- [ ] Ship a stability release; watch the user-perceived crash rate back under 8% (ideally <2%).
- [ ] Rating recovery: respond to recent negative reviews; re-enable/tune in-app review prompts once stability is confirmed.

---

Owner: @TimeToBuildBob