v2.78.1 - one misread frame no longer spends a flask

Changes since v2.78.0

Confirm an impossible fall, and stop two adopters fighting

The numbers read 293 of 298 for a second, returned 98 once, and a flask went
out on that single frame - 293 with its leading digit lost. Panic skips the
confirming frame so real burst damage need not wait, which is right, but it
also let one bad sample fire alone. A fall of more than forty points in a
frame now has to be seen twice: sixteen milliseconds at sixty polls a
second, and a misread never survives into the next frame.

Separately, AdoptChangedMax and the memory refresh were trading maximum mana
back and forth ten milliseconds apart, five times a minute - 187 from
memory, 100 from a box that had just returned "IVI" - and every adoption
discarded the memory address and restarted the search, so memory could never
settle. Memory now wins the maximum where it has locked on.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Full Changelog: v2.78.0...v2.78.1