feat(verify): per-pair cursor + last-touched pair ordering #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "worktree-verify-pair-cursor"
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?
Summary
cursor_side,cursor_rel) pluslast_touched_atin~/Library/Application Support/backup/verify-state/<key>.jsonand resumes interrupted scans where they stopped instead of restarting
alphabetically.
last_touched_atascending at the start of everyverify-allrun (None = oldest), so no pair starves another inbudget-limited environments.
deactivate --purgeremoves verify-state alongside fsevents-state.Implements the spec in
docs/superpowers/plans/2026-05-20-verify-pair-cursor.md.
Closes the starvation gap where large pairs at the end of the config
or files at the alphabetical tail could go indefinitely unverified.
Test Plan
confirm
pair order: <oldest>(touched=...), ...log line and thatverify-state JSON files appear under
~/Library/Application Support/backup/verify-state/confirm scan continues at saved cursor (look for
scan src: seen=N hashed=Kwith low N relative to the tree size)
deactivate --purge: confirm both fsevents-state andverify-state files are removed for the drive's pairs