v0.2.2

Codex plan usage was labelled wrong on every account whose plan has no
five-hour window. Codex publishes the length of each window and we ignored
it, so a seven-day window was drawn as 5h and the 7d row never appeared.
Both data sources now route by the published length; older Codex builds,
which send no length, keep behaving exactly as they did.

The header lookup also went silent whenever a Codex session read or edited
the agent-watcher source, because it accepted any log row that merely
mentioned the header name -- including Codex echoing that source back. It
now scans a bounded number of rows and takes the first that parses.

Two tests cover ground 0.2.0 left open: shutdown with an agent actually
bound, which is the half that can leak threads, and the
enable-claude-bridge invocation, whose failure mode is silent -- the
generated hooks would call a subcommand that does not exist and exit zero.

Known, unrelated, and not fixed here: Kimi plan usage stops after its OAuth
token expires. The fetcher reads access_token without checking
expires_at and never refreshes, and the failure is logged below the
default level, so the bars just stop.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

Full Changelog: v0.2.1...v0.2.2