## What happened

The `omarchy.agents` bar widget collects and renders Codex's local token stats, but the live subscription limits section shows:

```text
CODEX LIMITS UNAVAILABLE
account/rateLimits/read
```

The generated record contains an empty plan and limits array:

```json
{
  "tierLabel": "",
  "limits": [],
  "usageStatusText": "Codex limits unavailable",
  "authHelpText": "account/rateLimits/read"
}
```

This is distinct from the older `-a untrusted` reports. Omarchy 4.0.2-1 correctly launches Codex with `-a on-request`; `initialize` and `account/read` both succeed. Only `account/rateLimits/read` times out.

## Expected

The widget should display the authenticated Codex plan and its rate-limit windows.

## Steps to reproduce

1. Install and authenticate Codex CLI 0.151.0.
2. Run:

   ```bash
   "$OMARCHY_PATH/bin/omarchy-agent-usage-update" --limits-only codex
   jq '{tierLabel,limits,usageStatusText,authHelpText}' \
     ~/.local/state/omarchy/agents/usage/codex.json
   ```

3. Observe the empty fields shown above.
4. Speak the same JSONL protocol directly to `codex -s read-only -a on-request app-server`. The server successfully returns `initialize`, an unsolicited `remoteControl/status/changed` notification, `account/read`, and eventually a populated response for `account/rateLimits/read`.

## Root cause

There are two fragile parts in `bin/omarchy-agent-usage-codex`:

1. The rate-limit request has a hard-coded four-second deadline:

   ```python
   limits_msg = rpc_request(proc, 3, "account/rateLimits/read", timeout=4)
   ```

   The response takes longer on this otherwise working installation.

2. `rpc_request()` combines `select()` on a buffered `TextIOWrapper` with `readline()`:

   ```python
   ready, _, _ = select.select([proc.stdout], [], [], 0.25)
   line = proc.stdout.readline()
   ```

   `readline()` may prefetch multiple JSONL messages into Python's user-space buffer. A later `select()` checks only the kernel file descriptor, so it can wait even though a complete response is already buffered. The app-server's unsolicited notification makes multiple interleaved lines normal rather than exceptional.

The thrown `TimeoutError(method)` is then rendered as the bare method name, which is why the panel shows `account/rateLimits/read` rather than a useful diagnostic.

## Verified workaround

A user-level override that made both changes fixed the widget:

- Read the subprocess fd with `os.read()` and maintain an explicit newline buffer, avoiding `TextIOWrapper`/`select()` desynchronization.
- Give `account/rateLimits/read` a 20-second timeout.

After that change, the same collector returns a populated plan and weekly rate-limit window. Reverting to the packaged reader reproduces the failure.

Suggested upstream fix: use an unbuffered fd reader, a dedicated reader thread/queue, or another JSONL transport that owns its buffering; also use a less aggressive rate-limit timeout and surface the exception type/stderr in the record.

## System details

- Omarchy: 4.0.2-1
- Codex CLI: 0.151.0 (installed via mise)
- Kernel: 7.1.9-arch1-2, x86_64
- Desktop: Hyprland 0.56.2 / Quickshell 0.3.1
- Hardware: Dell Latitude 7430, Intel Core i5-1235U, Intel Iris Xe