@edgehero/pi-dispatch-admin 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -36
- package/dist/index.mjs +30187 -19889
- package/package.json +1 -1
- package/skills/operate-pi-dispatch/SKILL.md +13 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@edgehero/pi-dispatch-admin",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"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.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -57,6 +57,19 @@ Use them like this:
|
|
|
57
57
|
|
|
58
58
|
The confirm is the approval step. Treat a decline as a final, legitimate answer.
|
|
59
59
|
|
|
60
|
+
## Setting up a deployment — `/dispatch setup`, and why you cannot run it
|
|
61
|
+
|
|
62
|
+
When the tools report no reachable deployment (queue unreachable, no configured paths), the fix is the
|
|
63
|
+
first-run wizard — and it is **operator-typed only**: there is no model-callable setup tool, on purpose.
|
|
64
|
+
Tell the operator to type `/dispatch setup`. It will, with a consent step per action: create a deployment
|
|
65
|
+
folder, npm-install the pinned runtime into it, hand the terminal to `pi-dispatch up` (whose own y/N
|
|
66
|
+
prompts gate the docker actions), optionally install the worker as a user-level service, write the
|
|
67
|
+
deployment pointer so the panel finds everything afterwards, and offer a first trigger for the repo the
|
|
68
|
+
session is in. What it will NOT do, ever: write into the operator's repo (the `ai-trigger: allow` line is
|
|
69
|
+
printed for them to commit), accept a credential through a dialog, or run anything with `--yes`.
|
|
70
|
+
Do not try to reproduce the wizard's steps through other tools or shell access — the sequencing exists
|
|
71
|
+
so each mutation carries its own human gate.
|
|
72
|
+
|
|
60
73
|
## Staged packages — `run.packages`, and why you cannot set it
|
|
61
74
|
|
|
62
75
|
When a trigger fires, the job loads the third-party **pi packages the operator staged** into their global
|