fix(browserbase): handle optional command output

[NathanFlurry]

• Assert command output is present before parsing the Browserbase response.
• Restore the browserbase example typecheck under strict TypeScript settings.

[the-company-company]

Co · session: Fix agentos main CI (clippy 1.98 + browserbase types)

• Auto-fix ; feedback on this pull request flows to the session and gets addressed
• Review ; Co reviews new pushes

_{@co <ask> hands Co a task · @co mute pauses · @co archive ends the session}

[railway-app]

🚅 Environment agentos-pr-1970 in rivet-frontend has no services deployed.

[the-company-company]

🟠 1 medium-severity finding

_{Reviewed commit a9fcbc9.}

[the-company-company]

🟠 Medium · Capture the JSON response before parsing stdout

process.exec defaults to output.capture: "none"; the sidecar therefore returns stdout as undefined unless the caller opts in to capture it. The non-null assertion only hides that contract from TypeScript, and JSON.parse(stdout!) still throws whenever this example is run.

Pass output: { capture: "all" } with env for this call and the matching direct-client call (then retain an explicit assertion or guard as appropriate).

[the-company-company]

Fixed in 4f02710. Both Browserbase client examples now request output: { capture: "all" } and fail clearly if the command still returns no stdout. pnpm --dir examples/browserbase check-types passes.

[the-company-company]

✅ No issues found

_{Reviewed commit 4f02710.}