Update docs to reference deploy_wireless.sh and stop_app.sh

- MANUAL_TESTING.md: replace manual startup commands with deploy script,
add Wireless vs Lite instructions, reference stop_app.sh
- TESTING.md: add "Deploying to the robot" section, add scripts to layout
- REMOTE_TESTING.md: fix Python version (3.10 → 3.12), cross-ref deploy

MANUAL_TESTING.md

@@ -6,11 +6,33 @@ Run through this checklist after significant changes, on each platform
 
 **Prerequisites:**
 - Reachy Mini robot powered on and connected (Wireless or Lite)
-- App running: `cd marionette && python -m marionette`
-- Open `http://<robot-ip>:8042` in browser
+- App deployed and running on the robot (see below)
+- Browser open at `http://reachy-mini.local:8042`
 - A short WAV or MP3 file ready for upload tests (~2-5s)
 - Hugging Face CLI logged in (`huggingface-cli login`) for HF tests
 
+**Starting the app (Wireless):**
+
+The fastest way to deploy and start marionette on a Wireless robot:
+
+```bash
+cd marionette
+./deploy_wireless.sh
+```
+
+This syncs your local code to the robot, starts the app via the daemon,
+and streams logs to your terminal. See the script header for prerequisites
+(SSH key setup, daemon status). Pass an IP if mDNS doesn't resolve:
+`./deploy_wireless.sh 192.168.1.42`
+
+To stop the app: `./stop_app.sh` (or use the dashboard).
+
+**Starting the app (Lite or local dev):**
+
+```bash
+cd marionette && python -m marionette
+```
+
 ---
 
 ## 1. Startup & Page Load
@@ -176,8 +198,8 @@ Run through this checklist after significant changes, on each platform
 | 13.8 | **Rapid record/play cycles** | Record 1.5s, play it, record again, play again. Repeat 5 times. Robot should stay responsive, no stuck states. |
 | 13.9 | **Delete a file externally** | While app is running, delete a `.json` file from the dataset folder. Click Refresh. Move disappears from list. No crash. |
 | 13.10 | **Replace a .wav file** | Copy a different WAV file over an existing move's `.wav`. Click Refresh. Play the move — new audio plays. |
-| 13.11 | **Server unavailable** | Stop the backend. UI shows "Unable to reach backend." Restart backend — UI recovers on next poll. |
-| 13.12 | **No robot connected** | Start app without robot. App may fail to start or show error in terminal. UI should not hang. |
+| 13.11 | **Server unavailable** | Stop the app (`./stop_app.sh`). UI shows "Unable to reach backend." Restart (`./deploy_wireless.sh`) — UI recovers on next poll. |
+| 13.12 | **No robot connected** | Start app without robot (`python -m marionette`). App may fail to start or show error in terminal. UI should not hang. |
 
 ---
 

TESTING.md

@@ -265,9 +265,37 @@ git push
 - `@pytest.mark.hardware` — tests that require a physical robot (skipped by
   default unless you run with `-m hardware`)
 
+## Deploying to the robot (Wireless)
+
+For manual testing or quick iteration on a Wireless robot, use the deploy
+script instead of reinstalling via the dashboard:
+
+```bash
+cd marionette
+./deploy_wireless.sh                  # default: reachy-mini.local
+./deploy_wireless.sh 192.168.1.42    # custom IP
+./deploy_wireless.sh --sync-only     # sync without starting
+```
+
+This rsyncs your local `marionette/` into the robot's site-packages
+(same location the dashboard installs to), stops the current app, starts
+marionette via the daemon API, and streams logs to your terminal.
+
+To stop the app:
+
+```bash
+./stop_app.sh                         # default: reachy-mini.local
+./stop_app.sh 192.168.1.42           # custom IP
+```
+
+See the script headers for prerequisites (SSH key, daemon, Wireless-only).
+
 ## Project layout
 
 ```
+deploy_wireless.sh   # Deploy + start on Wireless robot (dev workflow)
+stop_app.sh          # Stop the running app via daemon API
+
 tests/
 ├── conftest.py          # Shared fixtures (TestClient, temp paths, make_wav_bytes)
 ├── test_api.py          # Unit tests — backend API

tests/REMOTE_TESTING.md

@@ -155,7 +155,7 @@ This imports `ReachyMini()` and checks for a response. Times out after
 
 ### What's pre-installed on the robot
 
-The robot runs Ubuntu with Python 3.10 in `/venvs/apps_venv/`. The
+The robot runs Ubuntu with Python 3.12 in `/venvs/apps_venv/`. The
 following are already available:
 
 - `reachy_mini` SDK
@@ -178,6 +178,12 @@ result = subprocess.run(
 print(result.stdout)
 ```
 
+## Deploying the app (not tests)
+
+To deploy and run marionette on a Wireless robot for manual testing
+(not automated tests), use `deploy_wireless.sh` from the project root.
+See `TESTING.md` for details.
+
 ## Troubleshooting
 
 | Problem | Solution |