fix(intercept): IIFE wrapping for installInterceptor/getInterceptedRequests

[Astro-Han]

Summary

Fixes #98 — INTERCEPT strategy commands fail to capture data.

1. Interceptor pipeline fix (page.ts)

Root cause: installInterceptor() and getInterceptedRequests() were changed from this.evaluate() to direct sendCommand('exec') during the daemon migration. This bypassed wrapForEval(), so CDP received bare arrow functions that were defined but never invoked.

Fix: restore this.evaluate() for both methods, so wrapForEval() wraps the arrow function as an IIFE (code)().

2. Twitter adapter fixes (followers, following, search, notifications)

With the interceptor pipeline working, discovered three additional issues preventing data capture:

• SPA navigation: page.goto() resets JS context, losing the installed interceptor. Changed to install interceptor first, then navigate via SPA (click for followers/following, pushState+popstate for search/notifications) to preserve JS context.
• Data path: GraphQL response is { data: { user: ... } }, not { data: { data: { user: ... } } }. Removed the extra .data level.
• Author resolution: Twitter moved screen_name from legacy to core. Updated to try core.screen_name first with legacy fallback.
• Selector update: Twitter changed /followers to /verified_followers.

3. Security hardening

• JSON.stringify for all user input interpolated into evaluate() JS strings
• Navigation validation: throw on SPA navigation failure instead of silent empty return

Also removed erroneous .filter(r => r?.url?.includes('Followers')) in followers.ts — interceptor stores response body JSON (no url field), pattern filtering happens at capture time.

Test plan

• npm run typecheck passes
• npx vitest run src/ — 213 unit tests pass
• twitter followers --user elonmusk --limit 5 — returns data
• twitter following --user elonmusk --limit 5 — returns data
• twitter search --query "opencli" --limit 5 — returns data with correct author
• twitter search --query "it's a test" — single quote in query handled safely
• twitter notifications --limit 5 — returns data

[jackwener]

Thanks for the contribution. This was a very helpful fix. Restoring the interceptor path in page.ts addresses the actual regression from the daemon migration, and the follow-up Twitter adapter updates make the INTERCEPT commands usable again on the current X frontend. I especially appreciated the careful notes in the PR description and the extra hardening around SPA navigation and JSON.stringify for injected values.

[Astro-Han]

Thank you! Glad the investigation into the IIFE wrapping root cause was useful. Debugging the SPA navigation was a fun puzzle — the pushState + popstate trick for search/notifications and the verified_followers selector change were unexpected discoveries along the way.

Note: the upstream search.ts uses the search-input approach for SPA navigation. I kept that as-is and only added the core.screen_name author fix on top — should be a clean merge with future changes to that file.

Happy to help with more adapters if needed!