twitter search fails with ClientTransaction error (whoami/user-posts work fine)

Running into a weird one - twitter search always fails, but whoami and user-posts work fine on the same setup.

Setup: Agent Reach 1.5.0, twitter-cli 0.8.5, installed with pip install --user --break-system-packages inside a non-root Docker container (node:22-slim, Python 3.11.2). Cookies set via TWITTER_AUTH_TOKEN/TWITTER_CT0 env vars, freshly exported from a real browser login.

twitter whoami and twitter user-posts <handle> both work and return correct data.

But any search, e.g.:

twitter search "Tesla" --json -n 3

always fails the same way regardless of the query:

WARNING twitter_cli.client: Failed to init ClientTransaction: 'NoneType' object has no attribute 'group'
{"ok": false, "schema_version": "1", "error": {"code": "not_found", "message": "Twitter API error (HTTP 404): Twitter API error 404: "}}

Interesting bit: that same ClientTransaction warning actually shows up on every call, including the ones that succeed — but only search blows up afterward with a 404. Looks like whatever computes the transaction ID (xclienttransaction dep, probably scraping/parsing something from x.com) is silently returning None now, and search is the only endpoint that actually enforces it.

Happy to grab -v debug output if that helps track it down. This is blocking keyword search for us specifically, account reads still fine.