infinicode 2.8.2 → 2.8.4

package/dist/robopark/serve.d.ts

@@ -9,7 +9,14 @@ export interface ServeOptions {
     foreground?: boolean;
 }
 /** Resolve the actual infinicode CLI entry point so `robopark setup --start`
- *  works even when global bins are not on PATH. */
+ *  works even when global bins are not on PATH.
+ *
+ *  Returns the node executable path and the path to `bin/infinicode.js` inside
+ *  the installed `infinicode` package. We avoid spawning the bare `infinicode`
+ *  command because npm's `.cmd` shim is not reliably resolvable by Node's
+ *  `spawn` without `shell: true` on Windows, and shell concatenation triggers
+ *  a deprecation warning when args are passed.
+ */
 export declare function resolveInfinicodeBin(): Promise<{
     node: string;
     script: string;

package/dist/robopark/serve.js

@@ -23,7 +23,11 @@ function pkgDir() {
 }
 function findScheduler() {
     const candidates = [
+        // When robopark serve is invoked via the robopark wrapper, the wrapper
+        // imports infinicode/robopark, so this code runs from inside the
+        // infinicode package. The scheduler Python files are shipped there.
         join(pkgDir(), 'packages', 'robopark', 'scheduler', 'main.py'),
+        // Fallbacks for local checkout / when robopark is installed standalone.
         join(pkgDir(), 'scheduler', 'main.py'),
         join(process.cwd(), 'packages', 'robopark', 'scheduler', 'main.py'),
         join(process.cwd(), 'scheduler', 'main.py'),
@@ -47,7 +51,14 @@ function findPython() {
     return 'python3';
 }
 /** Resolve the actual infinicode CLI entry point so `robopark setup --start`
- *  works even when global bins are not on PATH. */
+ *  works even when global bins are not on PATH.
+ *
+ *  Returns the node executable path and the path to `bin/infinicode.js` inside
+ *  the installed `infinicode` package. We avoid spawning the bare `infinicode`
+ *  command because npm's `.cmd` shim is not reliably resolvable by Node's
+ *  `spawn` without `shell: true` on Windows, and shell concatenation triggers
+ *  a deprecation warning when args are passed.
+ */
 export async function resolveInfinicodeBin() {
     try {
         // When running from the infinicode package itself, the CLI entry is nearby.
@@ -59,7 +70,8 @@ export async function resolveInfinicodeBin() {
     try {
         // When running from the robopark wrapper, resolve infinicode from npm.
         const { createRequire } = await import('node:module');
-        const require = createRequire(import.meta.url);
+        // createRequire expects a file path, not a file:// URL.
+        const require = createRequire(fileURLToPath(import.meta.url));
         const pkgMain = require.resolve('infinicode/package.json');
         const candidate = join(dirname(pkgMain), 'bin', 'infinicode.js');
         if (existsSync(candidate))
@@ -103,6 +115,7 @@ export async function roboparkServe(opts) {
         env,
         stdio: 'pipe',
         detached: !opts.foreground,
+        shell: process.platform === 'win32',
     });
     let ready = false;
     proc.stdout?.on('data', (d) => {

package/dist/robopark/setup.js

@@ -40,7 +40,9 @@ async function infinicodeArgv(args) {
     const bin = await resolveInfinicodeBin();
     if (bin)
         return [bin.node, bin.script, ...args];
-    // Fallback: assume `infinicode` is on PATH. Will fail clearly if not.
+    // Fallback: assume `infinicode` is on PATH. This will fail on Windows if the
+    // .cmd shim is not resolvable, but the resolved-bin path above is the
+    // intended path for all npm installs.
     return ['infinicode', ...args];
 }
 /** Build a Windows-task-friendly command string from an argv array. */

package/dist/robopark-cli.js

@@ -17,7 +17,7 @@ const config = new Conf({
 });
 const program = new Command('robopark')
     .description('RoboPark fleet control CLI — set up, watch, and drive talking robots')
-    .version('2.8.2');
+    .version('2.8.4');
 program
     .command('scan')
     .description('Auto-discover the fleet and print ready-to-run setup commands')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "infinicode",
-  "version": "2.8.2",
+  "version": "2.8.4",
   "description": "OpenKernel — provider-agnostic AI execution kernel. Native coding agent + mission-driven execution runtime.",
   "type": "module",
   "main": "./dist/kernel/index.js",
@@ -19,12 +19,14 @@
       "types": "./dist/kernel/index.d.ts",
       "import": "./dist/kernel/index.js"
     },
-    "./robopark": "./dist/robopark-cli.js"
+    "./robopark": "./dist/robopark-cli.js",
+    "./package.json": "./package.json"
   },
   "files": [
     "bin/infinicode.js",
     "bin/robopark.js",
     "dist",
+    "packages/robopark/scheduler",
     ".opencode/plugins",
     ".opencode/themes",
     ".opencode/tui.json",

package/packages/robopark/README.md

@@ -0,0 +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

package/packages/robopark/scheduler/Dockerfile

@@ -0,0 +1,24 @@
+# RoboPark Session Scheduler
+FROM python:3.11-slim
+
+WORKDIR /app
+
+# Install dependencies
+COPY requirements.txt .
+RUN pip install --no-cache-dir -r requirements.txt
+
+# Copy application
+COPY main.py .
+
+# Create data directory
+RUN mkdir -p /app/data
+
+# Expose port
+EXPOSE 8080
+
+# Health check
+HEALTHCHECK --interval=30s --timeout=5s --start-period=5s \
+    CMD python -c "import urllib.request; urllib.request.urlopen('http://localhost:8080/api/robots')"
+
+# Run
+CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8080"]