Split from #490 (and originally from #468's scope note, whose pointer to "#462" was dangling — nothing ever implemented buffer persistence). Session restore now survives crashes and remembers every FILE-backed tab, docked or detached (#495), but a never-saved scratch query still vanishes on any exit: there is no path to write down, and its content is not persisted anywhere.
Doing this properly is a feature, not a mirror fix, which is why it stayed out of #495:
The #469 close prompts already guard every interactive discard route, so the residual loss today is scratch content on ABNORMAL exit only — real but narrow. The distinction between chose-to-discard and never-got-to-choose is the design center.
Split from #490 (and originally from #468's scope note, whose pointer to "#462" was dangling — nothing ever implemented buffer persistence). Session restore now survives crashes and remembers every FILE-backed tab, docked or detached (#495), but a never-saved scratch query still vanishes on any exit: there is no path to write down, and its content is not persisted anywhere.
Doing this properly is a feature, not a mirror fix, which is why it stayed out of #495:
The #469 close prompts already guard every interactive discard route, so the residual loss today is scratch content on ABNORMAL exit only — real but narrow. The distinction between chose-to-discard and never-got-to-choose is the design center.