@edgehero/pi-dispatch 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@edgehero/pi-dispatch",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "description": "Self-hosted job harness for the pi coding agent: a BullMQ worker that drains the queue, mints scoped forge tokens, and runs one container per job — plus the pi-dispatch CLI (init, up, doctor, service).",
   "keywords": [

package/src/cli.mjs

@@ -36,7 +36,9 @@ const USAGE = `pi-dispatch — run pi coding-agent flows on your own folders
   pi-dispatch resume       resume taking jobs
   pi-dispatch status       show paused state + job counts
 
-Config comes from the environment (see .env.example); flags override it per run.`;
+Config comes from the environment (see .env.example); flags override it per run.
+Prefer being walked through all of this? The operator panel's /dispatch setup does every step
+with a consent per action:  pi install npm:@edgehero/pi-dispatch-admin`;
 
 export async function main(argv = process.argv.slice(2), env = process.env) {
 	const cmd = argv[0];

package/src/flow-gate.mjs

@@ -30,10 +30,11 @@ const exec = promisify(execFile);
  */
 
 // The skill name charset: lowercase kebab/underscore, 1-64 chars, no dots (so no "..") and no
-// slashes. Mirrors materialize.mjs SKILL_NAME_RE (not exported there) — keep in sync. Validating
-// `flow` against it BEFORE building any path is the traversal choke point: a bad name is denied,
-// never interpolated into a git path.
-const SKILL_NAME_RE = /^[a-z0-9](?:[a-z0-9_-]{0,62}[a-z0-9])?$/;
+// slashes. Validating `flow` against it BEFORE building any path is the traversal choke point: a
+// bad name is denied, never interpolated into a git path. Exported as the single source of truth
+// (issue #92): materialize.mjs imports it, and the admin's setup wizard lists a repo's .pi/skills
+// through it — three keep-in-sync copies would drift exactly where a traversal guard cannot.
+export const SKILL_NAME_RE = /^[a-z0-9](?:[a-z0-9_-]{0,62}[a-z0-9])?$/;
 
 export async function readFlowGate({ folder, flow, sha, git = defaultGit }) {
 	// `sha` is REQUIRED and never defaulted: a missing SHA fails closed rather than resolving HEAD,

package/src/init.mjs

@@ -73,5 +73,6 @@ Next:
   5. pi-dispatch worker                                 # drain the queue
 
 Operator panel (optional): pi install npm:@edgehero/pi-dispatch-admin   then   /dispatch
+  (or let the panel do all of the above: /dispatch setup walks these steps with a consent per action)
 `;
 }

package/src/materialize.mjs

@@ -2,6 +2,7 @@ import { execFile } from "node:child_process";
 import { mkdirSync, writeFileSync } from "node:fs";
 import { dirname, isAbsolute, join, relative } from "node:path";
 import { promisify } from "node:util";
+import { SKILL_NAME_RE } from "./flow-gate.mjs";
 
 const exec = promisify(execFile);
 
@@ -29,9 +30,10 @@ const PI_DIR = ".pi";
 const APPEND_SYSTEM = `${PI_DIR}/APPEND_SYSTEM.md`;
 // A skill directory name: lowercase kebab/underscore, 1-64 chars, no dots (so no "..") and no
 // slashes. This is what makes a traversal name impossible at the source. Matched against the
-// CAPTURED segment only, never the whole path.
+// CAPTURED segment only, never the whole path. The name charset itself is imported from
+// flow-gate.mjs (the exported single source of truth, issue #92); the path form stays local
+// because only the materialiser walks whole tree paths.
 const SKILL_PATH_RE = /^\.pi\/skills\/([a-z0-9](?:[a-z0-9_-]{0,62}[a-z0-9])?)\/SKILL\.md$/;
-const SKILL_NAME_RE = /^[a-z0-9](?:[a-z0-9_-]{0,62}[a-z0-9])?$/;
 
 /**
  * Classify a git tree path into the destination we will WRITE, or null to reject.