6973ce3ac2
Lightpanda's HTTP cache is opt-in (`--http-cache-dir`, off by default), and the launcher never passed it, so every Browser Use navigation re-fetched every asset. Point all Hermes-spawned instances at one shared cache under $HERMES_HOME/cache/browser-use/lightpanda/http-cache. Sharing it across sessions keeps assets warm through session churn; Lightpanda stores it in sqlite (WAL), so a write that loses a race degrades to a cache miss rather than a failed load, and --http-cache-entry-limit (default 1000) bounds the directory without Hermes managing eviction. Measured over 25 navigations across 5 sites, median warm navigation drops from 0.40s to 0.18s on news.ycombinator.com and 0.14s to 0.10s on wikipedia; total navigation time 7.0s -> 5.9s. The flag has existed since Lightpanda 0.3.x (April 2026), so this needs no minimum-version bump.