tools/dcvc-drift decodes the end-to-end job's fixture on each fabric through a loop that keeps
each element's scale, bucket and symbol, so drift and desync events are counted apart. On the
sink's route, the CPU provider at one thread, it also decodes through the sink's own
decode_envelope and holds the loop to it byte for byte; the other fabrics run in the loop alone.
research/dcvc-drift/verify.py, which shares no code with it, decodes every y stream again and
recounts every event, and a conformance step runs it over the committed readings.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
ffb32f740c