Seer SnowBrowser v3.0.0

Seer SnowBrowser v3.0.0 Release Notes

Status

This document defines the v3.0.0 release payload. The v3.0.0 tag and GitHub Release are the authoritative publication record.

Highlights

Operational Console

• Rebuilt the authenticated local Console as a Chinese-first operational workbench with clearer run, project, Profile, and Doctor workspaces.
• Added responsive wide-screen run/detail composition, 390-pixel history cards, stable keyboard focus, centralized status/error language, and reduced redraw during polling.
• Separated selected-run resources, shell resources, confirmation control, store state, and views behind finite browser-side interfaces without widening backend authority.

Reliable Cancellation And Cleanup

• Propagated cancellation through MCP, the authenticated control channel, command/API adapters, Extension DevTools, and configured Puppeteer extension reload.
• Cancelled extension reloads no longer start late worker-readiness probes, wake pages, breakpoint restoration, or reattachment after RUN_INTERRUPTED is returned.
• Cancellation errors remain bounded and never expose the caller's AbortSignal.reason; owned CDP sessions, pages, sockets, response bodies, and process trees retain explicit cleanup.
• Awaited transfer publication, Playwright cleanup, and scenario-step timeouts remain live until settlement, preventing Node.js 22 from exiting while a deadline is the only remaining event-loop handle.

Deeper Runtime Boundaries

• Added strict shared capability request contracts while leaving Playwright and Puppeteer native application, observation, and rollback inside their adapters.
• Added process-local MCP batch ownership, finite MCP request parsing, capability ports, and a standalone protocol surface while preserving the existing twenty-tool manifest v2 contract.
• Added persisted browser diagnostic correlation, bounded run summaries/benchmarks, immutable transfer publication/snapshot modules, and exact Profile lock/directory identity contracts.

Supported Runtime And Dependency Security

• Raised the minimum supported runtime to Node.js 22.12 because Node.js 20 is end-of-life upstream.
• Upgraded the exact Puppeteer Core dependency from 24.43.1 to 25.8.0, removing the vulnerable legacy extract-zip dependency chain reported by npm audit.
• Moved Windows CI to Node.js 22 while retaining locked dependency installation, read-only workflow permissions, unit/MCP tests, and entrypoint validation.

Windows Product Polish

• Added original PNG/ICO branding and a guarded shortcut installer for both the Windows desktop and a project-root fallback.

Compatibility And Safety

• The Node.js runtime floor changes from 20 to 22.12, which is the intentional breaking change reflected by the v3 major version. Upgrade Node.js before installing this release.
• Version 1 and version 2 configurations, the twenty MCP tools, named persistent Profiles, and both runtime lanes remain compatible without configuration migration.
• The release does not add real external-write approval, Profile reset, isolated Profile, arbitrary CDP, daily-Chrome attachment, registry mutation, arbitrary file access, or remote administration.
• Historical BrowserDebug references remain only where required for provenance or v2.0 migration guidance.

Upgrade

Install Node.js 22.12 or newer, pull or download v3.0.0, run npm install, and continue using the existing scripts\run-seer-snowbrowser.ps1 wrapper. To install the branded launcher, run scripts\install-desktop-shortcut.ps1; add -Destination ProjectRoot for the local fallback icon.

Verification

Release acceptance and exact local evidence are recorded in ACCEPTANCE.md. No binary release asset is required; GitHub source archives and the repository installation workflow remain canonical.