Does the flat transaction service in Canton 2.10 elide create/archive pairs?

IIRC, previous versions of the flat transaction service elided contracts that were created and archived in the same transaction, but I can’t find any documention to that effect in 2.10 proto docs.

Is still the case, and if so, can someone point me to the appropriate section in the docs stating this?

Are you thinking of the JSON API’s contract query stream? See “Some notes on behavior”, which mention this, and that even contracts created and archived in different transactions can be elided. As point (1) notes there, that is because it is not a transaction service at all.

That’s probably it, I read the contract query stream API documentation and somewhere down the line started conflating it with the transaction stream documentation in my head.

So, to be clear, the flat transaction stream has never, and does not, elide such pairs?

For anyone interested, after testing it indeed seems like the flat transaction stream elides create-archive pairs in the same transaction.