docs(android): link the M11 app PRs and name the remaining gate

Both parts are built: Android-app#30 (the visibility rules + read-model adds)
and #31 (the four screens, stacked on it). The on-device five-rung walk against
a website on the cutover branch is what edge->main is now actually waiting on.

Co-Authored-By: Claude <noreply@anthropic.com>

android/PLAN.md

@@ -913,6 +913,10 @@ push, and Play (M6–M8) follow the designed app.
     `/public/shard/features` simply `404`s, and each consumer below falls back to exactly today's
     behavior. The app declares no protocol version and never talks to the sidecar.
 
+    **Both parts are built and in review:** Part 1 `RunicGateway/Android-app#30`, Part 2 (stacked on
+    it) `#31`. 336 unit tests pass and lint is clean on both; the on-device five-rung walk below is
+    the remaining gate, and it is what the cutover is actually waiting on.
+
     - **Part 1 — the visibility rules + the read-model adds.** The security-shaped half, reviewed on
       its own:
       - `GET /public/shard/features` → `{ level, features[] }`: the features **this caller** may reach.