[Bug] twitter search times out with zero output and no error on logged-in session

## Bug

`opencli twitter search ` on a logged-in session times out with zero output and no error message. The command hangs until timeout and dies silently.

## Repro

Three separate attempts (different queries, logged-in browser bridge up, `doctor` green) — all three timed out with no rows, no error, no hint about what failed. Retrying the identical command later produced the same silent timeout.

## Context

Related twitter read/write flakiness in the tracker: #1781 (timeout reported but post actually succeeded), #2255/#2256 (write exits 0 when nothing happened). The pattern: twitter commands fail without surfacing a failure mode.

## Why it matters

For read lanes the silent timeout is indistinguishable from 'no results' — an automation layer cannot tell an empty result from a dead session. The X API side is flaky (rate limits, session expiry) but the CLI currently hides which one happened.

## Suggestion

On timeout/empty: print the reason when it is known (session expired / rate limited / no results), and exit non-zero on hard failure. Happy to help with a repro dump if useful.

Start by reproducing `opencli twitter search ` with a logged-in browser bridge and confirm that `doctor` is green. Trace the timeout and empty-result handling from the Twitter search command, then verify that known session or rate-limit failures produce an error and non-zero exit status while genuine no-result searches remain distinguishable.

Written by the indexing model from the issue text.