What changed

Closes #87.

This adds a self-hosted console_logs debug tool for browser-agent runs:

• captures browser console messages and pageerror events when a Browserbase session starts
• keeps a bounded per-session in-memory buffer so long-running sessions do not grow unbounded
• exposes recent logs through MCP with limit, types, and clear options
• detaches page listeners during session cleanup
• documents the new debug flow in the README
• adds a changeset for the user-visible tool addition

Why

When an agent drives a browser through MCP, many failures happen on the page side: hydration errors, failed chunks, blocked scripts, app-level warnings, etc. Without console/page-error access, the MCP client can see that an action or extraction failed but not the client-side reason.

This gives self-hosted users a lightweight debug surface without adding an external observability dependency or changing the hosted-tool parity for the existing browser automation tools.

Validation

• ./node_modules/.bin/tsc --noEmit
• ./node_modules/.bin/eslint src/consoleTelemetry.ts src/consoleTelemetry.test.ts src/sessionManager.ts src/types/types.ts src/tools/consoleLogs.ts src/tools/index.ts src/tools/__tests__/tools.test.ts tests/smoke.test.ts
• git diff --check

I also added focused Vitest coverage for the telemetry buffer and tool registry. Vitest itself could not start on my macOS checkout because the downloaded Rolldown native binding is rejected by the local code-signing policy before tests load; CI should run those tests in its normal environment.