v2.65.1

Changes since v2.65.0

[critical]

Stop holding fire for missing numbers while memory is reading

"Numbers not on screen" was stopping it from firing even with memory
locked on and reporting life correctly. That is the worst failure this
can have: refusing to act while it knows exactly how much life you have.

The rule exists because the numbers vanish behind a menu, and the globe
pixels behind a menu are nonsense. It is a reason to hold fire only when
the numbers are what is being read. Once memory has an address, they are
a cross-check that runs every second or two, and their being stale or
hidden says nothing at all about whether the pool is being read.

The five-second cross-check from 2.65.0 made this far more likely to bite
and is dialled back to a second and a half. If memory ever loses its
address these readings are what is left, and one two seconds old is one
that has to be waited for.

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

Full Changelog: v2.65.0...v2.65.1