docs(android): record the account-deletion decision for M8

The org lead chose self-service deletion on the website and in the app,
with a runicgateway.com page as Play's deletion URL. Planned separately,
before the cutover.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

android/PLAN.md

@@ -1050,9 +1050,13 @@ push, and Play (M6–M8) follow the designed app.
       posts and moderation, notification read state and preferences, and search text. All of it
       is declared collected, not shared, encrypted in transit, required. The server address
       and the inbox snapshot stay on the phone. Step 3 adds its own rows when it lands.
-      **Open:** the form's account-deletion questions. The app starts accounts (the sign-up
-      link to the deployment's website, and in-app game-account creation), and the platform has
-      no self-service account deletion.
+      **Account deletion, decided (org lead, 2026-10-29): build self-service deletion.** The
+      app starts accounts (the sign-up link to the deployment's website, and in-app
+      game-account creation), so Play requires a deletion path in the app and at a web address,
+      and the platform had none: only an admin could delete an account. A member gets *Delete
+      my account* on the website and in the app, which removes the account and its game links.
+      A runicgateway.com page explains it, and that page's address is the one Play is given. It
+      is planned as its own piece of work, before the cutover.
    3. **Report, block and hide** across `website`, `Module-Rust`, the kit and this app
       (`USER_SAFETY.md` §7).
    4. **The cutover**, `edge` → `main`, once 1-3 have landed, so the first Play bundle carries