Resume, don't restart

A state file drops a bookmark after every completed stage. Simulate a crash, then re-run the command and watch where it actually picks up.

The problem this replaces

No bookmark, no memory

Five completed stages, thrown away by one crash. Every re-run pays for the same work twice.

How it works

The command doesn't know it crashed — it just reads the file and continues where it left off.

Notifications fire at the start and end of every stage and every gate — so you don't have to keep the terminal open to know where things stand.

See it in action

context, plan, build — done, saved → ⚡ crash → re-run the command → resumes at review

Lunch happened in between. The pipeline didn't notice.

So what

Close your laptop mid-run — pick it up after lunch.