feat(organize): verify document bundles through move and undo

[seonghobae]

Problem and behavior

Individual organization could separate recordings from companion metadata, split application bundles, or propose protected agent state. Planning now retains those files, explains their status, and leaves files beyond the metadata-probe budget unplanned.

The UI can also preview an explicitly selected existing document folder and destination parent. Supported bundles are flat, contain at most 32 local regular files, and total at most 512 KiB. Plans and undo receipts bind member names, file identities, exact modification times, sizes, and content digests. New members or changed content prevent movement or undo. Recognized project ancestors, package/session boundaries, links, unavailable content, and cross-volume bundle moves are retained.

macOS same-volume moves use Foundation coordination and the shared exclusive rename primitive. The organizing validator runs inside the accessor, so a companion arriving after preflight prevents mutation. Structured receipt paths preserve filenames containing -> and decomposed Unicode names.

Validation

• 33 command tests passed, including whole-bundle movement/undo, late members, same-size/same-mtime content drift, and project-boundary retention.
• 47 shared safety tests passed through native macOS coordination.
• Svelte check: zero errors and warnings.
• Earlier regressions demonstrated failed filename round-trip and missing post-preflight validation before their fixes.
• The unchanged live cache-cleanup assertion failed in earlier runs and passed after adding diagnostics; its intermittent cause remains unverified and its protection was not weakened.

Integration and limits

Stacked on #345; protected checks and normal merge remain required. This is existing-folder preservation, not completed content/ontology classification. Recursive/larger bundles, crash-durable recovery, iCloud upload and cross-device confirmation, signed-app entitlement behavior, and deployment remain unfinished. Native test processes emitted sandbox-extension diagnostics despite successful movement and preservation assertions. Fixtures contain only generated test data; no real user folder was moved by these tests.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: bec7c1a3-68a4-4bfd-a366-b0f10df90a0b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}