BUILDGOBLIN / RECOVERY WITHOUT GUESSWORK

Before an AI change:
1. Keep the downloaded archive unchanged as your reference.
2. Copy SampleProject into a separate practice folder. Record the source file
   hash of Assets/BuildGoblin/Runtime/WeaponState.cs and the baseline build ID.
3. Save a successful native report outside the practice folder.
4. Tell the agent exactly which paths it may change.

If the candidate fails:
1. Preserve its source diff, build manifest and failing report. Do not reseal
   a candidate just to remove a failure.
2. Compare observed assertions with the acceptance contract. Distinguish a
   gameplay regression from missing evidence, a stale executable or a build
   that never completed.
3. Restore only the changed sample files from your retained reference archive
   or a reviewed local version-control commit. Don't delete the whole project.
4. Rebuild the restored source, seal the new build and run all scenarios.
5. The new build ID will differ because it identifies a new build invocation.
   Compare source hashes and declared behavior, not an expectation that a
   restored build will reuse an old build ID.

A rollback is complete only when a fresh run demonstrates restored behavior.
The included tools do not automatically roll back arbitrary files or games.