robopark 3.1.2 → 3.3.0

package/README.md

@@ -1,95 +1,66 @@
-# RoboPark
-
-RoboPark is the standalone runtime for a fleet of camera- and voice-enabled
-characters. It includes the gateway dashboard, durable scheduler, device
-pairing, LiveKit camera/audio publisher, ElevenLabs session integration, and a
-cross-platform supervisor. It does not require an InfiniCode installation or a
-source checkout.
-
-## Install
-
-```sh
-npm install -g robopark
-```
-
-Node.js 20+ and Python 3.10+ are required. RoboPark creates an isolated Python
-environment in `~/.robopark/venv` and installs the pinned packaged media
-dependencies on first use.
-
-## Three-command setup
-
-On the gateway:
-
-```sh
-robopark --password '<activation-password>' gateway start --public-url https://robopark.example.com
-```
-
-`gateway start` owns both RoboPark surfaces:
-
-- Full Park Control Center: port 47913
-- Private scheduler/API service: port 8080
-
-InfiniCode is not required to render or operate the Park UI.
-
-The gateway prints a complete connection command. Run it once on a device:
-
-```sh
-robopark connect rp1_<token>
-```
-
-Then persist the desired media runtime:
-
-```sh
-robopark start --voice --video --character vixen
-```
-
-Print the gateway command and every verified production bot command at any
-time:
-
-```sh
-robopark commands
-robopark commands --token rp1_<token> --public-url https://gateway.example.com
-```
-
-The packaged production bindings are Barracuda, Jaguar, Magnus, Palladin,
-Panda, Ronin, Titan, Vixen, and Volt. Panda and Ronin intentionally remain
-separate robot identities while sharing their recovered ElevenLabs agent.
-
-`start` writes durable desired state and registers an OS supervisor:
-
-- Linux: systemd with `Restart=always`
-- Windows: Task Scheduler with restart-on-failure
-- macOS: launchd with `KeepAlive`
-
-The supervisor also watches the child media process and gateway heartbeat. A
-crash receives exponential-backoff restart; a live-but-stalled worker is
-recycled after repeated stale heartbeats. A gateway outage does not create a
-restart storm: the media worker keeps its device identity and reconnects.
-
-Use `robopark start --foreground` in development and `robopark status` to read
-the local supervisor state.
-
-## Data and logs
-
-Durable device credentials, desired state, runtime status, logs, and the Python
-environment live under `~/.robopark`. Gateway data defaults to
-`~/.robopark/scheduler`, so upgrading or reinstalling the npm package does not
-replace fleet state.
-
-## Package boundary
-
-RoboPark owns device connectivity, camera/audio, sessions, transcripts, and the
-operator gateway. InfiniCode is an optional management/orchestration layer and
-is not a runtime dependency.
-
-The 3.0 artifact deliberately preserves the current scheduler, Pi client,
-ElevenLabs conversation worker, camera/vision service, screen relay, motor
-bridge, configuration filenames, and service names. Existing enrolled robots
-are grandfathered on upgrade and continue using their current device identity
-and `~/.robopark` state without an activation interruption. New gateways require
-one-time activation; a valid gateway pairing token activates a new robot only
-after enrollment succeeds.
-
-Publish this package with private npm access. The runtime activation gate
-prevents accidental use, but it does not encrypt a tarball after someone has
-downloaded it.
+# robopark
+
+Production architecture, device locks, verified stages, and incident memory
+are recorded in [`../../docs/ROBOPARK_PRODUCTION_MEMORY.md`](../../docs/ROBOPARK_PRODUCTION_MEMORY.md).
+
+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,7 +1,14 @@
 #!/usr/bin/env node
+/**
+ * robopark — fleet control CLI.
+ *
+ * Unlike the previous release, this is not a wrapper: the CLI ships in this
+ * package and has no infinicode dependency. `robopark serve` starts the
+ * scheduler (scheduler/main.py) and the control UI directly.
+ */
 import('../dist/robopark-cli.js').catch((err) => {
-  console.error('robopark: could not load its packaged runtime.');
+  console.error('robopark: failed to start.');
   console.error(err && err.message ? err.message : err);
-  console.error('Try reinstalling: npm install -g robopark');
+  console.error('If this is a source checkout, build it first:  npm install && npm run build');
   process.exit(1);
 });