why

browse functions init still instructed users to upload the Stagehand extension from a hardcoded path inside node_modules. The public getExtensionArchive() helper lets them export the bundled ZIP without depending on the SDK's package layout.

what changed

• Export stagehand-extension.zip with getExtensionArchive() before uploading it in the initializer's next steps and generated starter comments.
• Update the deployment guide's starter example to match its existing export instructions.
• Add a Browse patch changeset.

test plan

• CLI build, changed-file formatting and lint, changeset validation, and Mintlify docs validation passed.
• All 81 Functions and cloud API contract tests passed.
• Initialized a fresh project with npm and published Stagehand 4.3.0, ran the exact generated export command, and verified the resulting ZIP contains a valid Manifest V3 extension. Confirmed the command matches the starter comments and deployment guide.

---

Summary by cubic

Updates browse functions init and the deployment guide so extension upload instructions use browse cloud extensions upload --stagehand instead of exporting the bundled ZIP or referencing a hardcoded node_modules path.

• Drops the node -e export command from the deployment guide's upload step.
• Adds --stagehand to the CLI skill examples and includes a patch changeset for browse.

why

PR 2 of 2, stacked on #3289. The parent adds browse cloud extensions upload --stagehand. This updates the user-facing instructions to use it.

what changed

• Update functions init template comment and nextSteps output
• Simplify deployment guide's extension upload step
• Add --stagehand example to CLI skill

test plan

• 505 CLI tests pass
• Build, lint, and formatting pass