Declare browser profile isolation

docs/architecture.md

@@ -94,6 +94,10 @@ Daemon adapters provide a common interface:
 Adapters must be conservative. They do not modify non-AMPG config without showing a
 plan first, and managed config lives under AMPG-owned state directories.
 
+Fixture manifests are the AMPG-to-AMPB boundary. They declare the published URL, expected
+transport, expected profile, and transport-profile isolation result. They do not prescribe
+browser process management or local daemon ownership; those decisions remain inside AMPB.
+
 ## Platform providers
 
 Platform providers decide what daemon management means on the current host. AMPG detects

docs/fixture-manifests.md

@@ -19,7 +19,7 @@ The manifest contains public route expectations only:
 - enabled protocol fixtures.
 - protocol renderer and relative output path.
 - route URL for AMPB checks.
-- expected AMPB transport and profile.
+- expected AMPB transport, profile, and transport-profile isolation.
 - declared interaction tier, identity adapter, payment adapter, realtime flag, and
   public exposure flag.
 - optional route-group metadata for configured public route policies.
@@ -27,6 +27,10 @@ The manifest contains public route expectations only:
 It must not contain private host inventory, hidden-service keys, tunnel keys, credentials,
 or deployment notes.
 
+The isolation check is a browser-facing result, not a daemon-management instruction.
+AMPG declares which transport profile must consume the route; AMPB independently decides
+whether to adopt or start the local transport needed to reach it.
+
 ## Commands
 
 ```sh