Clarify browser timeout continuation semantics

[MagMueller]

Summary

• state explicitly that a timed-out browser_execute invocation cannot issue further CDP commands
• clarify that this does not close the shared CDP connection
• mirror the same distinction in the browser skill

This changes guidance and error wording only. Timeout isolation and recovery behavior are unchanged.

Testing

• targeted browser timeout/session regressions: 25 passed, 6 environment-dependent skipped
• bun run typecheck in packages/bcode-browser
• repository pre-push typecheck (17 packages)

---

Summary by cubic

Clarify timeout semantics for browser_execute: a timed-out call can’t issue more CDP commands, but the CDP session stays open and the next browser_execute continues on the same connection/target; the last command from the timed-out call may still complete. Updated the timeout error text in packages/bcode-browser/src/browser-execute.ts and the guidance in packages/bcode-browser/skills/browser-execute/SKILL.md; no behavior changes.

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

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}