resumelisted

# Resuming Something interrupted the loop. **Your first job is to find out what actually happened, not to get going again** — because the cheapest-looking recovery action, re-dispatching a task whose agent is gone, is also the one that can destroy work nobody knew was there. `/devteam:run` already reconciles and recovers on startup. This exists because it does so *immediately*, and after an interruption the record and the tree can disagree in ways only a human can settle. **It also covers the planned handoff**, which is not an interruption at all: a session handing to a fresh one at a good stopping point, so the memory files reload near the top of the new context and the finished task's debris does not follow it. That case has a resource a crash does not — **the predecessor is still alive** — and §0 exists to use it before anything else. ## 0. If the previous session is still alive, ask it **Reconstruction is what you do when nobody is left to ask.** A handoff at a planned stopping point is a strictly better position than a crash, and this skill was written as though only the crash existed. So before reconstructing anything: **is the outgoing session still open?** `ListAgents` will say. If it is, message it — and keep it open until you are done, because once it closes you are back to reading files. **You drive, not it.** A written handoff can only contain what its author thought to include, and what an outgoing session thinks is important is a poor predictor of what an