gba release: ship only tester_mb.gba, not the eyes payload

The eyes variant (joypad_mb.gba) is a firmware payload meant to be
multibooted by a host (joypad-os keeps its own independent copy for
that). It has no useful standalone runtime, so attaching it to a
public Release confused the "download and play" mental model.

After this change the gba Release attaches only tester_mb.gba -- the
standalone joypad button tester. The eyes build still happens in CI
(verify-build.yml uploads both variants for source-tree inspection)
and the eyes source stays in the repo, but it's no longer treated as
a publicly distributed ROM.

Author: RobertDaleSmith

.github/workflows/release.yml

@@ -127,12 +127,13 @@ jobs:
         working-directory: gba
         run: |
           mkdir -p _release
-          # Only the playable .gba ROMs go in the public release.
-          # _payload.c (C-array form for compile-time embedding) lives in
-          # the committed gba/build/ tree; submodule consumers like
-          # joypad-os pull it from the working tree, not from a Release
-          # artifact, so attaching it to the Release would be noise.
-          cp build/joypad/joypad_mb.gba  _release/
+          # Public release ships only the user-facing tester ROM.
+          # The eyes variant (joypad_mb.gba) is a firmware payload meant
+          # to be multibooted by a separate host (joypad-os keeps its
+          # own copy for that role), not run standalone -- end-users
+          # downloading the release want a playable joypad tester. The
+          # eyes build still lives in gba/build/ for source-tree consumers
+          # but doesn't get a Release attachment.
           cp build/tester/tester_mb.gba  _release/
           ls -la _release/
 

gba/README.md

@@ -144,11 +144,11 @@ unconditional handshake-complete write).
 
 Tagged as `gba-v<semver>` from the repo root — see
 [`gba/CHANGELOG.md`](CHANGELOG.md) for per-version notes. The release
-workflow attaches the two playable ROMs (`joypad_mb.gba`,
-`tester_mb.gba`) to each GitHub Release. The C-array embed forms
-(`build/<variant>/<variant>_payload.c`) stay in the committed `build/`
-tree for submodule consumers — they're not duplicated to Release
-artifacts.
+workflow attaches only `tester_mb.gba` — the user-facing standalone
+button tester. The eyes variant (`joypad_mb.gba`) is a firmware payload
+meant to be multibooted by a host firmware (joypad-os keeps its own
+copy for that role); it builds and ships in `gba/build/joypad/` for
+source-tree inspection but doesn't get a Release attachment.
 
 ## Origin / credits