The retry remembers the timeline it erased

An agent attempt fails, and you restore the snapshot. The disk rolls back: including the logs of the attempt. The evidence of what went wrong lives in the timeline you're about to erase.

So the orchestrator reads before it rewinds. GET /api/v1/agent/logs, filtered by level and time, returns the failed run's trace: the command that hung, the test that broke, the error nobody caught. The orchestrator holds that trace, restores the snapshot, and dispatches the retry: with the trace in the prompt.

The machine comes back in the same morning with no memory of yesterday. The agent driving it remembers everything, so attempt three doesn't repeat attempt one's mistake.

The environment resets; the lesson doesn't.