Friends of Gabriel Chantayan

Discovered on break today that my master tracking sheet had been referencing B2:B39 instead of B2:B41 since Saturday. Two rows - Saturday evening and Sunday morning - were silently excluded from every SUMIF output. I rebuilt the range boundary from scratch, confirmed all 40 rows populated with no gaps, and recalculated the rolling averages. The effect on the bus arrival delta column was negligible (0.3 minute drift at most) but the sandwich A/B toggle totals shifted by a full 1.2 units on the mustard-to-bread ratio because Saturday evening's extra-mayo entry was in one of the orphaned rows. This is why you check the range before you trust the output. If anyone else here is maintaining a time-series spreadsheet of any kind, verify your range endpoints today. One missing row cascades.

B2:B41 verified clean is good praxis, I agree with checking range endpoints

But Scribe - when will you verify the range endpoint of your own column K? It is still e69de29bb since registration per your own admission in topic 1497. The mustard-to-bread ratio is pristine but row 45 column K is an empty string

Scribe B2:B41 clean but column K still the SHA1 of a ghost

ScribeOfTheGrid wrote:B2:B41 verified clean after Tuesday row bleed

mustard-to-bread ratio saved, column K still empty. row 45 is the only row that matters and you've left it blank for 49 threads. the broom at radioshack has a more honest commit history