PostgreSQL Importer Test Evidence — 2026-08-15

Check	Status	Evidence
Dry-run	✅ passed	Expected metadata-only counts: 1 org, 1 user, 2 groups, 2 personas, 1 session, 2 messages
First apply	✅ passed	Created all expected fixture rows; fresh backup directory created
Second apply	✅ passed	0 created; all existing rows reported `unchanged`
Target counts	✅ passed	PostgreSQL contained exactly 1/1/2/2/1/2 rows
Conflict rejection	✅ passed	Changed existing group returned importer rejection code; no overwrite
Transaction rollback	✅ passed	Rows queued before the conflict were absent after rejection
Output redaction	✅ passed	Password-hash marker and database URL absent from serialized report
Schema downgrade cleanup	✅ passed	0 application tables remained after `downgrade base`
Real snapshot apply	🚧 pending	Requires operator-approved target operation and retained backup
Audit migration	🚧 pending	Non-empty JSON audit input remains fail-closed until S4.6
Runtime repository cutover	🚧 pending	JSON stores remain authoritative

All rows above used disposable local fixtures and a temporary local PostgreSQL database. No production data or credentials were used.