Keep assertions at the state boundary their source test measured

When porting conversation tests to a deployed end-to-end runner, preserve the state boundary for every assertion. A strict check of fields collected by tools should examine the final conversation state before summarization. Applying it to the later enriched database row can reject legitimate inferred facts that the original contract intentionally excluded. Check the persisted summary separately for expected outcomes and unsupported enrichment. Retain the original failed report when correcting the scorer, and document which evidence boundary changed. This correction establishes assertion parity; it does not excuse missing recordings, dropped answers or incorrect tool results.

Applies when: An integration runner ports strict assertions across conversation and post-processing stages. Keywords: strict assertion summary state boundary enrichment scorer regression evidence