github-such-software/adaptive-multi-protocol-browser
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-browser.git synced 2026-10-26 09:48:32 +01:00
Code Issues Packages Projects Releases Wiki Activity

Keep transports in one browser window

Browse Source
This commit is contained in:
jwinterm
2026-07-11 10:20:54 -04:00
parent 2c68c072ba
commit ce874fec3c
20 changed files with 346 additions and 423 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/fixture-manifests.md
+8 -4
View File
@@ -3,10 +3,14 @@
> Status: draft | Updated 2026-07-11 | Applies to: AMPB and AMPG compatibility checks
AMPB can check AMPG fixture manifests without contacting any network. The check confirms
that each generated fixture URL routes to the expected AMPB transport and profile, uses
the declared transport-profile isolation contract, and fits that transport's interaction
that each generated fixture URL routes to the expected AMPB transport context, uses
the declared transport-context isolation contract, and fits that transport's interaction
policy.
`ampg.fixture-manifest.v2` uses `checks.context` for the logical browser context. AMPB can
still read v1 manifests for route compatibility, but v2 is required for the current
one-window isolation contract.
Route-expanded fixtures may include `route.match` and `route.fixture_path`, which identify
the route group that produced the fixture.
@@ -21,8 +25,8 @@ manifest.
## Scope
Fixture checks validate route selection, profile isolation expectations, and declared
interaction policy only. They do not verify process separation, daemon health, hidden
Fixture checks validate route selection, context isolation expectations, and declared
interaction policy only. They do not verify engine-level partitioning, daemon health, hidden
service reachability, IPFS pinning, TLS, or content freshness.
The manifest must not contain private deployment notes, service keys, credentials, or