feat(cli): add official Homebrew distribution

[antonvishal]

Why

give macOS and Linux users a supported Homebrew installation path and keep the formula synchronized with Browse releases.

What

• brew install browserbase/tap/browse supported alongside npm
• tap formula stays synced automatically, only on browse releases
• brew installs get brew upgrade hint instead of npm i -g

How

Release job mints short-lived App token, regenerates formula from npm tarball checksum, pushes only on change.

One-time setup (maintainer):

• create browserbase/homebrew-tap
• grant release App Contents write on tap
• set BROWSERBASE_APP_ID (var) + BROWSERBASE_APP_PRIVATE_KEY (secret)
• enable macOS/Linux formula CI in tap

Reviewer testing:

• brew style/audit/install/test pass on generated formula
• publish browse-only release updates tap, other packages do not

---

Summary by cubic

Adds Homebrew as a supported install path for the browse CLI on macOS and Linux, so installs no longer require a Node toolchain. npm installs still work; the update notice now shows brew upgrade browserbase/tap/browse for Homebrew installs and keeps npm i -g browse@latest for npm installs.

Release automation

• The release workflow publishes a formula to browserbase/homebrew-tap whenever browse is published; releases of other packages don't touch the tap.
• The formula is built from the npm tarball checksum, prunes prebuilds for other platforms, and is only committed when its content changed.
• Requires one-time setup: create the tap repo, grant the release GitHub App Contents write access, and set the BROWSERBASE_APP_ID variable and BROWSERBASE_APP_PRIVATE_KEY secret.
• Docs and skill files now show both install paths and tell users to npm uninstall --global browse before switching to Homebrew.

^{Written for commit 8c81789. Summary will update on new commits.}

[changeset-bot]

🦋 Changeset detected

Latest commit: 8c81789

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
browse	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

This PR is from an external contributor and must be approved by a stagehand team member with write access before CI can run.
Approving the latest commit mirrors it into an internal PR owned by the approver.
If new commits are pushed later, the internal PR stays open but is marked stale until someone approves the latest external commit and refreshes it.