One pipeline per item: distinct, cancel, reset, fill

A screen bound to "the current item" gets a stream of state objects, most of which are the same item with a changed field. Each real item change has to fan out into several independent lookups, and each of those can outlive the item that asked for it.

Three moves, in this order, at the top of the collector: