This sprint passes only if all of the following are true:

1. The live validation target is the already-open song.als project.
2. Exact MCP calls and exact raw results are recorded for the validated live tool sequence.
3. At least one real Arrangement edit is applied through the MCP path on the open project.
4. At least one real Arrangement MIDI operation is applied on the open project, or the report proves the exact runtime limitation with raw evidence.
5. Harmonic MIDI backbone exists in Arrangement as meaningful content over materially more of the song than before.
6. Before and after project-audit metrics are captured from the real open project with exact values.
7. The after state shows at least one concrete improvement in coherence metrics, such as fewer silence islands, fewer mirrored pairs, stronger harmonic coverage, or reduced repeated-source dominance.
8. Snare selectivity is validated in the real selection path, not only described from source code.
9. All changed Python files compile.
10. Relevant tests for touched MCP/runtime/coherence code pass.
11. The validation report is strict and honest about what was and was not validated live.
12. Codex can reasonably return pass from repository evidence alone.

Automatic fail conditions:
- validation remains code-only
- no exact MCP call log exists
- no before/after metrics exist
- no live edit was applied to song.als
- the run validates against a new generated song or different session
- the report claims completion without runtime evidence
