fix(store): hold session texts whose set-aside fails, never overwrite them

This commit is contained in:
bchanot committed 2026-10-14 23:11:59 +02:00
1 parent 1312b366b1
commit e34b7f282e
19 files changed
+1093 -86

No files matched your search

+1
View File
@@ -12,6 +12,7 @@ Versions follow [Semantic Versioning](https://semver.org/).
### Fixed (maintenance after R2, 2026-10-14)
- **Session texts never lost when the browser storage is full.** A draft or archive the running build cannot read, and that cannot be set aside (storage full, or the quarantine slot already holds an earlier text, which is no longer replaced), now stays where it is: nothing is opened over it, and the editor shows a resolution panel with an exact copy to download, a permanent deletion or (for a draft to adapt to the current sheet) the adapted version, each behind a confirmation, and a retry. "New report" and "Import" refuse to start while such a text is held and send the practitioner to that panel; they also read a draft the page never opened before replacing it, so an unreadable one is set aside first. An unreadable draft is set aside together with the archive kept beside it. The draft mirror no longer reacts to unrelated store changes, and a refused draft write shows a storage-full banner in the editor. No change for a readable session.
- `supabase/.temp/cli-latest` (the Supabase CLI's version-check cache) is no longer tracked: it had been committed before the `supabase/.temp/` ignore rule existed, so every CLI run dirtied the tree. The local copy stays; the ignore rules already cover `.temp/`, `.branches/` and `supabase/.env.*`.
### Changed (Rust R2, domain core, 2026-10-14)