docs: clarify internal API fallback

CHANGELOG.md

@@ -8,7 +8,7 @@
 - Help output now documents config files and env vars.
 
 ### Fixed
-- `followers` now falls back to the legacy API when GraphQL returns 404.
+- `followers` now falls back to the internal v1.1 REST endpoint when GraphQL returns 404.
 
 ### Tests
 - Add regression test for global options in subcommand help.

docs/testing.md

@@ -25,3 +25,4 @@ Notes:
 - If you don't tweet, set `BIRD_LIVE_TWEET_ID` to a known tweet ID to use for `read/replies/thread`.
 - Optional: set `BIRD_LIVE_BOOKMARK_FOLDER_ID` to exercise `bookmarks --folder-id`.
 - `bird query-ids --fresh` live coverage: set `BIRD_LIVE_QUERY_IDS_FRESH=1`.
+- The live suite may hit internal X endpoints (v1.1 REST) as fallback; it still uses cookie auth (no developer API key).

src/lib/twitter-client-users.ts

@@ -409,7 +409,7 @@ export function withUsers<TBase extends AbstractConstructor<TwitterClientBase>>(
         }
 
         // GraphQL Followers regularly returns 404 (queryId churn / endpoint flakiness).
-        // Fallback to the legacy 1.1 endpoint so the CLI stays useful.
+        // Fallback to the internal v1.1 REST endpoint used by the web client (cookie-auth; no dev API key).
         const restAttempt = await this.getFollowersViaRest(userId, count);
         if (restAttempt.success) {
           return restAttempt;