LowNotes v0.3.4

✨ Features

• Persistent history and trash — History and trash in the sidebar keeps note versions and deleted notes or folders available after restarting LowNotes. Restore a selected deletion with its assets and collaborative history; if its old filename is occupied, restoration chooses another name instead of overwriting the new note.
• Compare and restore Markdown — compare an earlier version or another note, including a conflict copy, with the current Markdown. Choose either text, combine them or edit the result before applying it as a new collaborative edit. If the note changes during comparison, refresh it without losing your combined result.
• References follow renames and moves — stable note identities preserve collaborative history and map relationships when notes or folders move. Local Markdown links, reference definitions and wikilinks are updated while retaining labels, aliases, titles, anchors and code examples; relative paths also follow local assets.
• Credentials in the system store — provider keys and pairing identities move out of the preferences JSON into Windows Credential Manager, macOS Keychain or Linux Secret Service. Migration verifies stored credentials before removing the old copies, and unavailable stores show a retry action while notes remain usable.

🔧 Improvements

• Reliable offline structural changes — paired devices exchange durable creation, movement and deletion records before synchronizing note content. Deleted notes do not silently return when an offline peer reconnects; concurrent edits remain available for review, and a new note at an old filename has its own identity.
• Map changes merge across devices — distinct manual and assistant links created offline are retained regardless of file timestamps. Removing a relation records its observed additions, preventing stale lists from bringing it back. Relationships follow their original note identities through moves and explicit restoration.
• Configurable local retention — recovery data is kept forever by default. History and trash → Retention offers optional day limits, periodic cleanup and a preview before manual removal. Archives awaiting acknowledgement from paired devices, external recovery files and unsafe or incomplete archives stay protected; image blobs and structural deletion records are retained.

🐛 Bug fixes

• Recovery after interrupted writes — atomic replacement, validated backups and durable transactions coordinate Markdown with its collaborative state during saves, creation, moves and link removal. Reopening completes recoverable operations, preserves conflicting external files and reports recovery instead of silently discarding data.
• Consistent received and externally edited notes — legacy Markdown transfers save text and collaborative state together. Cached documents import recovered history before interpreting external edits, and synchronization imports external Markdown before comparing manifests, preventing duplicated text and overlooked changes.
• Removing links preserves collaborative history — unlinking map relations keeps their visible text through a coordinated Markdown edit and updates the open editor. Recovery follows note identities and rechecks the current text before completing interrupted changes.

📝 Documentation

• Synchronization and recovery guidance — documented note identities, conflict copies, local versions, retention and backup requirements. Update both paired devices to v0.3.4 for complete offline structural convergence; older clients retain compatible note synchronization but do not exchange durable structural changes. History and trash remain local to each device.
• Regression checks before publishing — PRs and pushes to the main branch verify Rust, frontend, native credentials and interface behavior on Windows, Linux and macOS. Release builds also require native Rust and interface regressions, including offline changes, abrupt-process recovery and collaborative restoration.