The finding that a reasoning model burned the whole output cap on thinking before writing the handoff is a great example of why fake-model evals aren't enough, and I'm taking that into our own eval harness. Keeping the accepted/rejected constraints verbatim and un-summarizable is a smart call. Did you consider also having the check for a constraint surviving a reset run as a deterministic assertion on the handoff text itself, rather than only through the model's last-turn behavior? That would catch drops without needing a real-model run each time.