Harden browser docs and transport recovery

README.md

@@ -1,6 +1,6 @@
 # Adaptive Multi-Protocol Browser
 
-> Status: draft | Updated 2026-07-07 | Applies to: AMPB contributors and operators
+> Status: draft | Updated 2026-07-11 | Applies to: AMPB contributors and operators
 
 Adaptive Multi-Protocol Browser, or AMPB, is a transport-aware browser shell. It routes
 URLs to the right network, adopts transports that are already healthy, and manages missing
@@ -11,8 +11,8 @@ app, Android targets bundled GeckoView/Fenix/Tor Browser Android-lineage code, a
 uses an AMPB-owned shell with platform browser-engine constraints.
 
 The first fixture is Wownero across clearnet, Tor, I2P, Gemini, and Reticulum-oriented
-targets generated by AMPG. Interactive fixtures include `ai-gen-bot` and the Medusa
-multi-tenant platform.
+targets generated by AMPG. Interactive fixtures should be described publicly by the
+capabilities they exercise, while project-specific target notes stay in private docs.
 
 ## Goals
 
@@ -21,6 +21,8 @@ multi-tenant platform.
 - Prompt on first visit before installing or starting a missing transport.
 - Manage approved transports through isolated AMPB state.
 - Keep browser profiles isolated by transport.
+- Treat route-aware desktop launches as a convenience and QA mode until storage isolation
+  is proven for mixed clearnet, Tor, and I2P navigation.
 - Present transport health in plain language.
 
 ## Non-goals