Porting Test Drive II from SNES to PC, Part 4: Validation, cleanup, and current blockers

Porting Test Drive II from SNES to PC, Part 4: Validation, cleanup, and current blockers By the second week of this repo, the technical risk had changed. The problem was no longer "we do not have enough scripts." The problem was "we have enough moving pieces that incorrect progress can look convincing." That is why the March 6 to March 19 history matters so much. This is the phase where asmdump turns archaeology results into contracts, turns renderer bugs into isolated fixtures, and starts cleaning up its own generated noise. Validation became executable Commit c5ec8be on 2026-03-06 added the first real validation policy layer: tools/check_regression_gates.py tools/validate_callback_contracts.py validation/regression_gates_intro.jsonc rom_analysis/docs/callback_state_contracts.jsonc rom_analysis/docs/validation_gates.md This is a major change in the repo's engineering model. Before that point, progress was mostly tracked through: rendered outputs trace logs prose notes After that point