v0.4.7 - Codex monitor fixes

[0.4.7] — 2026-05-09

Changed

• Codex Stop hook auto-refresh now uses an 80% verified-usage threshold instead
  of 90%, so Throughline can refresh before Codex native auto-compact while
  still staying above the monitor's 70% warning band. Estimate-only usage and
  estimated context windows still do not mutate the thread.
• Token monitor now discovers active Codex rollout files directly from
  ~/.codex/sessions/**/rollout-*.jsonl, so current Codex sessions appear even
  when the Codex Stop hook has not written a Throughline state file.
• Token monitor now displays Codex session ids as the raw first 8 thread-id
  characters (019e085c) instead of the confusing prefixed slice (codex:01).
  Codex in-flight turns still overlay transient output_tokens in the token
  count, but the model column no longer adds a separate live+<tokens> marker.

---

This release rolls up intermediate same-day patches that were published to npm but not individually tagged on GitHub:

[0.4.6] — 2026-05-09

Changed

• Codex monitor usage now overlays transient output_tokens while a Codex turn
  is open. During an in-flight turn the row displays input_tokens + output_tokens and marks the model with live+<tokens>; after task_complete
  the row drops back to verified input_tokens only.

[0.4.5] — 2026-05-09

Fixed

• VS Code detection now treats VSCODE_HANDLES_SIGPIPE as a VS Code-family
  environment signal. This lets throughline install provision the monitor task
  in Codex / VS Code sessions where TERM_PROGRAM, VSCODE_PID, and
  VSCODE_IPC_HOOK_CLI are absent.

[0.4.4] — 2026-05-09

Changed

• Token monitor now treats Claude transcript and Codex rollout files as live
  inputs. State-file usage snapshots remain a fallback, but the display and
  stale hiding no longer wait for Stop hook completion when the live files are
  still changing.
• throughline install now provisions or repairs the current project's VS Code
  Throughline Monitor task when running under VS Code / Cursor / VSCodium, so
  monitor auto-start setup no longer depends solely on the first hook event.

[0.4.3] — 2026-05-09

Changed

• Changed the installed Codex $throughline skill so bare $throughline runs
  the scripted current-thread refresh directly:
  throughline trim --execute --host codex --all --json. Doctor, dry-run,
  preflight, restore-safety analysis, host primitive audit, and fresh-thread
  handoff remain available only when explicitly requested instead of being the
  normal skill path.

[0.4.2] — 2026-05-09

Fixed

• Codex trim no longer falls back to the latest project session when --session
  is omitted. For --host codex, the default memory session is now the current
  Codex thread (codex:<thread_id> from --codex-thread-id,
  CODEX_THREAD_ID, or THROUGHLINE_CODEX_THREAD_ID), so Claude-side work
  cannot accidentally become the injected memory for a Codex rollback.