Document the Adeept ADR036 on-Pi bring-up runbook and installer shape

ddiff --git a/docs/HANDOFF.md b/docs/HANDOFF.md
iindex 9f92f4f..c1302e4 100644
---- a/docs/HANDOFF.md
++++ b/docs/HANDOFF.md
@@@ -113,7 +113,7 @@ pattern (dry-run), an H.264 byte stream from a child process (`rpicam-vid`, `ffm
  
  ## install.sh and CI
  
--`install/install.sh` (`curl -fsSL https://openvibe.bot/install | sh -s -- --robot rob_... --code ABCD-1234 --driver adeept`):
++`install/install.sh` (`curl -fsSL https://openvibe.bot/install | sh -s -- --robot rob_… --code CODE [--driver adeept|adeept-mecanum|cozmo|none]`, e.g. `--code ABCD-1234 --driver adeept`):
  detect OS/arch, download the release binary and the plugin bundle, create a Python virtual environment for plugins,
  install the service, pair with the code.
  CI: `go vet`, `go test ./...` (race detector), cross-compile every target, Python plugin tests, and a release workflow on
ddiff --git a/docs/hardware-adeept.md b/docs/hardware-adeept.md
nnew file mode 100644
iindex 0000000..3eb2874
---- /dev/null
++++ b/docs/hardware-adeept.md
@@@ -0,0 +1,62 @@
++# Adeept ADR036 4WD Smart Car — hardware bring-up (O30)
++
++The device side is the OpenVibe Node (`openvibe-node`) with the `adeept_adr036` plugin. Bot serves the one-paste
++installer; the panel is `openvibe.bot/panel/<rob_…>`. Nothing here runs the kit's stock control server — the Node
++replaces it, and the installer disables the kit's own autostart (`docs/install.md`).
++
++## 1. On the Pi (Raspberry Pi OS Bookworm, 64-bit)
++
++- `sudo raspi-config` → Interface Options: enable **I2C** and **SPI**. Reboot. (Or set `dtparam=i2c_arm=on` and
++  `dtparam=spi=on` in `/boot/firmware/config.txt`.)
++- Confirm the kit's stock control server is not running: `systemctl is-enabled Adeept_Robot.service` must report
++  `disabled` (or the unit absent), and ports 8888/5000 must be free. `install/install.sh` stops and disables
++  `Adeept_Robot.service`, kills a running `WebServer.py`/`APPServer.py` process, and comments out the kit's autostart
++  lines in the invoking user's crontab, root's crontab and `/etc/rc.local` (prefixing them with
++  `#openvibe-node-disabled:`). If it is still on, stop and disable it before pairing.
++- Python 3 + venv: the installer creates a plugin virtual environment in the Node's state dir
++  (`/var/lib/openvibe-node/venv` on Linux, `--system-site-packages`) and `pip install`s the plugin bundle there. No
++  manual `pip install` is needed.
++
++## 2. Pair (one pasted command from openvibe.bot)
++
++```sh
++curl -fsSL https://openvibe.bot/install | sh -s -- --robot rob_… --code XXXX-XXXX --driver adeept
++```
++
++Network pairing, if openvibe.bot offers the Network form:
++
++```sh
++curl -fsSL https://openvibe.bot/install | sh -s -- --network https://openvibe.network --pairing pair_… --code XXXX-XXXX --driver adeept
++```
++
++Then check the written config (`cat /etc/openvibe-node/config.json`): `plugins` names `adeept_adr036` with backend
++`real` and `wheels: "ordinary"`, and `video.whip_url` is set (the ingest URL + publish key the pairing returned; O30:
++`https://ingest.openre.stream/whip/<key>`). `openvibe-node status --json` should show `link.connected: true` and
++`video.state` at `connecting` or `live`.
++
++## 3. Panel checklist
++
++Drive from openvibe.bot; watch `openvibe-node status --json` for telemetry.
++
++| Subsystem | Expected | Pass |
++|---|---|---|
++| Motors (PCA9685 `0x5f`, 50 Hz; M1–M4 = 15/14, 12/13, 11/10, 8/9) | forward/back + steer; wheels stop at the 300 ms deadline and on `openvibe-node stop` | |
++| Servos pan ch0 / tilt ch1 (500–2400 µs) | reach min → centre → max | |
++| Battery (ADS7830 `0x48`, 2×18650 6.0–8.4 V) | telemetry `battery.volts` ≈ pack, `percent` sane | |
++| Ultrasonic (`DistanceSensor(echo=24, trigger=23)`) | `sensors.distance_cm` changes with a hand | |
++| Line tracking (GPIO 22/27/17) | `sensors.line` flips over tape | |
++| Buzzer (GPIO 18) / WS2812 (SPI 0.0) | horn + lights widgets work | |
++| Camera (`rpicam-vid --codec h264 --inline -o -` → `internal/video/whip.go`) | panel shows live video (needs the Ops-WHIP row) | |
++| Safety | kill Wi-Fi / Ctrl-C / panel e-stop → wheels stop; e-stop stays latched through a restart | |
++
++Mecanum chassis: re-run with `--driver adeept-mecanum` (profile variant `adeept.adr036.mecanum`, `wheels: "mecanum"`).
++
++OLED/display: **not supported** (deferred) — see `plugins/adeept_adr036/README.md`; the profile has no display
++widget and a `display` command is nacked.
++
++## 4. If the camera will not start
++
++If `rpicam-vid` is missing, `video.source` `auto` falls back to the plugin's JPEG frames (the core encodes them with
++`ffmpeg`) and then to the test pattern — the panel can still show video. Check `openvibe-node status --json` →
++`video.state` and `video.last_error` and report the exact error. `--driver adeept` installs the plugin but the core
++still needs `rpicam-apps` for H.264 and `ffmpeg` for the JPEG path (both noted in `docs/install.md`).
ddiff --git a/docs/plugins.md b/docs/plugins.md
iindex c58f2a2..3c58691 100644
---- a/docs/plugins.md
++++ b/docs/plugins.md
@@@ -107,6 +107,9 @@ the panel (ADR-043 decision 7: names are open strings checked against a registry
  | `camera`   | `{"h264_command": [argv]}` (the core runs it), `{"jpeg": true}` (frames by `video`), or `{"source": "test_pattern"}` | video |
  | `battery`, `sensors`, `lights`, `bridge` | informational                                              | —           |
  
++For the Adeept 4WD Smart Car's on-Pi pass — wiring, pairing, the panel checklist and camera troubleshooting — see
++[hardware-adeept.md](hardware-adeept.md).
++
  ## The bundled drivers
  
  ### `dryrun`