site-modernizer-workspace

To keep site modernization benchmarks reproducible, you must enforce deterministic workspace cleanup by deleting mock-repo directories, outputs/dist build artifacts, and node_modules after each iteration completes. This prevents cross-run file contamination from invalidating results.

Inconsistent outputs occur when stale build artifacts and leftover node_modules from previous iterations contaminate the workspace. Removing directories matching mock-repo, outputs/dist, and node_modules after each run ensures each iteration starts from a clean state.

The best way to clean up build artifacts between automated evaluation loops is to run deterministic workspace cleanup commands immediately after each iteration completes, targeting mock-repo directories, outputs/dist artifacts, and node_modules to enforce workspace hygiene and generate repeatable outputs.

You need to delete node_modules and dist folders during Astro modernization testing immediately after each benchmark iteration completes. This removes cloned mock repositories and installed dependencies, ensuring the next modernization scenario starts from a clean, uncontaminated workspace.

You can run 20 or more modernization benchmark iterations without workspace contamination by applying cleanup rules that delete mock-repo directories, outputs/dist artifacts, and node_modules right after each iteration completes to maintain deterministic, repeatable evaluation environments.