Agent Session Resume

Purpose

Resume or audit prior coding-agent work with continuity. Reconstruct what happened before acting, then continue from the real stopping point.

Run a provenance self-check.
- Run python3 skills/agent-session-resume/scripts/skill-provenance.py when available.
- Otherwise compare the loaded SKILL.md path and size against the known install paths under $HOME/.claude and ${CODEX_HOME:-$HOME/.codex}.
- Report staleness on the Loaded skill line of the resume report. Details: references/evidence-and-provenance.md.
Identify the source. If the user names a platform, read the matching file in references/; if the ask spans platforms, read references/cross-platform.md. Otherwise inspect the workspace for session folders, exports, summaries, and artifacts. When a session title is given, prefer exact or fuzzy title matches over recency.
Locate the transcript or best substitute. Prefer full transcripts over summaries, workspace-local session data over global history, and explicit user-provided paths over discovered paths.
Read the full available session record before acting. For large transcripts, inventory files, event types, and timestamps first, then read the evidence-bearing slices until the record is accounted for. Full coverage means no relevant evidence skipped; bounded searches and slices are fine for giant records, but say so and name the file/event. Do not edit files or repeat prior work before this pass is complete.