Skip to content

fix(motion): harden video-motion store migration - #124

Merged
brunoazoulay merged 2 commits into
mainfrom
fix/motion-migration-hardening
Oct 30, 2026
Merged

brunoazoulay merged 2 commits into
mainfrom
fix/motion-migration-hardening

Conversation

@brunoazoulay

Copy link
Copy Markdown
Collaborator

Summary

  • Harden the video-motion store migration: keys/ symlink + owner trust check before/after migration and on key read/create.
  • A migration failure blocks only Motion-scoped calls and reports the real cause.
  • Legacy + new layouts both present: new layout wins, legacy stays protected; banned.txt is the union of both.
  • Protected-pre detection only applies to pre events.
  • Release 0.1.113 (version bump + CHANGELOG in a separate commit).

Test plan

  • bunx tsc --noEmit exit 0
  • bun test test/motion-*.test.ts test/confirm-*.test.ts: 579 pass, 0 fail
  • Full suite: 3385 pass, 1 fail (multi-rdv-sim > 01-filesize-block-then-comply.json, pre-existing, fails identically on main)
  • CI green

Breaking changes

None

- keys/ directory symlink and owner trust check before and after
  migration and on key read/create
- a migration failure now blocks only Motion-scoped calls and shows
  the real cause
- when both legacy ~/.fuse-harness/motion and new
  ~/.fuse-harness/video-motion exist, the new layout wins and the
  legacy one stays protected
- banned.txt is the union of both layouts
- protected-pre detection only applies to `pre` events
@brunoazoulay
brunoazoulay merged commit 85fa53a into main Oct 30, 2026
1 check passed
@brunoazoulay
brunoazoulay deleted the fix/motion-migration-hardening branch October 30, 2026 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant