Seed legacy platform storage explicitly and drop Android app handles

docs/modernization/roadmap.md

@@ -92,6 +92,14 @@ Current hotspot files:
 
 Latest slice:
 
+- `App` no longer owns `and_app` or `and_engine`; the retained Android
+  entrypoint now seeds only the explicit legacy platform storage snapshot
+  needed by touched platform services instead of storing Android-native
+  handles on the app singleton.
+- `active_legacy_storage_paths()` no longer snapshots `App::I` lazily inside
+  `src/platform_legacy/legacy_platform_state.*`; storage roots are now seeded
+  explicitly from app startup plus the iOS, macOS, and Android entrypoints
+  through `set_legacy_storage_paths(...)`.
 - `pp_platform_api` no longer compiles
   `src/platform_linux/linux_platform_services.*`; Linux concrete platform code
   now lives in `pp_platform_linux`, which `pp_legacy_app` and
@@ -215,9 +223,11 @@ Current architecture mismatches that must be treated as real blockers:
   the retained GLFW window hooks, Apple handle snapshots, and fallback
   storage-path return now also using local retained-state helpers instead of
   direct method-body reads, while Windows VR session snapshot state now also
-  lives behind platform-owned helpers instead of on `App`, and the
+  lives behind platform-owned helpers instead of on `App`, the
   `platform_legacy`-mirrored Apple/GLFW handle cluster is now seeded
-  explicitly from platform entrypoints instead of being copied out of `App`.
+  explicitly from platform entrypoints instead of being copied out of `App`,
+  and retained storage roots are now also seeded explicitly instead of being
+  lazily copied from `App::I` inside `active_legacy_storage_paths()`.
 - `src/platform_legacy/legacy_platform_services.*` is still part of the live
   app shell.
 - `pp_panopainter_ui` still depends on `pp_legacy_app`.