Close the read-only SQLite handle and begin releasing its exact shared semantic-family lifetime. Idempotent. Release rejection is observed internally and retained by the persistence debt registry; callers that need teardown completion or an explicit retry use closeAndRelease.
Nothing.
Validate a batch in one synchronous SQLite read snapshot.
Persisted authority tuples to validate.
A current/stale mask captured atomically, or all false after close.
Confirm an exact, non-quarantined source receipt.
Vault-relative source path.
Content-source kind.
Source mtime selected with the persisted bytes.
Source authority revision selected with the bytes.
True only while that exact receipt remains current; false after close.
Database-content-non-mutating authority check over an existing embedding database. Opening and closing do publish then remove private persistence coordination markers; the configured SQLite family remains read-only. Implementations are safe to keep open across awaited vault reads: each validation call starts a fresh read transaction, while every receipt in one batch shares that transaction's SQLite snapshot.
Example