USR369 left for EOS Redlands, gave ODO 77120. Last message flagged this as an ODO check because 77120 looked notably lower than the 83,021 figure in the carried-forward tire-rotation reminder item -- that flag was MY error: 83,021 was never a current reading, it is the projected next-service-due mileage (77,021 install baseline + 6,000mi interval, per handoff-50.md and the Bill Linder Tires invoice). USR369's follow-up ('made a mistake, this is the correct reading right now') confirmed 77120 as today's real live ODO -- no correction was actually needed to any existing record, the tire-rotation projection (83,021) and the install baseline (77,021) were both already right; I had conflated a future threshold with an expected current reading. TASKGATE (system=50, task=log ODO reading for trip with no gas purchase) returned matched:false, but manual search (D-SEARCH-FIRST) found SOP-STANDARD-MILEAGE.md already covers exactly this case and names the Notion Mileage Log as destination -- TASKGATE's keyword-scoring just under-weighted it (worth a knowledge-api log_mistake entry re: TASKGATE scoring gap on this SOP). Queried the Notion Mileage Log's 5 most recent rows to find the last logged figure: 76754 (08/29 departure, per a gap-explanation Waypoint row noting Vilma/Markus commute 76636->76754). Gap from 76754 to 77120 = 366mi over 9 days (~41mi/day averaged) -- above SOP-STANDARD-MILEAGE.md's ~200mi/week question-threshold, so did NOT apply the silent weekday-commute default this time; logged the reading and flagged the gap size in the Notes field and to USR369 directly rather than assuming.