cleanup-verify

To verify game development project health after a pipeline run, you need to rebuild targets, check derived artefact drift, run automated test suites, and compare performance against established budgets to ensure build stability.

Derived artefact drift occurs when pipeline modifications cause regenerated build files to diverge from existing sources. Detecting this drift requires comparing newly generated artefacts against the original files to ensure source-to-derived parity.

Setting up performance guardrails involves capturing performance snapshots during post-pipeline verification and comparing them against defined budgets. This process prevents silent regressions by flagging builds that exceed acceptable performance thresholds.

Yes, this automated build verification is designed for engine-agnostic workflows. It evaluates project health by checking missing references, shader compilation, and build stability without relying on a specific game engine framework.

You should run an automated post-implementation cleanup and verification pass after any content pipeline modifies assets. Running it before committing ensures that pipeline changes have not introduced regressions, missing references, or build instability.

The best way to check build stability and parity is to perform a deterministic post-implementation verification pass. This method rebuilds targets, validates references, and compares regenerated derived artefacts against existing project files.