Added chatterbox connections

README.md

@@ -1,4 +1,4 @@
-# Escape Gallery — Glitch: the Dark Machine
+# Escape Gallery — Glitch: the Dark Machine
 
 **A Godot arcade escape-room framework with a browser-based operations hub.**
 
@@ -22,7 +22,7 @@ The Arcade software is separate from Odin. Its RFID helper follows the tester PC
 | Start Pi services remotely over SSH | [Remote cabinet startup](docs/remote_pi_start.md) |
 | Stage and activate fleet releases | [Deployment tools and current limitations](tools/deploy/README.md) |
 | Configure the operator/controller | [Room controller guide](tools/room_controller/README.md) |
-| Test sequential cabinet objectives | [5 seconds → 500 points → 1 frog](docs/three_cabinet_test.md) |
+| Test sequential cabinet objectives | [5 seconds → 500 points → 1 frog](docs/three_cabinet_test.md) |
 
 The fleet wizard is not yet a complete RFID installer: it does not generate the device/helper paths and rejects an empty output allowlist with real GPIO enabled. Use the master walkthrough's manual installation for the RFID-only test. Do not add an arbitrary output pin to bypass this limitation.
 
@@ -103,7 +103,7 @@ Doorways are layout annotations. They do not change game collisions or act as li
 
 Open a cabinet profile's **PCB Connections** editor and select a connector to assign a device type, name, unique ID, binding, and wiring notes. Digital inputs expose their pull-up setting. The editor validates duplicate assignments and relevant pin/action conflicts, supports Undo/Redo, and saves the configuration with the cabinet resource.
 
-The board includes direct GPIO connectors, J16 I2C, and multiplexed J1–J8 reader connectors. See the [pin mapping guide](docs/cabinet_pcb_setup.md). Saving this inventory does not energize outputs or install drivers. Supported entries can be exported into the optional runtime feedback configuration; I2C and Other devices remain inventory-only.
+The board includes direct GPIO connectors, J16 I2C, and multiplexed J1–J8 reader connectors. See the [pin mapping guide](docs/cabinet_pcb_setup.md). Saving this inventory does not energize outputs or install drivers. Supported entries can be exported into the optional runtime feedback configuration; I2C and Other devices remain inventory-only.
 
 ## Operator hub and managed play
 
@@ -226,4 +226,10 @@ tests/                  Godot/Python checks and isolated fixtures
 
 Physical RFID commissioning, complete RFID support in the fleet wizard, browser doorway rendering, additional cabinet artwork, general sensor-to-scenario rules, detailed puzzle-step views, coordinated finale variants, and room timers/hints remain future work. The hub can link to other services; it is not yet a full multi-room orchestration system.
 
-Pac-Man power-button wiring, the `devices.json` input entry, and the complete power → boot → RFID → Start acceptance test are included in the [master walkthrough](docs/pacman_rfid_first_setup.md).
+Pac-Man power-button wiring, the `devices.json` input entry, and the complete power → boot → RFID → Start acceptance test are included in the [master walkthrough](docs/pacman_rfid_first_setup.md).
+
+## Glitch / Odin integration lab
+
+The isolated [Rust, NATS, and Flutter lab](labs/glitch_odin/README.md) provides an experimental GM screen and simulated Pac-Man cabinet for testing the power, boot, RFID credit, Start, and win flow. It leaves Odin and the current Pi deployment untouched. Begin with the lab prerequisite check; Rust/Flutter checks and the headless real-Godot integration test now pass; physical RFID testing remains pending.
+
+The [whole-room simulation walkthrough](labs/glitch_odin/ROOM_SIMULATION.md) covers the seven-cabinet Glitch story, discovery puzzles, ship cells, party-scaled calibration, launch and Teddy narration. This is an isolated Rust/NATS/Flutter prototype with virtual time and replayable traces; production durable recovery and hardware integration remain separate gates.