[kcrmin]

What and why

db/migration/README.md still described V1 as generated: 181 tables, with the schema and seed-data fingerprints from 2026-08-13. b7de78b then added operations.operator_login_credentials and operations.operator_sessions to V1 before launch and updated only the SHA-256. The README now gives 183 tables, the recomputed fingerprints, and how they are computed. No V*.sql file is touched.

Verified

• Ran the fact queries from the root scripts/new-v1-baseline.ps1 against each V1 applied to an empty postgres:16-alpine. The 2026-08-13 V1 (e3bec375...) reproduces the old values exactly (301075f9..., e14e81ad..., 10/70/181). The current V1 (ccc5950a..., matching MigrationPolicy.BASELINE_SHA256) gives 4349602f..., 5e99f495... and 10/70/183.
• The fact diffs are only the two new tables, both with zero seed rows.
• Full ./gradlew test: 1054 tests, 1 skipped, 2 failed. These are the AccountClosurePersistenceIntegrationTest wall-clock failures that test(account): pin legal hold applied_at #294 fixes. This branch is develop plus this README edit, so they also fail on develop.

Checklist

• Documentation only
• No migration file changed
• No secrets or personal data