pi-dispatch v0.7.0
The first-run wizard (issue #92), plus a front page that reads like an overview again.
New
/dispatch setupin the admin extension: with nothing butpi install npm:@edgehero/pi-dispatch-admin, the console detects there is no deployment anywhere and builds one. Pick a folder, consent to an npm install of the pinned runtime, watchpi-dispatch uprun its own prompts in your terminal, optionally install the worker as a user-level service, optionally arm a first trigger for the repo you are sitting in (its flow picked from that repo's.pi/skills/), then land in the panel. Every step asks first and can be declined. Nothing is ever written into your repo (theai-trigger: allowline is printed for you to commit) and no credential passes through a dialog.- Deployment pointer: setup writes
~/.pi/agent/pi-dispatch-deployment.json(override withPI_DISPATCH_DEPLOYMENT_FILE) so the panel finds the deployment from any directory afterwards. Paths only, never credentials; your own env vars always win, key by key; a broken or newer pointer degrades to the old behavior with a one-line notice. - Detection on bare
/dispatch: a configured deployment with a down queue keeps the unreachable banner as before; the setup offer appears only when there is truly nothing. A one-time startup notice points new installs at the command.
Changed
- Both READMEs compacted: the root README went from 769 to 354 lines with every screenshot and diagram kept; the depth lives in the docs/ pages.
Ships as @edgehero/pi-dispatch-admin@0.4.0 and @edgehero/pi-dispatch@0.1.1.
Changes
- chore(release): pi-dispatch 0.7.0, admin 0.4.0, worker 0.1.1
- docs: compact both READMEs
- feat(admin): /dispatch setup -- first-run wizard, detection, and a once-ever nudge (issue #92)
- feat(admin): deployment pointer -- the panel finds a deployment built elsewhere (issue #92)
- refactor(worker): export SKILL_NAME_RE from flow-gate as the single source of truth (issue #92)
Full changelog: v0.6.0...v0.7.0