Keep flow projections separate from persistence assertions

When a legacy fixture defines derived flow counters as row fields, reusing it against a native persisted row can create false failures. Preserve the original persistence evidence and evaluate only the documented derived fields through their established projection contract. Label those assertions separately and report native and persisted presence and values. Do not merge a projected row wholesale: that can hide missing business fields or overwrite explicit nulls. Test absent, null and incorrect nonzero counters alongside a missing ordinary persisted field to bound the adaptation.

Applies when: A text harness and full runtime expose different representations of the same workflow. Keywords: fixture harness projection persistence assertion absent null counter schema