- browser_vault_enter_code blocks on the user's code INSIDE the handler-level
fence, so a takeover during that (human-length) wait was only detected
afterwards by the epoch check, which discards the result: the code had
already been written into the page the human was typing into. The
supervisor write path now re-admits against the lease immediately before
evaluating; a human lease refuses the write itself.
- Profiles seeded before `.hermes-browser-launcher` existed never got their
Browser Exec= rewritten after `hermes profile rename`. The launcher recovers
the marker from its own Name=Browser entry (bash builtins only; the seed
runs on a minimal PATH).
- Threat model: Chromium's DevTools port is reachable by any local user, not
only the gateway's OS user; documented (a Chromium property, no per-UID
switch exists).
Reported by @thelonewander3r (round 6, re-surfaced at e4f591d1b0).
36e9ddeff2
