The durable task vs. disposable session distinction is the real insight here. A lot of orchestration complexity comes from treating those as the same lifecycle.

The checkpoint approach is especially solid: carrying forward Git state, tests, contract hash, and worktree state instead of asking a fresh model to trust a prose summary. That makes context rotation an execution concern rather than a correctness risk.

I’d frame this as a useful rule for agent orchestration: business work should have a durable identity; model sessions should be disposable.