Repository navigation
Return to the previous archive after the demo or a cancelled switch - #71
Conversation
- Exiting the demo reopens the saved archive that was open when it started; a demo started with nothing open still returns to setup. - Cancel on the Opening screen during a switch reopens the archive that was open before it. Startup Cancel, a Cancel while reopening, a switch begun with nothing open, or a previous archive forgotten meanwhile still return to setup, so Cancel never loops. - Reopening goes through switchArchive, so the Opening screen, Cancel, token checks and failure handling are unchanged. - Tests updated for the new behaviour plus the no-loop, nothing-open and forgotten-archive cases. Playbook, troubleshooting and CHANGELOG updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VAvgB9dNWtJBuNHAAxsPDH
|
Reviewed and pushed follow-up commit Fixed a cancellation race: a delayed saved-archive refresh could reopen the previous archive after a newer manual connection attempt. Both the refresh and automatic return now honor opening and connection tokens, captured before notifying listeners. The new regression fails against the original PR and passes with this fix. Corrected the demo privacy wording in the Playbook, README and setup guide: browsing stays local, but returning to a saved real archive reads credentials, contacts its server and may update its saved selection. Published 0.5.0 behavior is distinguished from this development change. Validation: clean Flutter analysis; all 420 Flutter tests and 225 Python tests pass; 250 local documentation links pass; privacy scan reports 0 items; whitespace check passes. No remaining blocker found in the host review. Follow-up CI must pass; the return/cancel recovery paths still need checking on the next device candidate. No merge, native build or publication performed. |
Owner decisions (2026-11-18): demo exit goes back to where you were; Cancel during a switch goes back to the previous archive.
Behaviour
Implementation
Reopening goes through
switchArchive, so the Opening screen, Cancel, the opening and connect token checks, the persistence lock and failure handling are all reused.exitDemonow returns aFuture; the UI callbacks are unchanged.Tests
flutter analyzeis clean andflutter testpasses (420 tests). check_docs, privacy_check, the Python tests andgit diff --checkpass.Docs
Playbook (demo mode and Cancel), troubleshooting and a CHANGELOG Unreleased entry.
Generated by Claude Code