Seer SnowBrowser v2.0.0 — Canonical Cutover

Seer SnowBrowser v2.0.0 Release Notes

Status

Accepted for publication. v2.0.0 is the current canonical release and has completed the documented local and repository-rename acceptance gates. The final commit/tag/push/GitHub Release sequence is a separate transactional publication step; this record does not assert that those operations have already occurred.

Canonical-Only Cutover

v2.0.0 makes Seer SnowBrowser / 雪花浏览器 the sole live product identity. The canonical entrypoints are seer-snowbrowser and seer-snowbrowser-mcp; live configuration, MCP tools/resources, Console branding, runtime evidence, profiles, registries, and AppData resolution use the SeerSnowBrowser identity. BrowserDebug terminology remains only where historical provenance or migration evidence requires it; it is not a supported live compatibility alias.

This is a breaking change for scripts, MCP host configurations, configuration filenames, profile/artifact paths, and integrations that still invoke or resolve BrowserDebug names. Update those consumers to the canonical names before adopting v2.0.0.

Browser Workspace Enhancements

• Parallel pages on a shared profile: eligible explicitly non-external-write page scenarios can run as bounded Page Workers under one Profile Owner. They share authenticated state while retaining deterministic result order and owned cleanup. The explicit declaration is a consequence gate, not a static proof that a browser interaction is side-effect-free.
• Extension Workspace and MV3: version 2 supports up to 16 uniquely named unpacked MV3 extensions on the explicit puppeteer-chrome lane with equivalent substitution disabled. Tests select an extension by logical name; workspace preflight verifies the installed extension, worker, and page identity.
• MCP background batches: the stdio MCP server exposes bounded background job/batch controls, exact configured-test sharding, named shared-profile pools, pending-only cancellation, and continue/fail-fast behavior. It defaults to unattended gating: isolation or real external writes become blocked instead of opening a prompt.

Migration and Safety Limits

• The canonical repository, .git metadata, %LOCALAPPDATA%\SeerSnowBrowser storage, and migration receipts are present. The prior %LOCALAPPDATA%\BrowserDebug root, four legacy .browserdebug directories, and .SeerSnowBrowser.git-link.pre-migration pointer are absent.
• <legacy-repo-root> still exists outside the GitHub release tree, but its access/ACL enumeration is denied in the available environment. The user explicitly deferred its deletion. This makes the local Phase 005 deletion contract incomplete/deferred; it is an accepted local-release exception, not evidence that the legacy root was removed.
• No release process may infer authority to delete that external directory. If the user later authorizes it, re-resolve the exact path and repeat fresh preservation, quiescence, and canonical-health checks before any deletion.
• Shared profiles are persistent and not a sandbox. Isolated profiles, profile reset, and real external writes remain independently confirmation-gated; MCP does not expose arbitrary file access, registry mutation, reusable approval, or active-job force termination.

Validation

Release gates and exact evidence are recorded in ACCEPTANCE.md: package/lock metadata is 2.0.0; @modelcontextprotocol/sdk is 1.30.0; npm audit reported zero vulnerabilities; and the final Windows validation completed with 946 total tests (944 passed, 0 failed, 2 documented skips), MCP 24/24, a standalone MV3 probe, Doctor, a cleaned full-stack run, inspected screenshot, package dry-run, and forbidden-content checks. No real external write, profile reset, or product-isolated run was used.

The public repository is Taurusxw/SeerSnowBrowser, with the MIT license, main default branch, canonical origin URL, and legacy URL redirect verified.