Summary
- Route browser-dependent work through the user's live session, not fresh automation.
- Classifies tasks as static-capable (fetchable without interaction) or browser-required (needs rendered state, interaction, or live session), then routes accordingly Covers logged-in dashboards, localhost apps, form uploads, DOM/iframe/Shadow DOM inspection, and anti-bot friction detection Maintains domain-specific site-pattern notes to avoid repeating failed assumptions and to document stable routes, login quirks, and interaction primitives Includes decision guides for iframe/lazy-load handling, media inspection, parallel page ownership, and recovery from stale selectors or navigation drift