This is the interesting one :)

It aims to ensure that on every new file we start, "The decision on the offset we start from is persisted." There is now a decision to start any files encountered during startup from the end (or begin if from-beginning=true). And any files encountered during running from the end.

Instead of sending this through publisher (which doesn't care and will block it if pipeline slow) we bypass and send directly to registrar. So it's still following the usual pipeline - just jumping past registrar to ensure the chosen offset is persisted immediately.