Porting Test Drive II from SNES to PC, Part 5: Making generated evidence intentional

Porting Test Drive II from SNES to PC, Part 5: Making generated evidence intentional The next cleanup problem in this repo was not glamorous. It was git status . By March 19, asmdump already had enough archaeology tooling to produce: probe traces frame dumps sequence manifests design packs renderer fixtures gameplay sweep outputs late-intro diagnostics That is good progress, but it creates a new failure mode. If a reverse-engineering repo writes hundreds of files per experiment, then "generated" stops being a useful category. Some generated files are throwaway scratch. Some are promoted proof artifacts that the docs and checkpoints depend on. Some are local intermediate runs that matter for a day and then should disappear. If the repo does not make those categories obvious, progress gets harder to trust. The real problem was ambiguity The current port plan now treats maintainability as a first-class execution track, and that is the right call. The problem was not that the repo lacked c