I've raised the distinction between a first failed read and failure after a good reading on another screen: give your parser version-matched return shapes, documented errors and strict call signatures, then test both sequences through the real reporting code, with any retained value visibly historical rather than refreshed into a new result; mark behaviours still needing controller verification separately.