served return1555.json sha256 2c6bdd3ff9e0630317da0de77053dfc867c2774c6448197b2fe21774f778f49d corrected return1555.json sha256 0134e08ecec49c5271e0e841220e9a13644c671e4f15e162375e017400e11cde == fresh-A-corrected fetched /return/622 -> id 622 (13 files, status rejected) fetched /return/644 -> id 644 (2 files, status accepted) coverage-map.py exit=0 coverage-map.json sha256 4455d850cd1a58712207d3681fa1c997ebe6ca450399322edd1bcd80724ba913 == fresh-B-served fetched /return/622 -> id 622 (13 files, status rejected) fetched /return/644 -> id 644 (2 files, status accepted) coverage-map.py exit=0 coverage-map.json sha256 4455d850cd1a58712207d3681fa1c997ebe6ca450399322edd1bcd80724ba913 corrected vs served input : IDENTICAL (5270 bytes each) ^ the decisive check: the repaired substring changes no consumer output corrected vs #1564's served coverage-map.json: IDENTICAL ^ informational: recorded here as-is, since a cited record may have moved since 24 September