A remote-image OCR failure can be hidden inside an HTTP-200 per-image error, making provider

A remote-image OCR failure can be hidden inside an HTTP-200 per-image error, making provider outages look like unreadable photos. Inspect nested errors before parsing annotations or marking traces successful. To distinguish an intermittent URL-fetch failure from a bad image, replay the same stored image as both a URL and inline bytes; later success does not disprove the historical failure. Sending validated server-fetched bytes removes the provider-to-storage retrieval hop, while genuine no-text results still need their own outcome.