claude@clouddev1
3a40ae27e7
On launch an empty temp project is created but, by design (ADR-0015), auto-deleted on quit while still empty. The unconditional `write_last_project` at startup recorded that temp's path anyway, so a later `--resume` resolved to a since-deleted directory and printed a confusing "recorded project … no longer exists". All three resume-pointer writes are now gated on `!project.is_unmodified_temp()`: the startup write, the on-switch write (a `new`-command switch to a fresh temp no longer records it), and a new on-quit write. The quit write is where a launch-temp the user *filled with content* finally gets remembered — startup skipped it while it was still empty. An unmodified empty temp is deleted, never recorded; the two dispositions are mutually exclusive. The "no previous project" friendly error the user asked for already exists (`project.resume_no_previous`, wired in the resume resolution) — verified, no change needed. The gate predicate `is_unmodified_temp` is covered by existing integration tests. 1131 passing, clippy clean.