Agent Browser Release

Preconditions

• npm run verify passes.
• GitHub Actions passes on the Mac mini runner.
• Release Please has opened a package-scoped release PR.
• The release PR updates packages/agent-browser/package.json, package-lock.json, .release-please-manifest.json, and packages/agent-browser/CHANGELOG.md.
• npm run check confirms package version metadata is in sync.

Publish

1. Merge the Release Please PR.
2. Release Please creates the GitHub release and tag.
3. The Release workflow runs npm run verify.
4. The Release workflow publishes @cmmd-center/agent-browser to GitHub Packages.
5. The Release workflow verifies the package version is available and posts to #agent-browser-releases.

Manual npm publish --workspace packages/agent-browser is reserved for emergency correction work. Do not use it for routine releases.

Post-Publish

• Verify clean install from GitHub Packages:

  npm view @cmmd-center/agent-browser@<version> version --registry=https://npm.pkg.github.com

• Update Forge dependency in a clean Forge branch only after the exact package version is visible in GitHub Packages.

• Open or update internal docs when install steps, API behavior, Forge integration, or operator behavior changed.

• Keep Agent Browser package docs internal. Do not publish install/API/Forge package docs to docs.cmmd.ai.

Forge Consumption Gate

Do not start or merge Forge integration against a local checkout, unpublished branch, or moving tag. Forge production work must pin an exact published @cmmd-center/agent-browser version and commit the package-manager lockfile change in the Forge repository.