Build a browser-native Station client path

[joshuajbouw]

Outcome

Website-hosted Astrid experiences can resolve and verify Station content entirely on the user side without a native filesystem or always-on application server.

Parent

astrid-runtime/astrid#1563

Scope and ownership

Repository: astrid-runtime/station-tools. Browser transport, browser persistence/locking, WASM-compatible client boundary, and a minimal in-browser resolution demonstration. The protocol crate already compiles to wasm32-unknown-unknown; the native client currently depends on filesystem locking.

Dependencies

• Stable landed Station v1 wire and TUF contract.
• A deliberate browser storage and cross-tab locking design.
• Decision on whether browser execution installs Capsules, supplies verified bytes to a web runtime, or only resolves metadata.

Exit gate

• The browser client compiles for the supported WASM target without native filesystem dependencies.
• fetch transport and persistent trusted-state/cache semantics work in browser storage with rollback/freeze/expiry guarantees intact.
• A static website resolves and verifies an official or disposable Station generation and demonstrates the agreed user-side Astrid handoff.

Claim boundary

This is a browser consumer of the same Station v1 contract, not a second Station product version and not permission to weaken TUF, event replay, or local runtime policy.