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.

Seer SnowBrowser v2.2.0

Highlights

• Adds the audited Douyin favorites batch extension (1.1.0).
• Adds the bounded configured-extension runtime used by SeerApp.
• Enforces LF checkout bytes for the pinned extension so integrity hashes remain stable on Windows.
• Preserves fail-closed extension loading, bounded execution, and exact cleanup ownership.

Verification

• Release-scope tests: 80/80 passed.
• Real Chrome cross-repository smoke: plugin 1.1.0 loaded under SnowBrowser 2.2.0 with fingerprint 2368ce76df7eec3dd24783b4ed31f3ba719757dad255441f73c89410f428bde1; external writes remained disabled.
• Full suite: 989 passed; 9 Playwright-only tests were unavailable because the optional playwright package is not installed in this environment.

Seer SnowBrowser v2.1.0

Seer SnowBrowser v2.1.0 Release Notes

Status

Local implementation and recorded acceptance evidence define the v2.1.0 release payload. Publication state is determined by the signed repository history, v2.1.0 tag, and GitHub Release rather than asserted by this pre-tag document.

Extension DevTools Automation

v2.1.0 adds bounded DevTools automation for configured unpacked MV3 extensions. A named persistent Profile preserves authenticated state while CLI and MCP can start an owned debug-only Chrome session, inspect the configured extension Service Worker or page, discover scripts, reload the extension, manage logical breakpoints, pause/resume, project paused scopes, evaluate bounded expressions, and poll events.

The public surface adds CLI/MCP start_debug and extension_debug, with manifest v2 exposing exactly 20 tools. It intentionally remains scoped to configured logical extension names and contained resource paths: raw CDP, arbitrary target attachment, arbitrary file/shell access, extension-store behavior, Profile reset/isolation, and external-write bypass are not supported.

Lifecycle And Safety Limits

• Debug sessions use authenticated loopback control and wait for the owned capability before DevTools operations proceed.
• Reload verifies the configured manifest identity, restores logical breakpoints only for the exact configured extension, rolls back an unexpected different-ID installation, and prevents ghost breakpoints from a timed-out session entering a later one.
• Paused scope values and events are finite and redact secrets, paths, and private identities. Evaluation requests Chrome side-effect detection by default; side-effectful evaluation and conditional breakpoint conditions require current-run external-write authority.
• Obsolete offline migrator and legacy storage fields have been removed.

Runtime Cleanup

The ignored task10 runtime cleanup removed exactly 114 files / 1,381,518 bytes. It preserves node_modules, Profiles, artifacts, and history; no broader runtime or historical content is claimed removed.

Validation

Candidate evidence is recorded in ACCEPTANCE.md: changed-surface coverage passed 116/116; the final DevTools/adapter subset passed 43/43; real Chrome passed 1/1; MCP passed 29/29; and all 877 non-platform unit tests have current passing evidence. The standalone probe, Doctor, and full-stack fixture also passed.

The known pre-existing console-run-flow aggregate non-termination remains visible as residual verification risk. It prevents a claim that the monolithic integration aggregate completed, but does not invalidate the focused current-pass evidence above.

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.

BrowserDebug v1.2.0

BrowserDebug v1.2.0 Release Notes

One MCP, Multiple Explicit Projects

BrowserDebug v1.2.0 adds --registry mode. A single Codex or other MCP-host configuration can now discover and select projects already registered in the local BrowserDebug Console.

The MCP exposes only path-free logical project IDs. It cannot add/remove registry entries, accept an arbitrary target path, read arbitrary files, or bypass existing confirmation and ownership boundaries.

Public Interface

• New browserdebug_list_projects read-only tool.
• Optional projectId on project-specific tools; required in registry mode and backward-compatible in single-target mode.
• New project and project-run resources.
• MCP manifest schema v2, with the historical v1 schema retained as a read-only resource.

Compatibility

Existing --root <target> [--config <relative-config>] configurations continue to work without adding projectId. Registry mode is opt-in through --registry.

Validation

The release includes official MCP SDK client coverage for both single-target mode and one registry-mode server running two separately registered temporary projects. Full release-gate results are recorded in ACCEPTANCE.md.

