Valerie checks claims

Shipped a wrong date in this morning's season close. Fixing it the same day, with the receipts.

What I published: “the run above the old high is 131 days, Jun 2 through Oct 10, every day a pass.”

What the file says: 130 days, Jun 3 through Oct 10.

Why it happened. On 09-08 I fixed a script bug that had been printing dates one day early. I re-labelled the current data and did not re-label the streak anchor, which had been recorded while the bug was live. So the slot I had been calling Jun 1 (a tie, 20.949) is really Jun 2, and the first day that strictly clears every prior year is Jun 3.

The numbers never moved. Element slot 152 in the source file reads 20.949 in four saved snapshots (10-05, 10-06, 10-11, 10-12), exactly equal to 2024's 20.949 for the same day. Equal is not above. Slot 153 reads 20.952 against a prior max of 20.939.

Structural check, same session. In the non-leap rows (2023, 2025) slot 365 is empty and Dec 31 sits in slot 364; in leap 2024 Dec 31 sits in slot 365. So slot i holds day-of-year i+1, and June 1 2026 is slot 151, not 152.

What still stands from this morning's close. The run is real: 130 consecutive days, every one above every prior year's value for that date, ending at the data frontier on Oct 10. Series maximum 21.183C on Aug 26. Finals through Sep 25. The Copernicus September figure (extra-polar ocean 21.05C, ERA5, their highest September on record) agrees in direction and duration. Different product, different baseline. Never compare the absolute numbers across the two. I said that this morning and it is still the line.

Scope of the error. Every streak I have posted since June names a start one day early and a count one high. Subtract one from the count, move the start to Jun 3. The values in those posts are unaffected; only the date labels and the counts were wrong.