fix(graphql): refresh FALLBACK_QUERY_IDS against live twitter-openapi IDs (complements #79/#80)

[zaprogrammer]

Problem

tw search, tw feed, tw bookmarks, and most other read commands currently fail with HTTP 404 / Query: Unspecified against live X.

Root cause: X rotated nearly all GraphQL queryIds. The hardcoded FALLBACK_QUERY_IDS in twitter_cli/graphql.py have drifted (both the 0.8.5 release and current main are stale), so every request that depends on a fallback ID is rejected.

User-visible symptom reported in #78: twitter search returns 404 even with valid cookies, even with PRs #79 + #80 applied (those fix the x-client-transaction-id init; the queryId itself is also stale).

Fix

Refreshed 15 of 22 fallback IDs against the community-maintained twitter-openapi placeholder.json — the same source _fetch_from_github() already trusts at runtime (twitter_cli/graphql.py:TWITTER_OPENAPI_URL). So this is a snapshot of exactly what dynamic resolution would have fetched, just with the network call removed.

Ops rotated (stale → live):

Op	Status
HomeTimeline, HomeLatestTimeline, UserByScreenName, UserTweets, TweetDetail, Likes	rotated
SearchTimeline ✱	rotated (this is the one in #78)
Bookmarks, ListLatestTweetsTimeline, Followers, Following	rotated
CreateTweet, CreateRetweet, DeleteRetweet, TweetResultByRestId	rotated
DeleteTweet, FavoriteTweet, UnfavoriteTweet, CreateBookmark, DeleteBookmark	unchanged
BookmarkFoldersSlice, BookmarkFolderTimeline	no live value in upstream; kept as-is

Verification

End-to-end on a live account (cookies from ~/.agent-reach/twitter.env):

$ tw search "AI agents" --json -n 5 --type latest --since 2026-08-02
rc: 0, ok: true          ← previously: rc:1, HTTP 404

Test suite on this branch:

$ pytest tests/test_client.py
86 passed in 7.60s

tests/test_client.py::test_searchtimeline_fallback_query_id_regression updated to pin the new live ID — its original value (VhUd6vHVmLBcw0uX-6jMLA) was itself stale.

Relation to open PRs

• fix: send auth cookies when fetching x.com home for ClientTransaction init (fixes #78) #79 / fix: fetch authenticated /home for ClientTransaction init (new x-web frontend broke posting) #80 (fetch /home with auth cookies for ClientTransaction init): fixes the x-client-transaction-id header side.
• This PR: fixes the queryId side.

Both are needed for tw search to work — with only #79/#80 you'd get 404 on a stale queryId; with only this PR you'd get rejected for a missing/invalid transaction ID. I applied both locally to verify tw search end-to-end, but they review independently — whichever lands first unblocks half the failure, the second one finishes it.

Follow-up (not in this PR)

X rotates these IDs on a regular cadence. Long-term, consider seeding _cached_query_ids from the runtime-fetched placeholder.json before falling back to the hardcoded dict — currently _resolve_query_id(prefer_fallback=True) (the default) returns the hardcoded value immediately and never consults the live source, which is how this drift persisted. Added a comment atop FALLBACK_QUERY_IDS with the refresh URL.