Play policy compliance for next release: 16 KB pages, target API 36, accessibility disclosure

Play Console currently lists three policy items that are **not** addressed by master, so any release cut before these merge will be rejected (likely including the update currently in review):

| Item | Status | PR |
|---|---|---|
| 16 KB memory page sizes (enforced for updates since Nov 1, 2025) | NDK r25 produces 4 KB-aligned `libaw_server.so` (verified `LOAD ... 0x1000`) | #213 (NDK r28 + CI alignment gate) |
| Target API 36 by **Aug 31, 2026** | targeting 35 | #214 |
| Accessibility API prominent disclosure (standing rejection since Oct 2023) | onboarding jumps straight to accessibility settings | #215 |

Already fine: target API 35 (landed in #179).

## Manual Play Console steps (not fixable in code)

- [ ] Fill the **AccessibilityService declaration form** (App content → Sensitive app permissions): declare non-accessibility use, describe web-browsing-tracking core functionality, reference the new in-app disclosure (#215)
- [ ] After the next release build, spot-check the AAB with `bundletool` / Play Console pre-launch report that no 16 KB warnings remain
- [ ] Confirm the in-review update's verdict; if rejected for 16 KB, resubmit after #213 ships in a release

Related: #189 (FOREGROUND_SERVICE_DATA_SYNC + ChromeWatcher NPE) covers the other release blockers.