Practical Picks PP-280 method — checked October 3, 2026 Historical record: this describes an earlier hands-on check run on October 3, 2026, before Practical Picks adopted its research-only method. It is kept unchanged below as dated evidence. We no longer run product checks; the current article was re-decided on October 19, 2026 from public sources, and these observations corroborate it but did not decide it. Versions checked: dbmate 2.36.0, sqlite3def 3.11.26, sqlite-schema-diff 0.3.1. Job: change a local SQLite schema on a disposable development database before deployment. This is not a deployment test or a test of production data. Fixture: research/PP-280/seed-fixture.py creates two invented task rows with the same owner, an old index and an empty obsolete table. research/PP-280/target.sql adds a defaulted state column, new index and events table, and removes the old objects. The dbmate migration expresses the same up change and an authored down change. These inputs were fixed before product runs. Reproduction files: /assets/pp280/replay.py, /assets/pp280/seed-fixture.py, /assets/pp280/target.sql and /assets/pp280/migrations/202610030001_change_schema.sql. The Python replay script creates the deliberately failing desired schema and failing migration from fixed SQL text embedded in the script. It seeds three separate SQLite files, runs the commands below, checks exact object names, columns, version records, invented row values and PRAGMA integrity_check, and writes stdout, stderr and exit codes to replay.json. It refuses different binary digests. Run it only in a disposable directory. Exact Linux amd64 setup, with a working directory you control: mkdir -p pp280-replay/bin pp280-replay/migrations cd pp280-replay curl -fL -o bin/sqlite-schema-diff https://github.com/MizuchiLabs/sqlite-schema-diff/releases/download/v0.3.1/sqlite-schema-diff_linux_amd64 curl -fL -o sqlite3def_linux_amd64.tar.gz https://github.com/sqldef/sqldef/releases/download/v3.11.26/sqlite3def_linux_amd64.tar.gz curl -fL -o bin/dbmate https://github.com/amacneil/dbmate/releases/download/v2.36.0/dbmate-linux-amd64 printf '%s %s\n' '9757c73b23d983f9b97b742cf2e59b61f464f0dd97b7ffec9d1249ff9ae66b40' bin/sqlite-schema-diff '7ef1cadbbaca6f12543c00edd3abe6b607ec69f30239517c47e36f86b580e378' sqlite3def_linux_amd64.tar.gz '47e284b3d8cbad1ba5f090495aa05afd1bbd5f35e2ed5577aad06da74ce780ce' bin/dbmate | sha256sum -c - tar -xzf sqlite3def_linux_amd64.tar.gz -C bin sqlite3def chmod +x bin/sqlite-schema-diff bin/sqlite3def bin/dbmate curl -fL -o replay.py https://practicalpicks.guide/assets/pp280/replay.py curl -fL -o seed-fixture.py https://practicalpicks.guide/assets/pp280/seed-fixture.py curl -fL -o target.sql https://practicalpicks.guide/assets/pp280/target.sql curl -fL -o migrations/202610030001_change_schema.sql https://practicalpicks.guide/assets/pp280/migrations/202610030001_change_schema.sql python3 replay.py --bin-dir ./bin --output ./replay.json At this private-draft stage, practicalpicks.guide asset URLs are not public. The same files are in the PP-280 source tree for local review. The script writes databases to a temporary directory and deletes them after writing JSON evidence. It does not use a real database. Our run returned `PASS: 19 commands`; each failure had a nonzero exit code: sqlite-schema-diff 1, sqlite3def 1, dbmate 2. Full raw outputs and asserted states are retained in `research/PP-280/observations/replay.json` for editorial review. Versions: dbmate 2.36.0, sqlite3def 3.11.26, sqlite-schema-diff 0.3.1. Linux amd64 release binaries ran from a temporary task directory. Combined downloads and extracted binaries were about 57.4 MB. No account, package installation, service database or live record was used. We previewed or inspected pending work, applied the change, checked SQLite schema objects, original row values, new defaults and PRAGMA integrity_check. Then we planted a unique index on the duplicated owner values in a separate post-change copy. Dbmate's failing migration first created another table to test transaction rollback. We checked for the failed index, the prior table, row changes and integrity after the error. Result: all three applied the five intended schema changes, kept both original row values and passed integrity_check. Each rejected the planted unique index and left no failed index; dbmate also left no preceding table or failed version record. Dbmate's authored down migration restored the original schema shape and both retained task rows. sqlite3def did the same by applying the old desired schema. The dropped table was empty, so this does not demonstrate recovery of deleted data. sqlite-schema-diff wrote a pre-change backup; we copied it to a separate file and verified the copy had the same SHA-256 digest, original schema and rows, and integrity_check=ok. We did not replace a live open database. Recovery paths differ. An authored down migration is not automatic reversal of arbitrary data changes. Reapplying an old schema cannot restore data from dropped objects. A backup requires a deliberate, correctly timed restore. Keep an independent backup and rehearse recovery for consequential changes. Limits: tiny synthetic data, one Linux environment, one schema transition and one failing unique-index change. No concurrency, large tables, nonempty dropped table, changed constraints, cross-version compatibility, performance ranking, production deployment or full security audit. Semantic schema objects and data were compared, not byte-identical CREATE statements. Source and binary release pages were checked October 3, 2026.