Make agent-browser errors doc more descriptive

[shpeedle]

docs: clarify distinction between console and errors commands

Problem

The documentation for the console and errors commands was unclear about what each command captures. Users expected errors to show all errors including console.error() calls, but it only shows uncaught JavaScript exceptions.

This caused confusion when users would see errors in agent-browser console output but get empty results from agent-browser errors.

Solution

Updated the documentation in README.md to clarify:

• console - captures all console.* calls (log, error, warn, info)
• errors - captures only uncaught JavaScript exceptions (not console.error() calls)

Future Enhancement Suggestion

A useful follow-up feature would be adding type filtering to the console command:

agent-browser console --type error    # Only show console.error() messages
agent-browser console --type warning  # Only show console.warn() messages

This would make it easier to filter for specific message types without parsing the full output.

[vercel]

@shpeedle is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[ctate]

Nice, thank you!