chore(cli): prepare browse 0.9.7 release

Draft
SH
3mo ago
+114-6

BLUF

Prepare the smallest auditable release path for the tactical Browse Functions hotfix: publish only browse@0.9.7 from the legacy CLI line, through npm trusted publishing, after the full package test and packed-artifact smoke gates pass.

This PR is intentionally stacked on #2700 so reviewers see only release mechanics. Merge #2700 into v4-spike-cli first, then retarget this PR to v4-spike-cli; merging this PR will trigger the publish.

Why this path

  • packages/cli is no longer on main, so the normal main release job cannot consume its changeset.
  • A local/manual npm publish would bypass the repository's existing OIDC provenance path.
  • Running the monorepo-wide changeset publish from v4-spike-cli risks touching unrelated Stagehand v4 packages.
  • The existing npm trusted publisher recognizes .github/workflows/release.yml, so this adds a branch-gated Browse-only job to that workflow.

Changes

  • consume the tactical changeset and version Browse from 0.9.6 to 0.9.7
  • add a v4-spike-cli release path that can publish only the browse package
  • skip safely when the version already exists
  • lint, test, build, pack, inspect, and install-smoke the exact tarball before publishing it
  • publish that exact tarball with npm provenance and tag the release commit
  • keep the existing Stagehand TypeScript release job restricted to main

Validation

  • pnpm --filter browse lint
  • pnpm --filter browse test — 25 files, 367 tests passed
  • packed browse-0.9.7.tgz; verified package name/version
  • installed the tarball into a clean temporary directory
  • verified installed browse --version reports 0.9.7
  • verified installed browse functions --help exposes publish/dev/invoke/init
  • actionlint .github/workflows/release.yml
  • confirmed browse@0.9.7 is not present on npm

The live Functions E2E matrix for the exact tactical source is documented on #2700, including fresh scaffold install, local dev, cloud publish, synchronous invoke, asynchronous invoke/status, and API-key-based project inference.


Summary by cubic

Publishes browse@0.9.7 through a branch‑gated, provenance-enabled workflow to ship the Functions parity hotfix with an auditable path. Previously, the release workflow only published from main; now a v4-spike-cli job publishes only browse after tests and tarball smoke checks, leaving other packages and the main release path unchanged.

  • Bumps browse to 0.9.7 and updates its changelog; removes the consumed changeset.
  • Adds a Release Browse CLI job in .github/workflows/release.yml that runs only on v4-spike-cli.
  • Skips safely if the version already exists on npm.
  • Runs lint, tests, packs the exact tarball, verifies name/version, and smoke-installs to assert --version and functions help.
  • Publishes that tarball with npm provenance and tags the release. No migration required.