v1.5.2 -- the CONTROLS tab can be used from a pad

A hotfix for two bugs that both needed the runtime rebuilt, so they ship
together. Nothing else changed.

The CONTROLS tab could not be used from a controller (#9)

Reported against 1.5.1. Trying to bind a button backed out of the bind instead
of taking it, every time. There were two separate causes stacked on top of
each other:

1. The menu acted on the press it was capturing. The overlay is driven by
   the pad -- B backs out, A confirms, the D-pad navigates -- and it kept doing
   that while a rebind was listening. Backing out cancels a pending bind by
   design, so pressing B to bind it cancelled its own bind.

2. A row could never be bound to the button that activated it. The detector
   samples every input's value when it starts and ignores anything already
   held. You activate a row by pressing A, so A was still down at that instant
   and stayed invisible for the full three seconds. That was never
   pad-specific: it was always whichever button confirms the row. Activating a
   row now only arms the bind, and the detector starts once you let go.

Both confirmed by hand on a controller.

A stray file in game/files/ refused every netplay session

A directory-backed game folder no longer folds the synthesised filesystem table
or the disc layout table into its sync hash, so an unrelated file sitting in
game/files/ stops making every session fail to start. Modified game archives
and mismatched regions are still refused -- that check is separate and
unchanged.

Also

A version bump now actually reaches the binary. The build read VERSION at
configure time only, so bumping it rebuilt everything with the previous number
still compiled in.

Downloads

• RingOut-1.5.2-linux-x86_64.zip -- desktop Linux. Run ./setup.sh <your disc image>, which recompiles the game on your machine.
• RingOut-1.5.2-steamdeck-x86_64.zip -- Steam Deck.

You need your own disc image of the game. That is what makes this legal to
share: the recompiled code is built from your copy.