Reposition README: local black box recorder for Codex CLI

[kkrlstrm]

Repositions the repo around its actual insight instead of a generic "telemetry" framing.

Why

The old headline read "Telemetry for the OpenAI Codex CLI — the sibling of cc-logger." Accurate but generic, and it buried the sharpest point: Codex hooks are incomplete (on the build tested, PreToolUse/PostToolUse fire for shell only), so this tool bypasses hooks and reconstructs the full run — apply_patch, MCP calls, subagents — from the rollout files Codex already writes. That's the wedge, and it now leads.

What changed

• New H1 + tagline — "The local black box recorder for OpenAI Codex CLI," full-fidelity local observability.
• Pain-first structure — "Why this exists: hooks are not enough" comes before the cc-logger sibling relationship.
• Real proof — actual codex-logger stats output up top (apply_patch / write_stdin counts that hooks would miss), plus sessions/inspect examples.
• "Questions it helps answer" section to make the value concrete.
• Copy-paste SQL for the three most common questions (top cost, tool failure rate, subagent share).
• Capability comparison table (hooks vs cloud tracing plugin vs codex-logger) with a caveat that the hooks row is version-specific.
• "Where this fits" — the local agent-ops stack (cc-logger / agent-guard / codex-logger).
• Softened the version-pinned hook claim so a future Codex release that changes hook coverage can't make the headline read as wrong.
• Updated the pyproject.toml package description to match.

Docs only — no code changes. Stats/sessions output in the README is real (ingested from local Codex history); the inspect block is sanitized/illustrative to avoid leaking real paths.

🤖 Generated with Claude Code