robopark 2.8.26 → 2.8.27

package/README.md

@@ -1,63 +1,63 @@
-# robopark
-
-The **RoboPark fleet control CLI** — set up, watch, and drive a room full of
-talking robots from one command. `robopark` is the operator front-end; it rides
-the [`infinicode`](https://www.npmjs.com/package/infinicode) device mesh, which
-it installs as a dependency. You install and think in one name — everything else
-is plumbing.
-
-## Install
-
-```sh
-npm install -g robopark
-```
-
-## The whole setup — two commands
-
-Operators think in **scheduler / robot / laptop**; the mesh underneath thinks in
-hub / satellite / peer. `robopark` translates, and each role turns on the right
-defaults automatically.
-
-```sh
-# On the on-site hub (LiveKit Server 1) — LAN + Tailscale + dashboard on:
-robopark setup --scheduler --gateway ws://<infinibot-gateway>:18789 --start
-
-# On each robot Pi — accept-only, LAN-discovered:
-robopark setup --robot --name robopanda --start
-
-# From anywhere — a live table of the whole fleet:
-robopark fleet --watch
-```
-
-Run `robopark setup` with no role for a guided wizard.
-
-## Commands
-
-| Command | Does |
-|---|---|
-| `robopark setup` | Configure this device's role + site and (with `--start`) launch its node. |
-| `robopark fleet [--watch]` | Live table of every node the mesh can see. |
-| `robopark run <node> <cmd>` | Run a command on one node (use `.` for the local node). |
-| `robopark apply` | Publish this hub's providers / keys / policy to every satellite. |
-| `robopark dashboard [--open]` | Open the web control panel served by the hub. |
-
-## How it fits together
-
-```
-you ── robopark ──▶ infinicode nodes (the mesh) ──▶ InfiniBot (watch)
-                          └──▶ web dashboard :47913 (watch / drive)
-```
-
-- **robopark** — the remote control. A CLI, no daemon. Writes config and calls
-  each node's HTTP API.
-- **infinicode** — the runtime. `infinicode serve` runs on every device, forms
-  the mesh, runs agents, streams telemetry, and serves the dashboard.
-- **InfiniBot** — the cockpit. Each node pushes its status *up* to InfiniBot;
-  you watch there (or in the built-in dashboard).
-
-`robopark` never talks to InfiniBot directly — it drives infinicode nodes, and
-those surface in InfiniBot.
-
-## License
-
-MIT
+# robopark
+
+The **RoboPark fleet control CLI** — set up, watch, and drive a room full of
+talking robots from one command. `robopark` is the operator front-end; it rides
+the [`infinicode`](https://www.npmjs.com/package/infinicode) device mesh, which
+it installs as a dependency. You install and think in one name — everything else
+is plumbing.
+
+## Install
+
+```sh
+npm install -g robopark
+```
+
+## The whole setup — two commands
+
+Operators think in **scheduler / robot / laptop**; the mesh underneath thinks in
+hub / satellite / peer. `robopark` translates, and each role turns on the right
+defaults automatically.
+
+```sh
+# On the on-site hub (LiveKit Server 1) — LAN + Tailscale + dashboard on:
+robopark setup --scheduler --gateway ws://<infinibot-gateway>:18789 --start
+
+# On each robot Pi — accept-only, LAN-discovered:
+robopark setup --robot --name robopanda --start
+
+# From anywhere — a live table of the whole fleet:
+robopark fleet --watch
+```
+
+Run `robopark setup` with no role for a guided wizard.
+
+## Commands
+
+| Command | Does |
+|---|---|
+| `robopark setup` | Configure this device's role + site and (with `--start`) launch its node. |
+| `robopark fleet [--watch]` | Live table of every node the mesh can see. |
+| `robopark run <node> <cmd>` | Run a command on one node (use `.` for the local node). |
+| `robopark apply` | Publish this hub's providers / keys / policy to every satellite. |
+| `robopark dashboard [--open]` | Open the web control panel served by the hub. |
+
+## How it fits together
+
+```
+you ── robopark ──▶ infinicode nodes (the mesh) ──▶ InfiniBot (watch)
+                          └──▶ web dashboard :47913 (watch / drive)
+```
+
+- **robopark** — the remote control. A CLI, no daemon. Writes config and calls
+  each node's HTTP API.
+- **infinicode** — the runtime. `infinicode serve` runs on every device, forms
+  the mesh, runs agents, streams telemetry, and serves the dashboard.
+- **InfiniBot** — the cockpit. Each node pushes its status *up* to InfiniBot;
+  you watch there (or in the built-in dashboard).
+
+`robopark` never talks to InfiniBot directly — it drives infinicode nodes, and
+those surface in InfiniBot.
+
+## License
+
+MIT

package/bin/robopark.js

@@ -1,17 +1,17 @@
-#!/usr/bin/env node
-/**
- * robopark — thin operator front-end.
- *
- * This package is a wrapper: the actual CLI lives in `infinicode` (its declared
- * dependency), exposed as the `infinicode/robopark` subpath. Importing it runs
- * the command against this process's argv, so `robopark …` and
- * `infinicode robopark …` are the exact same code. Keeping it a wrapper means
- * operators install and think in one name — `robopark` — while all the mesh
- * machinery ships and versions under infinicode.
- */
-import('infinicode/robopark').catch((err) => {
-  console.error('robopark: could not load the infinicode runtime.');
-  console.error(err && err.message ? err.message : err);
-  console.error('Try reinstalling:  npm install -g robopark');
-  process.exit(1);
-});
+#!/usr/bin/env node
+/**
+ * robopark — thin operator front-end.
+ *
+ * This package is a wrapper: the actual CLI lives in `infinicode` (its declared
+ * dependency), exposed as the `infinicode/robopark` subpath. Importing it runs
+ * the command against this process's argv, so `robopark …` and
+ * `infinicode robopark …` are the exact same code. Keeping it a wrapper means
+ * operators install and think in one name — `robopark` — while all the mesh
+ * machinery ships and versions under infinicode.
+ */
+import('infinicode/robopark').catch((err) => {
+  console.error('robopark: could not load the infinicode runtime.');
+  console.error(err && err.message ? err.message : err);
+  console.error('Try reinstalling:  npm install -g robopark');
+  process.exit(1);
+});

package/package.json

@@ -1,38 +1,38 @@
-{
-  "name": "robopark",
-  "version": "2.8.26",
-  "description": "RoboPark fleet control CLI — set up, watch, and drive a fleet of talking robots. The operator front-end over the infinicode mesh.",
-  "type": "module",
-  "bin": {
-    "robopark": "./bin/robopark.js"
-  },
-  "files": [
-    "bin/robopark.js",
-    "scheduler",
-    "pi-client",
-    "vision",
-    "README.md"
-  ],
-  "engines": {
-    "node": ">=20"
-  },
-  "dependencies": {
-    "infinicode": "^2.8.9"
-  },
-  "keywords": [
-    "robopark",
-    "fleet",
-    "robots",
-    "livekit",
-    "raspberry-pi",
-    "cli",
-    "infinicode",
-    "mesh"
-  ],
-  "author": "Ra Kai'Un",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/chosen-to-build/infinicode"
-  }
-}
+{
+  "name": "robopark",
+  "version": "2.8.27",
+  "description": "RoboPark fleet control CLI — set up, watch, and drive a fleet of talking robots. The operator front-end over the infinicode mesh.",
+  "type": "module",
+  "bin": {
+    "robopark": "./bin/robopark.js"
+  },
+  "files": [
+    "bin/robopark.js",
+    "scheduler",
+    "pi-client",
+    "vision",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "dependencies": {
+    "infinicode": "^2.8.9"
+  },
+  "keywords": [
+    "robopark",
+    "fleet",
+    "robots",
+    "livekit",
+    "raspberry-pi",
+    "cli",
+    "infinicode",
+    "mesh"
+  ],
+  "author": "Ra Kai'Un",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/MrYungCEO/infinicode"
+  }
+}

package/pi-client/README.md

@@ -1,17 +1,17 @@
-# robopark-pi-client — full robot client (reference)
-
-The full on-robot client: enrollment, heartbeat, motor control, and a
-LiveKit publish loop (`livekit_bridge.py`) that joins a standing per-device
-room whenever `production_mode` is on. `pi_ui.py` serves a touchscreen UI
-with a manual "Join Conversation" button — the human-in-the-loop trigger.
-
-This is a reference implementation shipped for Pi deployment; it is not
-currently wired into `robopark setup --robot` (which uses `../scheduler/
-preview_agent.py` for the on-demand preview + vision-trigger flow — see
-`../vision/README.md`). `client.py`'s standing-room model and the scheduler's
-`request-session`-per-trigger model are two different session strategies;
-reconciling them into one is follow-up work, not done here.
-
-Install: `pip install -r requirements.txt` (`livekit`/`livekit-api` are
-commented out — Pi-only, install separately with the `livekit` SDK).
-`install.sh`/`*.service` are Linux/Pi systemd wrappers.
+# robopark-pi-client — full robot client (reference)
+
+The full on-robot client: enrollment, heartbeat, motor control, and a
+LiveKit publish loop (`livekit_bridge.py`) that joins a standing per-device
+room whenever `production_mode` is on. `pi_ui.py` serves a touchscreen UI
+with a manual "Join Conversation" button — the human-in-the-loop trigger.
+
+This is a reference implementation shipped for Pi deployment; it is not
+currently wired into `robopark setup --robot` (which uses `../scheduler/
+preview_agent.py` for the on-demand preview + vision-trigger flow — see
+`../vision/README.md`). `client.py`'s standing-room model and the scheduler's
+`request-session`-per-trigger model are two different session strategies;
+reconciling them into one is follow-up work, not done here.
+
+Install: `pip install -r requirements.txt` (`livekit`/`livekit-api` are
+commented out — Pi-only, install separately with the `livekit` SDK).
+`install.sh`/`*.service` are Linux/Pi systemd wrappers.