aqua-listen: autosave keyed on kit id and clip ids, not the content hash #51
Loading…
Reference in a new issue
No description provided.
Delete branch "aqua/listen-autosave-key"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A page rebuild changed
kit.hash, so the autosave key (aqua-listen:<kit>:<hash>) changed and the listener lost all answers on reload (tract page 93312816 -> 7f6ad26e).aqua-listen.v2:<kit id>:<sorted clip ids>. Same clip ids = same kit = same save; a different clip-id set starts fresh and leaves the old entry untouched.aqua-listen:<kit>:<hash>save whose answers and pairs name only this kit's clips is adopted; an existing new-key save is never overwritten. Erase removes both so nothing resurrects.idA|idB. The pair value A/B/same is positional (A = first of the pair in the seed's order), so it is only stable while the manifest clip order is unchanged.logic.cjs(saveKey,pickLegacySave), 20 node tests;smoke.mjsgains a headless-Chromium persistence test (reload, rebuild with a different hash, migration, erase). Mutation check: reverting to the hash key fails the node test and three smoke checks.aqua/listen-export-fallbacks(889b018,84fc228) and a merge of main (92d4282).🤖 Generated with Claude Code