Fix reservation fixture after migration identity restoration
Composing Database #134 with #125 leaves the new reservation fixture opening the old pack migration filename, which #125 restores to its recorded version. The affected suite fails before running any tests. This isolated successor normally merges both existing candidates and changes only the fixture to import the owning release-pack fixture's migration constant.
No SQL bytes are changed: all282 migration files match the previously inspected combined tree914fc433104f34dd2bee7fc9b86da6bc0ea6f858. Original #125, #134 and #115 branches remain untouched and open; this PR does not close or authorize merging them.
Validation: reproduced the exact FileNotFoundError on PostgreSQL17, then all17 affected composition tests passed on PostgreSQL15 and17. Independent narrow review is recorded separately. Catalog's completed four-migration bundle qualification was not repeated. Normal required CI still applies.
Release boundary: this full combined tree exposes SIX pending migrations against the November17 collected production ledger, not Catalog's reviewed four:20261010210500,20261022120000,20261106120000,20261110010000,20261110010100,20261117000000. Merging this PR as-is is therefore not an inert test-only release. Keep draft pending root's four-first versus six-file disposition and exact integration executor/ordering/transaction semantics. If #125's four are released first, refresh the actual ledger before claiming only the two reservation versions remain. No hosted apply, migration-history repair, grants, access, financial data, spending or activation was performed or authorized. Root owns the merge/release decision.
Summary by cubic
Fixes the credit reservation composition fixture after migration identity restoration so the affected suite no longer fails before running any tests. The fixture now imports the owning release-pack fixture's migration constant instead of the old 20261020150000_release_pack_jobs.sql filename.
Combines the previously open #125 and #134 with no SQL byte changes — all 282 migration files match the previously inspected combined tree, and only the fixture file and two renamed migration files are touched. The affected release-pack and professional-account migrations are restored to their recorded names (20261020154953 and 20261024002432). Reproduced the exact FileNotFoundError on PostgreSQL 17, then all 17 affected composition tests passed on PostgreSQL 15 and 17.
Release
- No hosted apply, migration-history repair, grants, access, financial data, spending, or activation is performed or authorized by this PR.
- The combined tree exposes six pending migrations against the November 17 collected production ledger, not the reviewed four:
20261010210500,20261022120000,20261106120000,20261110010000,20261110010100,20261117000000. - Merging as-is is not an inert test-only release; keep it draft pending root's four-first vs six-file disposition and exact integration/executor/ordering/transaction semantics.
- If #125's four are released first, refresh the actual ledger before claiming only the two reservation versions remain. Root owns the merge/release decision.