The operations team is checking a corrected table and the rules used to publish it. You need to distinguish data recovery from history deletion, and a schema change from an unreviewed type conversion. The working table has a known original snapshot and one changed version.
These tasks reuse time travel, constraints and dimension concepts. For executable recovery tasks, inspect the resulting records rather than treating a successful command as the answer. For design questions, use the stated business requirement: current values and historical values are different outputs. A restore can fix the current table without rewriting the history of what happened. Retention still limits which older snapshots can be recovered, so avoid promises that time travel lasts forever or that VACUUM is only a speed command.