fuse-browser-usage

<objective> This is the canonical doctrine for every `mcp__fuse-browser__*` call: 4 zero-tolerance rules (fast-path first with no browser launch for reading, one session always closed, batch over per-URL loops, deterministic schema-based extraction over manual snapshot parsing), then routing to one of three reference profiles depending on the goal -- research/docs (fetch, crawl, SERP, no pixels), webapp testing (console, network, live interactions), or visual/design (screenshots, responsive + dark mode, regression diffing). It covers only the raw browser tooling. The full design pipeline (identity -> generate -> audit) is NOT here -- that lives in `fuse-design:design-web` and the `fuse-design:design-review` gate. </objective> # fuse-browser — Efficient Usage Canonical doctrine for every `mcp__fuse-browser__*` call. Read this skill FIRST, then load the one reference matching your goal. Default engine is **patchright** (stealth identity auto-generated); the Chromium binary comes from `setup.sh`. ## 4 Rules (ZERO TOLERANCE) 1. **Fast-path FIRST (no browser launch, ~10× faster)** — `browser_fetch` / `browser_fetch_batch` / `browser_crawl` / `browser_serp_batch` to read a page, bulk-fetch, crawl a site, or scrape Google SERP. Open a live session ONLY when you need interaction, JS rendering, or pixels. 2. **One session, always closed** — `browser_open` once → reuse the `sessionId` across `browser_navigate` calls → `browser_close` when done. Never leak sessions; the 2-min TTL i...