What Problem This Solves

SQLite archive backup had a private VACUUM INTO implementation that could not be reused safely by snapshot/restore work. A second implementation would risk weaker integrity, sanitization, publication, and durability guarantees.

Why This Change Was Made

• Add one shared SQLite snapshot primitive that validates the source and final artifact with quick, full integrity, index, and foreign-key checks.
• Compact after any snapshot transform so removed sensitive rows cannot remain in free pages.
• Publish only verified private staging files, using no-overwrite hard-link or exclusive streamed-copy paths.
• Fsync files with Windows-compatible handles, verify file identity across publication, and clean up only artifacts proven to be owned by the operation.
• Export the existing global state owner/schema validator for future offline snapshot and restore validation.
• Move archive backup onto the shared primitive without changing its CLI contract.

This is the current-main foundation for the snapshot direction explored in #94805. The commit preserves Gio Della-Libera's co-author credit while replacing the stale prototype's direct-copy restore assumptions with a smaller verified primitive.

User Impact

openclaw backup create keeps the same interface, but SQLite snapshots now use a reusable publication path hardened against unsafe indexes, foreign-key corruption, target races, partial fallback copies, post-sanitization remnants, and Windows fsync behavior.

Evidence

• node scripts/run-vitest.mjs run src/infra/sqlite-snapshot.test.ts src/infra/backup-create.test.ts src/commands/backup-verify.test.ts src/commands/doctor-state-sqlite-compact.test.ts
  • 96 tests passed on Blacksmith Testbox through Crabbox, id tbx_01kxb7nzpq84zv43m20x3ep69t
• corepack pnpm check:changed
  • passed on the same Testbox
• oxfmt --check on all touched files
  • passed
• .agents/skills/autoreview/scripts/autoreview --mode local
  • clean, no accepted/actionable findings