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

[ErikBjare]

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 (fix: add prominent disclosure before accessibility settings redirect #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 build: bump NDK to r28 for 16 KB page-size compliance #213 ships in a release

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

[ErikBjare]

Code side complete (all merged to master as of 2026-08-10):

Item	PR	Status
Target API 36	#214	✅ merged
16 KB memory pages (NDK r28 + CI alignment gate)	#217 (superseded #213 after a merge conflict)	✅ merged
Accessibility prominent disclosure	#215	✅ merged

#217's CI ran the full build + API-29 E2E green with the r28 toolchain, so the 16 KB alignment gate is proven in CI, not just locally. #215 was rebased onto the r28+API36 master before merge and passed a full build.

Remaining — Play Console only (not code)

• Fill the AccessibilityService declaration form (App content → Sensitive app permissions): declare non-accessibility use + describe web-browsing-tracking core functionality, now backed by the in-app disclosure from fix: add prominent disclosure before accessibility settings redirect #215. The code change alone won't clear the standing Oct-2023 rejection without this form.
• Cut a release from current master and confirm the Play pre-launch report shows no 16 KB warnings.
• Confirm the previously in-review update's verdict; if it was rejected on 16 KB grounds, resubmit with the new release.

Once the declaration form is submitted and a compliant release is cut, all four Play policy items are resolved — with margin before the Aug 31 API-36 deadline.