audit 3: a restore is ended by its Resync, and half an archive is refused

The restore manifest was consumed as soon as its version was checked,
before store.Open and the Resync; a start that failed in between left a
data directory the next start took for an ordinary one (M1). openData now
runs CheckRestore, store.Open, the Resync, and only then ConsumeRestore.

A truncated archive had nothing to refuse it: the manifest is the first
entry, so a download cut short or a tar stopped by a damaged block was a
restore on half a database. Every archive now ends with data/contents.json,
the size and SHA-256 of each data/ file (deploy files are the operator's to
edit), and CheckRestore compares /data with it before the database is
opened, then renames it contents.checked.json so a start after a failed one
does not compare again unless the manifest changed.

Tests: a start whose Resync fails, then a start that resyncs and consumes;
an archive cut in the database, before the deploy files and in its last
entry (refused, database untouched, no -wal); a damaged key named; the
record's names confined to data/; the domain import of a cut plain export,
a cut and an altered .spde (refused, nothing created). e2e on the test
server: full_backup_restore now also sees contents.json in the archive and
gone after the first start, through the real entrypoint and daemons (all
pass, 762 s); go vet + go test of 24 packages pass there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/audit-2026-10-12.md

@@ -1074,11 +1074,24 @@ those after it move up one patch number each.
 
 ### Stage 3 — persistence and restore (M1–M5, L1–L4, L7) → `2.5.3`
 
-- [ ] **Consume the manifest after the resync succeeds** (`CheckRestore` reports;
+- [x] **Consume the manifest after the resync succeeds** (`CheckRestore` reports;
    `run` deletes after `resyncAfterRestore` returns nil). Test: Resync fails →
    manifest kept → second boot resyncs. And a corrupted or truncated archive
    is refused on restore and on import with its message, nothing half
    written (a row of review-2026-08-followups, placed here 2026-10-14). — **Opus**
+   *Done 2026-10-15:* `cmd/panel` `openData` runs CheckRestore, `store.Open`,
+   the Resync and then `backup.ConsumeRestore`. A truncated archive had
+   nothing to refuse it - the manifest is the first entry, so half an
+   archive was a restore on half a database: every archive now ends with
+   `data/contents.json` (size and SHA-256 of each `data/` file; the deploy
+   files are the operator's to edit), CheckRestore compares `/data` with it
+   before the database is opened and renames it `contents.checked.json`, so
+   a start after a failed one (which had the database open) does not compare
+   again unless the manifest changed. Tests: the start that fails, a cut in
+   the database / before the deploy files / in the last entry (database
+   untouched, no `-wal`), a damaged key named; the domain import of a cut
+   plain export, a cut and an altered `.spde` (each refused, nothing
+   created). The CLI's `-decrypt -o` is step 3.
 - [ ] **Indexes**: `idx_send_log_domain_created_at (domain_id, created_at)` —
    on the id column stage 2 adds, replacing `idx_send_log_domain`;
    partial `idx_send_log_queued (created_at) WHERE status = 'queued'`;