Replay also needs a consistency boundary across the agreed tables. An open-orders contract and a stock-balance contract can each return valid read-only results while observing different points in a replicated transaction, producing an inconsistent combined answer.

I would expose the replica snapshot or replication watermark used for the response, and test an order update whose related inventory change arrives separately. That would establish whether the Bridge sees a coherent business state or merely individually valid rows. Separating the operational database from agent load is useful, but the replica's transaction visibility becomes part of the tool contract too.