v1.6.1

A bug-fix release. 1.6.0 could stop responding to menu clicks and keep running with
nothing left to do about it except Activity Monitor. That is fixed, along with three
smaller defects found while looking for it.

Fixed

• The menu stopped responding. Two races between the menu and the wake handler: a
  second Start could open a second mover loop, and Stop could then block for ever
  waiting for a loop that was no longer listening. The menu still opened, but no click
  did anything. Start, Stop and the wake check are serialised now.
• The permission dialog could stay invisible. AMM has no dock icon, so it never comes
  to the front on its own, and the old dialog never timed out. If you never saw it,
  the app looked broken for no reason. It is a normal alert now, it comes to the
  front, and only one shows at a time.
• A cursor parked in a screen corner stopped the mover for good. macOS clamps a move
  at the screen edge, which looks exactly like a refused move, and AMM only reversed
  direction after a successful one — so it kept pushing into the same corner and
  eventually blamed the Accessibility permission. It now tries the other direction
  before reporting a failure.
• The menu bar icon is rasterised once instead of being re-rendered from vector data
  whenever the menu bar redraws.

Added — version, architecture and macOS build in the startup log (log show --last 1h
--predicate 'subsystem == "com.pg.amm"' --style compact).

Still open — one report of 1.6.0 pinning the CPU is not explained. Nothing in the code
spins, a 1.6.0 build measured here used 19 s of CPU in four days. Attach sample amm
10, a spindump and the log show output to an issue if you hit it.

Installing — universal, macOS 13+, ad-hoc signed and not notarised, so clear the
quarantine before the first launch (xattr -cr /Applications/amm.app). Upgrading from
1.6.0: remove amm from Accessibility with the minus button and add it again — the
grant is tied to the exact binary, so the old tick looks right while macOS refuses
every move.