Resume interrupted work

What you'll get

A recovery view of everything that was mid-flight when a session ended, each item paired with the exact action that restarts it. Sessions die for ordinary reasons, a sleeping laptop, a full context window, a closed terminal mid-run, and none of those should cost you the work. The task log outlives the session, and this command reads it back into a plan.

The steps

1. Open a fresh session in the same folder, then ask.

/marg:resume

The folder matters, because the task log lives in your working directory and resume reads it from there. Run it elsewhere and it finds nothing.

2. Read the recovery view. Marg walks the task history, keeps only the latest state per task, and shows you the ones still in flight. Each comes with what it was, which team ran it, how far it got, and the one action that picks it back up.

3. Restart only what is worth restarting. Not everything earns a second life. A status check from yesterday can stay dead, while a half-finished pricing analysis is one re-spawn from a deliverable. Scan the view, choose what still matters, and trigger the action beside it.

What comes back

The view sorts in-flight work into four states, and the label tells you what kind of restart each needs. Pending means the task was registered for a batch but never started. In-progress means it was running when the lights went out. Partial means a specialist returned some of the work and flagged the rest. Incomplete means a specialist finished without reporting cleanly, so its output has to be re-run before you trust it. Read the label first, because it is the difference between collecting finished work and restarting unfinished work.

Variations

• After a long gap: resume doubles as archaeology. Returning to a project after two weeks, /marg:resume and /marg:status together rebuild your picture of where things stood faster than scrolling back through the transcript.
• Nothing was in flight: resume says so and points you to /marg:status to confirm. Failing that, describe what you were doing and Marg routes it fresh.

If something goes wrong

• "No active-tasks file in this directory": you are in a different folder than the interrupted session ran in. Move to the project folder and rerun.
• The interrupted task is not listed: it most likely finished before the cut-off, so its deliverable is in the prior session's transcript. Check /marg:status for its final state.
• Resume offers to re-run something you already have: trust your copy and skip it. When an interruption lands mid-write, the log can trail reality by a single step.