Long Claude Code work, run as phases.

Phase Console plans the work, hands each phase to a fresh session, and keeps a board that reads what is actually done — from disk, never from memory.

Phase graph — checkout-rewrite5/5done

How a plan runs

Four moves. The fourth is what makes the other three worth trusting.

The plandone
Every phase declares what must finish before it can start. The graph is the plan — there is no cursor to keep.
A fresh sessiondone
Each phase gets its own session, sized to the model's window, so it never thins out mid-thought.
The handoffdone
A phase ends by writing the baton: state now, files changed, decisions, and the exact next commands.
The boarddone
Recomputed from the plan and the handoff files on disk, every time you look.

Nothing remembers your progress: The board is derived from the dependency table and the handoff files, so out-of-order and resumed work stay correct.
Phases fan out: Finishing one phase can release several. Those touching different repositories go at the same time; those sharing one are serialized by a lock.
A phase that stops short is classified: The console reads why it stopped and climbs a bounded ladder of remedies, within caps in attempts and in dollars. Exhausted, it leaves you one errand.

One install, and one console per project. Change into a repository and start it; the others carry on.

macOS, Linux and WSL2. No runtime dependencies.