moldavite-portabilitylisted

# Moldavite Portability Use Moldavite's app UI for archive, migration, and export operations. MCP does not expose import, export, restore, or backup tools. Never simulate a destructive replace import with note-by-note MCP writes. ## Choose the Right Operation | Goal | Operation | | --- | --- | | Portable Forge content archive | ZIP export | | Password-protected Forge copy | Encrypted `.moldavite-backup` export | | Add files without overwriting existing paths | Import with Merge | | Restore archive contents as primary notes | Import with Replace | | Share selected notes | Markdown, plaintext, or PDF export | | Move app preferences only | Settings JSON export/import | | Move from Obsidian | Built-in Obsidian importer | ## Safe Backup Workflow 1. Confirm source Forge and destination outside that Forge. 2. Choose encrypted export when archive privacy matters. 3. Keep the password separately; Moldavite cannot recover it. 4. Verify the output file exists and has plausible nonzero size. 5. Test restore into a disposable Forge when backup assurance matters. 6. Keep more than one generation before deleting source data. Forge archives include `daily/`, `weekly/`, `notes/`, `templates/`, and `images/`. They exclude app-managed indexes, trash, plugins, and root agent files. ## Merge vs Replace - **Merge** skips destination files that already exist. It is safer for combining content but does not reconcile two versions of the same path. - **Replace** clears destination daily, weekl