Summary
Fix weak-storage compatibility, imports, metadata rescans and publication recovery while preserving sources when safe deletion cannot be proven. This also fixes manual companion imports and root availability after mount-local device numbers change.
Fixes #904.
Fixes #911.
Fixes #831.
Fixes #947.
Changes
Added
- Structured registration-recovery blockers and retry support.
- Durable registration-publication rollback and recovery, including anonymous journals and Copy/HardlinkCopy operations.
- Verified Organise batch journals and a consolidated migration for the publication evidence and recovery schema.
- Metadata-only refresh on weak storage without enrolling unsupported physical identity.
Changed
- Use live operation-local proofs and durable content/ownership journals rather than historical filesystem identity as operational authority. Retain sources when restart or unavailable proof prevents safe retirement.
- Resolve automatic case rules from native information or read-only observations of existing entries. Remove the case-confirmation prompt without creating filesystem probe files; unknown or conflicting rules still block affected writes.
- Bound open filesystem handles during large batches while revalidating content and ownership before destructive operations.
- Remove the obsolete frontend weak-storage deletion checkbox and save flow. Retain the deprecated API and persisted fields for upgrade compatibility; verified cleanup is authorized automatically by current storage capabilities and operation evidence.
Fixed
- CIFS root confirmation/path-change recovery blockers and metadata-rescan failures after restart.
- Persisted weak or historical physical identities incorrectly controlling current storage operations or granting deletion authority.
- Registration lifecycle and ownership-transition errors, including SQLite identity-observation timestamps and conditional physical-generation compensation.
- C...
Automated Canary build