v0.0.3 — Restore daemon-created Codex terminal sessions

Codex terminal conversations originally created through the shared daemon are now captured after they are resumed locally, even when their transcript metadata says source=vscode. The transcript must identify codex-tui as its originator, and its session ID must still match the filename. Editor sessions, subagents, and ambiguous transcripts remain excluded.

• Added regression coverage for daemon-created terminal metadata and rejected non-terminal sources.
• Added recovery guidance for missing conversations and stale macOS data-access permissions after an update.
• Validated a real Warp restart on macOS: all 11 expected conversations (six Codex and five Claude Code) resumed exactly once, including a previously skipped daemon-created Codex conversation. Verification covered the new Warp lifetime, actual agent processes and transcript metadata, restore claims, and continued watcher capture.
• Validation: make test (go test -race ./... and go vet ./...) and GitHub CI.

Conversations still running through the shared Codex daemon cannot reliably be mapped to individual Warp panes. Start or resume them with --no-daemon so each terminal holds its own transcript. This release does not recover conversations that were never captured in a snapshot.

After updating, check System Settings → Privacy & Security → Files & Folders → Warp Restore → Data shared by Warp and affiliated apps. The locally signed app may need this permission enabled again. The README includes a scoped permission-reset procedure if macOS retains the previous app signature.

Downloads include macOS Apple Silicon and Intel binaries plus SHA256SUMS.