v0.5.1

v0.5.1

Released 5 August 2026

Two fixes reported from real use, both cosmetic in cause and misleading in effect: one made a healthy
fleet look like a broken one, the other made the Steam Deck app look like it had stopped responding.
Nothing about how saves sync has changed.

Before you upgrade

• Redeploy the console (docker compose pull && docker compose up -d) and update every agent.
  The version fix is split across both, so doing only one of them leaves Config still reporting a
  version split until the other catches up.
• Windows agents update themselves. On Steam Deck, download the newer tarball and re-run
  install.sh.
• No database changes. Unlike v0.5.0, this one carries no migration and downgrading the container
  is a clean rollback.

Fixed

• Config no longer reports one release as two versions. A fleet running a single release could
  show up as v0.5.0 on some machines and v0.5.0.0 on others, which reads as agents disagreeing
  with each other — a genuine fault, and one worth acting on, since agents on different versions can
  disagree about exclude globs and save paths and produce repeated sync conflicts. There was never a
  disagreement: Windows and Steam Deck agents were reporting the same build in two different formats.
  Every agent now reports one format, and the console treats the old four-part strings as equivalent
  so a fleet part-way through updating is not flagged either.
• The Steam Deck app no longer shows two things highlighted at once. On opening the app, and
  intermittently on the Overview list, two items could appear selected — and pressing A seemed to
  do nothing, because only one of them was really selected and it was rarely the one you were looking
  at. Moving the D-pad appeared to fix it, which made it look random. The Deck always has a pointer,
  whether or not you have touched the trackpad, and wherever it happened to be resting was drawn as a
  second selection. The pointer is now ignored until you actually use it.

For the curious

The second one could not be reproduced anywhere except on a Deck, which is a bad place to debug: the
development loop runs the Deck interface in a window on a PC, where the mouse sits outside that
window and never hovers anything. The fix that mattered most was therefore to the test setup — the
Deck interface can now be told to park a pointer at a fixed position, which turns "cannot reproduce
on demand" into a check that runs unattended and captures a screenshot.