v1.5.2

Changed

• Main screen (Android and desktop): six buttons for what you do every game
  (new game, undo, redo, flip, hint, board) and a "more" menu for the rest
  (opening library, PGN import/export, game analysis). The texts above the
  board are down to one line: training progress or engine strength, replaced
  briefly by the blunder warning when there is one. Android buttons show a
  tooltip on long-press; the board button is filled green while a board is
  connected.
• The evaluation display is now off until you switch it on; a stored choice
  still wins.
• Boards: there is no board type to choose any more. "Connect board" lists
  the devices in range, recognised boards first, and the app finds out
  whether the one you pick is a DGT Pegasus or a Chessnut by probing its
  Bluetooth services, trying the next candidate when the first does not
  match. On Android a Pegasus is recognised by its advertised UART service
  even after it has been renamed.
• Chessnut: messages name the model the board announces, e.g. "Chessnut Air
  connected". Air+, Pro and Go speak the same protocol as the Air and are
  listed alongside it; only the Air has been tested. The Move is not
  supported.
• Desktop: the "more" button is a plain button with a context menu, so its
  glyph sits centred.

Fixed

• Android, landscape: the New Game dialog no longer hides the colour choice
  and the strength slider below the fold on short screens (phones, 7-inch
  tablets); it now lays out in two columns, opponent on the left and the
  rest on the right.
• Android, DGT Pegasus: disconnecting within the board's start-up sequence
  no longer leaves one "write failed" error per remaining init command
  behind, and a reconnect inside that sequence no longer starts a second,
  interleaved one.
• macOS: the app connects through a freshly created Bluetooth central and
  says why Bluetooth is unavailable instead of failing silently.
• Windows: a board that drops the link while its services are still being
  looked up no longer triggers a cascade of "service not found" / "connect
  failed" reports and a given-up reconnect; the next attempt starts clean.
  Boards advertising a random address now connect reliably. Error messages
  name the Bluetooth status. A second disconnect while already reconnecting
  no longer starts two reconnect timers.
• Linux: the same guard for the BlueZ transport, covered by a test against a
  fake BlueZ. Still unverified on real hardware.
• Linux, macOS: a second disconnect while already reconnecting no longer
  starts two reconnect attempts in parallel.

Build

• Building from source on Windows: Visual Studio and MSYS2 are found
  automatically, so a plain terminal or IDE build works.
• Running the desktop app from Gradle no longer needs a separately installed
  JDK 23; the Foojay toolchain resolver provisions it.