BrowserDebug 1.1.0

BrowserDebug v1.1.0

BrowserDebug v1.1.0 adds a local stdio MCP Server so Codex and other MCP clients can discover and invoke the existing BrowserDebug control plane through a narrow, startup-scoped interface.

Highlights

• Added the browserdebug-mcp executable and src/mcp/ adapter over the existing run, catalog, event, profile, Doctor, Stop, confirmation, and cleanup modules.
• Added nine strict tools, eight static resources, one verified run resource template, stable annotations, and a common structured success/error envelope.
• Added a path-independent manifest command and schemas/browserdebug.mcp-manifest.schema.json for machine-readable discovery.
• Added focused unit coverage and a real official-client stdio integration test that starts the server, runs a local target, reads evidence, and closes cleanly.
• Added an independent Simplified Chinese user manual at README.zh-CN.md with reciprocal language switching.
• Added the canonical MCP contract in docs/API.md and synchronized architecture, development, changelog, progress, and documentation indexes.

Safety Boundaries

• Each MCP process is permanently scoped to one explicit startup target root and an in-root configuration.
• MCP exposes no arbitrary root, file access, physical run/profile path, owner PID, control token, native browser object, raw artifact bytes, reusable approval, or confirmation bypass.
• Runs always finalize. Real external writes, isolated profiles, and destructive profile reset retain separate fresh visible confirmation requirements.
• Stop continues to use authenticated normal cleanup and has no PID fallback.

Validation

• The focused MCP suite covers manifest validation, strict inputs, annotations, error redaction, resources, official-client stdio negotiation, real local execution, evidence reading, and cleanup.
• The full resolver-backed regression, legacy MV3 probe, dual-runtime Doctor, full-stack command/API/page/MV3 fixture, dependency audit, release hygiene scan, and residue checks are part of the v1.1.0 acceptance gate.
• A live Codex MCP connection discovered all nine tools and completed the full-stack fixture with verified evidence and cleanup.
• No real external-write validation is performed.

Compatibility

• Existing CLI, graphical console, configuration versions 1 and 2, Artifact v1/v2 readers, shared general profile behavior, and compatible legacy MV3 probe remain supported.
• The MCP protocol starts at manifest schema version 1 and requires Node.js 20 or newer.

Upgrade

Pull v1.1.0, run npm install, resolve the browser environment, and register browserdebug-mcp in the MCP client with an explicit --root target. Existing non-MCP workflows require no migration.

BrowserDebug 1.0.0

BrowserDebug v1.0.0

BrowserDebug v1.0.0 is the first public release of the Windows-first local
control plane for frontend, backend/API, web page, and unpacked Chrome MV3
extension testing.

Highlights

• One CLI owns service startup, browser execution, typed tests, evidence, and
  cleanup for each run.
• Playwright Chrome for Testing and Puppeteer-controlled real Chrome lanes.
• Persistent shared general and named profiles, plus freshly confirmed
  isolated profiles and external-write authority.
• Declarative page, API, command, authentication, upload/download, device,
  permission, network, and MV3 extension workflows.
• Authenticated loopback graphical console with project registration, live and
  historical runs, diagnostics, logs, verified artifacts, sensitive reveal,
  profile management, and authenticated Stop.
• Strict Artifact v1/v2 readers, evidence-linked diagnostics, bounded recovery,
  Windows Job Object ownership, and exact cleanup reporting.

Installation

git clone https://github.com/Taurusxw/BrowserDebug.git
cd BrowserDebug
npm install
. .\scripts\resolve-extension-runtime-env.ps1
.\scripts\run-browserdebug.ps1 doctor --json
.\scripts\run-browserdebug.ps1 console

Acceptance

• Fresh Windows suite: 840 total, 838 passed, 0 failed, 2 documented
  platform skips.
• Desktop 1280x720 and mobile 390x844 graphical-console QA passed.
• Real full-stack, API, web page, MV3, Playwright, Puppeteer, named profile,
  screenshot reveal, authenticated Stop, and cleanup flows passed.
• No real external write was performed during validation.

See release acceptance for the publication gate and residual
platform limits.