check / check (push) Waiting to run
Deep verify set verified only on success and never set missing, so a failed --deep --json run reported zero for both. It now counts each blob whose contents pass as it goes, and the existence check runs through every blob, counting the missing and wrong-size ones as shallow verify does, instead of stopping at the first; it fails if it found any. Deep verify still stops at the first damaged blob and reads no blob contents while any blob is missing or the wrong size, so verified is 0 there where shallow mode counts the present blobs. Each missing or wrong-size blob is logged as a warning with its hash; the error now gives counts instead of naming one blob. Model: opus-5-5