Evidence record / eve
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-eve-local-development-recovery-becomes-explicit-rather-than-automatic
Local development recovery becomes explicit rather than automatic. Earlier local-development invocations remain dormant by default. eve dev --resume attempts retained-snapshot recovery even after framework or authored source changes, and replay may perform work before failing. Missing snapshots are cancelled; malformed generation metadata remains dormant. Requests to dormant conversations fail explicitly.
Channel: tagged-release. Half: both. Date: 2026-09-28 (eve@0.68.0).
Operator consequence: Choose recovery deliberately after a development restart and review source changes and possible effects before using --resume. A durable architecture is not a promise of automatic local restart recovery or side-effect-free replay.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-eve-local-development-recovery-becomes-explicit-rather-than-automatic
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact