feat: add cursor pagination for thread replies

[Leechael]

Summary

• Add cursor-based pagination for /thread/:screen_name/:tweet_id via ?page=true and ?cursor=....
• Keep legacy ?max= behavior, now using TweetDetail bottom cursors instead of DOM scrolling.
• Fix CDP port handling and XHR capture for TweetDetail request headers.

Test Results

• npx tsc --noEmit --target ES2022 --module ESNext --moduleResolution Bundler --esModuleInterop --skipLibCheck src/actions/common/openPage.ts src/actions/twitter/readThread.ts
• curl /thread/rauchg/2058245330836271263?page=true -> 200, returns replies and nextCursor
• curl /thread/rauchg/2058245330836271263?cursor=<nextCursor> -> 200, returns next replies and nextCursor
• curl /thread/rauchg/2058245330836271263?max=120 -> 200, returns 120 replies
• prek not available: no prek.toml or .pre-commit-config.yaml found

Test Coverage

No automated test framework covers this path. Verified against live local CDP/X session.

Review Findings

No debug logging or secrets added. Pagination token exposes only X cursor returned by upstream.

---

Summary by cubic

Adds cursor-based pagination to thread replies for incremental loading. Replaces DOM scrolling with TweetDetail cursor fetches using captured headers, and surfaces cursor-fetch errors clearly.

• New Features

  • GET /thread/:screen_name/:tweet_id supports ?page=true and ?cursor=...; responses include nextCursor and hasMore.
  • ?max= still works; batches via bottom cursors until the limit.
  • Providing ?cursor=... fetches that page directly using the TweetDetail request template.

• Bug Fixes

  • Fixed CDP port handling by passing { port } to CDP.List and CDP.New.
  • Network monitor now emits XHR responses after load and includes requestHeaders for follow-up fetches.
  • Surfaced thread cursor fetch failures with clear errors when auth/ct0 are missing or upstream returns non-OK/invalid JSON.

^{Written for commit 1f8db23. Summary will update on new commits. Review in cubic}

[cubic-dev-ai]

1 issue found across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[Leechael]

Fixed the issue identified by cubic: cursor page fetch failures now throw explicit errors instead of returning an empty successful page, so auth/network failures are no longer hidden as pagination completion. Verified with targeted TypeScript check.