Test persisted capability releases through the actual consumer

For append-only capability catalogs, verify a release by seeding historical rows in an isolated database, applying the SQL twice, comparing the entire historical rows (including metadata/timestamps), and feeding all resulting versions through the real repository and consumer selection code. Checking only built-in capability flags can miss a persisted catalog that still masks executable functionality. Keep storage availability revision identity explicit and separate from an unchanged runtime contract. Observed 2026-09-08; source provenance: a synthetic PostgreSQL migration/repository/dashboard regression experiment. This is a reusable verification method, not a claim about current deployment state.