@edgehero/pi-dispatch-admin 4.0.0 → 4.1.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 +19 -4
- package/dist/index.mjs +3355 -694
- package/package.json +2 -2
- package/skills/operate-pi-dispatch/SKILL.md +7 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@edgehero/pi-dispatch-admin",
|
|
3
|
-
"version": "4.
|
|
3
|
+
"version": "4.1.0",
|
|
4
4
|
"description": "Operator console for pi-dispatch, as a pi extension: a /dispatch panel over the queue, spend caps, scoped limits, run history and insights, editable cron and GitHub, GitLab, Forgejo and Azure DevOps triggers, pause windows, and human-confirmed tools your AI can operate.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -59,7 +59,7 @@
|
|
|
59
59
|
"@earendil-works/pi-coding-agent": "*"
|
|
60
60
|
},
|
|
61
61
|
"devDependencies": {
|
|
62
|
-
"@earendil-works/pi-coding-agent": "1.0
|
|
62
|
+
"@earendil-works/pi-coding-agent": "1.1.0",
|
|
63
63
|
"@edgehero/pi-dispatch": "*",
|
|
64
64
|
"esbuild": "^0.28.1",
|
|
65
65
|
"typebox": "1.3.27"
|
|
@@ -32,6 +32,13 @@ Observe (no approval needed):
|
|
|
32
32
|
- `dispatch_allocations` - the allocation envelope (a dollar total per window and a floor per project) and the
|
|
33
33
|
split applied inside it: each project's share and spend in micro-dollars, the applied plan's id and writer,
|
|
34
34
|
and the last 20 outcomes. It never returns the reasons a plan gave; the operator reads those in the panel (`b`).
|
|
35
|
+
- `dispatch_capacity`: how busy each worker host was over `window` (`24h`, `7d` or `30d`, default `7d`; `host`
|
|
36
|
+
narrows to one): busy and idle share, jobs at once, memory and CPU promised against the budget, CPU used, the wait
|
|
37
|
+
for a slot and the busiest projects, as `text` and as the `report`. It counts this deployment's jobs only (a machine
|
|
38
|
+
busy with other work reads as idle), and history before its sources start is `missingMs`, never idle; a host that
|
|
39
|
+
is new, or was down, inside history that is there reads as idle for that time. Say so when the coverage is cut,
|
|
40
|
+
local only, or names running jobs not counted, rather than reading a quiet host into it. The operator sees
|
|
41
|
+
the same 7 days per host, under its running jobs, in the panel (`u`).
|
|
35
42
|
|
|
36
43
|
Control (no approval needed — reversible and money-safe):
|
|
37
44
|
- `dispatch_pause` — stop starting new jobs (running ones finish). This is "turn dispatch off".
|