/**
 * Type contract for `cleo backup verify` — per-DB freshness + integrity walker.
 *
 * `cleo backup verify` walks every entry in `DB_INVENTORY` and reports, for
 * each role, the freshest snapshot in BOTH the canonical backup directory
 * (`.cleo/backups/sqlite/` per T10315) and the legacy backup directory
 * (`.cleo/backups/snapshot/`, kept read-only for one deprecation window).
 * Each snapshot is opened via the canonical chokepoint, verified with
 * `PRAGMA integrity_check`, and surfaced as a structured envelope. Operators
 * use the envelope to detect stale and corrupt backups before they're needed
 * for recovery.
 *
 * Verdict semantics (see {@link BackupVerifyVerdict}):
 *
 *  - `healthy` — a fresh snapshot exists (≤ 24h old) AND `integrity_check`
 *    returned `ok`.
 *  - `stale` — a snapshot exists but its mtime is > 24h old. Integrity may
 *    still be OK; the operator should run `cleo backup add` to refresh.
 *  - `corrupt` — at least one snapshot exists but the FRESH snapshot failed
 *    `integrity_check`. The legacy snapshot may still be usable as a fallback.
 *  - `missing` — no snapshot was found in EITHER the canonical or legacy
 *    directory. Recovery from snapshot is impossible.
 *
 * @task T10319
 * @epic T10284
 * @saga T10281
 */
export {};
//# sourceMappingURL=backup-verify.js.map