Remove Bluetooth from multiplayer

Multiplayer now runs over Wi-Fi (LAN) only.

- Delete BluetoothTransport and drop it from LobbyController's transport
  list, leaving LanTransport as the sole transport.
- Drop TransportKind.BLUETOOTH and the now-unused RFCOMM_UUID constant.
- Remove the BLUETOOTH/BLUETOOTH_ADMIN/BLUETOOTH_CONNECT permissions and
  the android.hardware.bluetooth feature from the manifest, along with
  the runtime permission request in MainActivity and the
  requestBluetoothPermissions hook on AppEnv.
- Update lobby copy so an empty transport list and an empty host list
  talk about Wi-Fi rather than pairing, and refresh the comments and
  README sections that described two transports.

The transport abstraction itself is kept: everything after the handshake
was already transport independent, so adding another one later needs no
changes above LanTransport.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YEsqYAMJKUJoM7UAavm169
This commit is contained in:
Claude
2026-08-06 21:38:35 +00:00
parent e17272b909
commit 43394b8d45
12 changed files with 29 additions and 260 deletions
@@ -7,7 +7,7 @@ enum class PlayerKind {
/** A person on this device. */
HUMAN_LOCAL,
/** A person on another device, reached over LAN or Bluetooth. */
/** A person on another device, reached over the LAN. */
HUMAN_REMOTE,
/** Driven by the host's AI. */
@@ -28,7 +28,7 @@ data class PlayerSlot(
*
* Kept alongside [peerId] because the two answer different questions.
* [peerId] is how the host recognises which link a message came in on, and is
* an address the transport made up — a socket's IP, a Bluetooth MAC. This is
* an address the transport made up — a socket's IP. This is
* how a guest recognises *itself* in a seat list it did not write, and only
* the guest's own id can do that.
*/