@edgehero/pi-dispatch-admin 0.2.0 → 0.3.0

package/README.md

@@ -66,7 +66,16 @@ Then run pi and open `/dispatch`. Point it at your deployment with `VALKEY_URL`
 
 ## Get the whole thing
 
-The queue, worker, container image, and GitHub webhook receiver — the actual service — are in the main repo. **Start there:**
+The service this console drives is a sibling install away — no clone needed:
+
+```bash
+mkdir my-dispatch && cd my-dispatch
+npx @edgehero/pi-dispatch up      # consented setup pass: job image, Valkey, config scaffold, preflight
+npx @edgehero/pi-dispatch worker  # drain the queue (its own terminal, or `service install`)
+```
+
+(`@edgehero/pi-dispatch` is the worker + CLI; `@edgehero/pi-dispatch-receiver` is the webhook edge for
+forge triggers.) The container image, docs, specs, and SECURITY.md live in the main repo. **Start there:**
 
 ### → **https://github.com/edgehero/pi-dispatch**
 

package/dist/index.mjs

@@ -5220,9 +5220,13 @@ function resolvePaths(env = process.env) {
     valkeyUrl: env.VALKEY_URL ?? "redis://127.0.0.1:6379",
     logsDir: env.PI_LOGS_DIR || defaultLogsDir(),
     settingsFile: settingsFilePath(env),
-    triggersPath: env.PI_TRIGGERS_FILE ?? "deploy/triggers.json",
-    pauseWindowsPath: env.PI_PAUSE_WINDOWS_FILE ?? "deploy/pause-windows.json",
-    subscriptionsPath: env.PI_SUBSCRIPTIONS_FILE ?? "deploy/subscriptions.json",
+    // Cwd defaults match what `pi-dispatch init` scaffolds (and, since issue #80, what the receiver
+    // reads), so a deployment folder works without env wiring when pi is launched from it. The old
+    // `deploy/…` defaults pointed at the repo's committed EXAMPLE files — right only from a checkout
+    // root, and silently wrong (demo triggers) everywhere else.
+    triggersPath: env.PI_TRIGGERS_FILE ?? "./triggers.json",
+    pauseWindowsPath: env.PI_PAUSE_WINDOWS_FILE ?? "./pause-windows.json",
+    subscriptionsPath: env.PI_SUBSCRIPTIONS_FILE ?? "./subscriptions.json",
     // The operator's global pi overlay dir (REQ-GLOBAL-PI-OVERLAY), where the staged third-party pi
     // packages live under `packages/`. `|| null` so unset AND empty both read as "no overlay" -- the
     // normal deployment, in which no trigger can arm any package.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@edgehero/pi-dispatch-admin",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Operator console (a pi extension) + skill for pi-dispatch: run the pi coding agent as a self-hosted service. A /dispatch TUI for the queue, spend caps, run history, editable GitHub, GitLab, Forgejo and Azure DevOps triggers (cron/label/comment/PR/MR/work item), and scheduled pause windows — plus AI-operable, human-confirmed controls. Runs against a live pi-dispatch deployment.",
   "keywords": [
     "pi-package",
@@ -58,7 +58,7 @@
   },
   "devDependencies": {
     "@earendil-works/pi-coding-agent": "0.80.7",
-    "@pi-dispatch/worker": "*",
+    "@edgehero/pi-dispatch": "*",
     "esbuild": "^0.28.1",
     "typebox": "1.1.38"
   }