19c8eb846e
* claim: #6550 * Crash reports: keep journaling through file.new and doc.open (#6550) `Session::replace_design` swapped in the fresh session without its `crash_journal` flag, and the app turns it back on only at its next frame. So `file.new`/`doc.open` never recorded how they ended, the commands sent after them in the same frame (a control-channel or MCP batch) were not journaled, and a crash report then named `file.new` as the command in flight. `replace_design` now keeps the flag, like the other session-wide fields it keeps; only the design on screen has it set. Test: `commands_right_after_a_new_design_are_journaled` (crash_tests.rs). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>