Retrospective development diary · Week beginning 2026-08-24. Written in September 2026 from the project history; this is not an original publication date or a release announcement.
The late-August checkpoint gathered a substantial expansion of import support. QueVault could recognise more password-manager and browser exports, including native 1Password .1pux data and formats from Bitwarden, Proton Pass, Dashlane, Keeper and LastPass. This was a natural consequence of becoming a broader vault: useful information already lives in several different places.
The interesting part was what happened when those places overlapped. Duplicate review offered comparisons and choices to merge, retain an existing record, use the imported record or keep both. Manual merging also made it possible to bring related records together after import. The goal was to consolidate useful details without silently throwing away the differences.
Backup work developed alongside that. Guided setup made it easier to create a first backup, and a new backup was decoded for verification before becoming a restore point. Unchanged automatic copies could be skipped, keeping retained versions more useful.
These changes were recorded together in the 24 August checkpoint; some may have been developed earlier between commits. They describe the development build, not a dated App Store launch. Together they show the next challenge after broadening the vault: making the move into it understandable, and keeping a dependable route back.