v0.1.1 — Adaptive review timeouts

Watchdog expiry is now a mandatory review point rather than an automatic stop.

• The main conversation selects a rolling no-progress threshold by task class: 180/300/600/900/1800 seconds or a justified custom value.
• Healthy current evidence—such as advancing scans, fresh stream/log/tool-call records, changing files, active process work, or worker phase changes—can heartbeat the exact tag and continue indefinitely.
• A static Thinking label or timer tick alone is not evidence.
• Explicit image-generation attempts retain their separate 180-second hard watchdog.
• The CLI fallback for an omitted manual timeout is now 300 seconds.
• Added timeout-policy documentation and regression coverage for stalled-to-armed review recovery.

v0.1.0 — Initial public release

Initial public release of the Windows-first, local-first Codex Task Watchdog.

Highlights:

• read-only Codex Desktop event-state monitoring for stalled responses and tool calls;
• exact arm/heartbeat/disarm tags for long-running and parallel attempts;
• oversized-task health diagnosis and metadata-only recovery manifests;
• bounded watchdog-only cleanup and conservative no-automatic-retry safety model;
• installable Codex skill, PowerShell installer, schemas, documentation, and 26 tests.

No runtime logs, session data, credentials, user paths, or recovery records are included.