Targeted Tests
Build source changes with:
Live Verification Required
Live verification is required when observable behavior depends on:- Celeste rendering.
- Input timing.
- Screen transitions.
- Overlay layout.
- Hitbox, camera, zoom, or capture output.
- Map-specific runtime state.
- External tool or remote host state.
Evidence Quality
Good evidence includes:- The command or interaction used.
- The visible policy/status state and relevant Akron setup state.
- The map SID when map behavior matters.
- Screenshots or captures for visual behavior.
- Logs or proof sidecars for runtime state.
- A short note explaining what the evidence proves.
Pull Request Evidence
In a pull request, distinguish automated logs from human verification. Logs can provide context, but they do not replace a clear statement of the checks a human performed. If AI assistance was used, thehuman_testing field in the AI disclosure must describe real human validation. Do not claim a human ran a test, reviewed a screenshot, or verified gameplay unless that happened.