Developing Boof Runner
Boof Runner project layout, packages and development commands: dev, test, typecheck, lint and build.
Project layout
packages/shared task-file format, schemas, lifecycle state machine, atomic store
packages/runner tool adapters, git worktree isolation, the pipeline engine
packages/web Hono server + file-watch SSE; React UI under packages/web/ui
packages/desktop Electron app: boots the server + runner in-process, opens the UI window
bin/ the `boof-runner` CLI: scaffolds data, boots web, ensures a single runnerThe @boof-runner/* packages are consumed from source and bundled into a single self-contained
CLI by tsup; the React UI is built by Vite and served by the Hono server.
For a deeper explanation of Boof Runner's runner responsibilities, architecture, and next steps, see docs/boof-runner.md.
Development
bash
npm run dev # boot from source (web + runner)
npm test # full offline suite (unit + integration + web E2E, mock tool)
npm run typecheck # tsc -b across all packages
npm run lint # prettier --check
npm run format # prettier --write
npm run build # vite build (UI) + tsup bundle (CLI)All pipeline tests drive the mock tool, so CI never makes network calls or burns tokens.