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>
- Malformed model JSON is sent back for repair, then retried; a failed job
starts over once before it fails. Visitors can dismiss failed sets.
- Generated sets get a short distinct name and description; flashcards are
atomic and have no hints; standard study shows known/learning counts.
- Share links: "In progress" list, finished sets join the normal lists with a
"New" tag, plain progress steps, newest exam first.
- Share-link AI expires after a week, can be limited to the US or Arizona
(DB-IP Lite or Cloudflare headers) and is locked by abuse protection
(migration 8).
- The assistant never answers from general knowledge; MCP and web search
tools load without a manual test.
- Plain-text copy, no question count in exam mode, filler text removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pushes to v2 typecheck and test inside the Node 24 image via a new Dockerfile
test stage, build and smoke-test the production image as a fresh non-root
container, then publish :v2 and :v2-<sha>. Never touches V1's :latest.
Document the image tags and Unraid 99:100 volume ownership.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>