Hyperspace CLI v5.85.25 (macOS browser run zero-config + remote-access persists)

macOS browser fixes — hyperspace browser run now works on any Mac with Chrome, zero config.

• Find Chrome on macOS: the browser SDK probes /Applications/Google Chrome.app (+ Chromium / Canary / Brave, system + ~/Applications, and brew chromium). Before, it only searched PATH and failed with "no chromium on PATH" on every Mac. (#997)
• Cold-launch timeout: bumped to 20s on macOS — a first Chrome launch (Gatekeeper verification) can exceed the old 10s and spuriously fail. (#997)
• The bundled rusty-browser sidecar gets the same macOS Chrome discovery (#1107, agentic-os-prod).

Also: a node started with --remote-access now STAYS remote-access-enabled across an auto-update / launchd / reboot restart (it persists the intent to ~/.hyperspace/daemon-launch.json and replays it) — fixes the "comes back as an unreachable half-node after auto-update" regression. HYPERSPACE_REMOTE_ACCESS=0 still the kill switch. (#998)

Carries the ds4 auto-detect real-mode sidecar (5.85.24) + the full 5.85.x line.