fix: capture all network requests including document navigations

[juliobrasa]

Summary

network requests only captured XHR/fetch calls because request tracking was activated on-demand when the user first ran the command. Navigations occurring before that call were never recorded.

Root cause

startRequestTracking() registered a page.on('request') listener only when called explicitly. Document navigations (page loads, redirects, form submissions) that occurred before the user ran network requests were invisible.

Fix

Move request tracking into setupPageTracking() so it is always active for every page from creation. This captures all network activity:

• Document navigations
• Redirect chains (3xx)
• Resource loads (scripts, stylesheets, images)
• XHR/fetch (as before)

startRequestTracking() is kept as a no-op for backwards compatibility.

Before

agent-browser open https://example.com
agent-browser click @e1  # navigates to /other-page
agent-browser network requests
# (empty)

After

agent-browser open https://example.com
agent-browser click @e1  # navigates to /other-page
agent-browser network requests
# GET https://example.com/other-page (document)

Test plan

• TypeScript compiles without errors
• network requests captures document navigations
• network requests --filter still works for filtering

Closes #555

🤖 Generated with Claude Code

[vercel]

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

A member of the Team first needs to authorize it.