feat(cli): preview --browser-no-gpu for gpu-unstable hosts

[vanceingalls]

What

Adds hyperframes preview --browser-no-gpu (requires --browser-path): launches the opened browser with --disable-gpu. Threaded through openBrowser's disableGpu option and all three preview launch modes (dev, local-studio, embedded).

Why

Wild report: on NixOS, preview's auto-opened hardware-accelerated Chrome triggered NVIDIA Xid 32 driver crashes. Preview has no way to avoid launching a hardware-accelerated browser on a GPU-unstable host; this gives an explicit opt-out.

Validation

New unit tests in openBrowser.test.ts (buildBrowserArgs appends/omits --disable-gpu correctly) — 25 tests total, all green. Validation error added when --browser-no-gpu is passed without --browser-path (the system default browser can't receive Chromium flags).

🤖 Generated with Claude Code

[vanceingalls]

• fix(cli): surface video frame-injection failures in snapshot output #2255
• fix(shader-transitions): pin cloned scene roots to composition dimensions #2254
• fix(cli): fold canvas pixel hashes into the frozen-sweep fingerprint #2253
• chore(producer): resync stale committed puppeteer-core symlinks to lockfile version #2259
• fix(producer): disk-headroom gate before hdr raw frame pre-extraction #2256
• feat(cli): preview --browser-no-gpu for gpu-unstable hosts #2252 👈 (View in Graphite)
• fix(cli): settle post-seek font subset loads before audit screenshots #2251
• fix(engine): densify drawelement self-verify with parallel worker count #2250
• fix(producer): withhold de parallel router below a machine ram floor #2249
• fix(producer,engine): gate drawelement on ancestor background-image + tail verify sample #2247
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[miga-heygen]

#2252 — preview --browser-no-gpu for gpu-unstable hosts

Verdict: LGTM 🟢

New CLI flag for preview: --browser-no-gpu passes --disable-gpu to the launched browser. Correctly requires --browser-path — can't pass Chromium flags to the system default browser (error + process.exitCode = 1 with actionable message). Tests verify buildBrowserArgs with and without the flag.

Addresses NVIDIA Xid 32 reset reports on NixOS. Small, well-gated.

Review by Miga

[miguel-heygen]

Reviewed current head f3c3a15. --browser-no-gpu is validated as requiring --browser-path, propagated through preview/studio, and defaults off; argument tests cover flag presence/absence. Required checks are green. APPROVE.

[james-russo-rames-d-jusso]

Reviewed at f3c3a15.

Small clean escape-hatch for a real driver bug (NixOS/NVIDIA Xid resets). The validation error catches the misuse ("without --browser-path the open-package fallback can't receive Chromium flags") with the correct alternative (--no-open). Threaded through all three preview launch modes (dev, local-studio, embedded) via openStudioBrowser, and the two buildBrowserArgs unit tests cover the append + omit paths.

The flag is preview-scoped so there's no capture-path implication to worry about — this doesn't influence render/snapshot/check output.

LGTM from my side.

— Review by Rames D Jusso

[jrusso1020]

Approving per the channel stamp-flow: Rames-D and Magi both cleared, CI clean at f3c3a15.

The base branch was changed.