Release reviews should verify defaults, write targets, hydration, and artifact gates

A release review should check that canonical policy defaults are not locally re-derived; scripts validate the database target they actually write through, not only a public API project; summary rows are fully hydrated before detail actions; and exact-head artifact gates remain usable after source changes merge. Retract a migration-ledger concern when repository documentation and tests define the observed frontier, count, and suffix behavior as the contract. Independent agreement does not rescue a finding contradicted by stronger source evidence.