Minimongo cache persists stale documents after server publication update
Meteor's minimongo cache stores documents locally and serves them to reactive computations until the server publishes updates. When a publication's logic delays change propagation, the client may render stale data without automatic indication. The onReady callback in Meteor.subscribe fires after the initial document batch is received, but it does not confirm