Session safety and route caching

Public guest documents may be prepared in the current browser only when their registered route policy permits it. Signed-in, account-specific, terminal-output, entitlement, and other private payloads use session-safe or no-store behavior.

The adapter declares policy through SnapWeb’s versioned route registry. It does not duplicate fetching, HTML parsing, or cache ownership.

Test transitions between signed-out and signed-in menus, account pages, home variants, Terminal, Docs, Search, and Shop. A cached guest page must not overwrite member state, and a member response must never be reused for a guest.

Avoid generic optimization rules that combine or cache private REST or document responses.