The /api/import/v1 endpoint, server/services/v1import.ts and its test are
gone; Settings already restores full V2 backups in that place. MIGRATION.md
now covers V1 JSON exports and running the old importer from history
(7125dec), plus moving data between V2 installs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings → Data → Import gets "Restore a full backup" in place of the V1
import row. The zip from "Download backup" is uploaded and replaces the
database, every setting and the uploaded files on the running server:
- the staged database is upgraded to this schema (newer backups are refused),
saved keys are re-encrypted for this server's key, interrupted jobs are
marked, and the restoring session is carried over;
- a pre-restore snapshot is written, running generations stop, and the file
is swapped under the open DB handle (DB.replaceWith); uploads and media are
copied into place and background work restarts.
The /api/import/v1 endpoint stays for the V1 cutover (docs/MIGRATION.md).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>