feat(pi): orchestrator runTask — per-task pi sessions with in-process queue tools

[gewenyu99]

Implements runTask on the pi harness so the orchestrator runs model-agnostic through pi — pairs with PostHog/context-mill#181 (the flow-scoped agents + step-skills it consumes).

Testing

• check out this branch and the context-mill PR branch (experiment/orchestrator)
• serve context-mill locally: PORT=8770 npm run dev in the context-mill checkout
• point REMOTE_SKILLS_BASE_URL in src/lib/constants.ts at http://localhost:8770 (revert after, it breaks the health-check unit tests while edited)
• copy a fixture app somewhere disposable, e.g. wizard-workbench express-todo, without node_modules
• run from the wizard checkout:

  SNAP_OUT=/tmp/snaps APP_DIR=<app copy> POSTHOG_KEY_FILE=<personal api key file> PROJECT_ID=<project id> \
  WIZARD_CI_FLAG_OVERRIDES='{"wizard-orchestrator":"true","wizard-use-pi-harness":"true"}' \
  npx tsx scripts/tui-snapshots.no-jest.ts
  

• expect in /tmp/posthog-wizard.log: harness=pi (flag) and sequence=orchestrator (flag), then the queue draining
• expect at the end: a 7/8 or 8/8 outro, posthog-setup-report.md in the app, a real dashboard in the project

Full TUI run — 24 frames (7/8 done, 1 reasoned skip, 0 failed, 8m01s, dashboard 1825791)

01-intro — intro — orchestrator + pi flags resolved

02-auth — auth

03-run — run start

04-run — seed planning

05-run — queue seeded, install running

06-run — install

07-run — install done

08-run — init running

09-run — init

10-run — init done

11-run — parallel branch starts

12-run — identify + capture + error-tracking in parallel

13-run — instrumentation

14-run — identify skipped with reason

15-run — instrumentation done

16-run — build — real npm install

17-run — build verifying

18-run — dashboard task

19-run — dashboard insights via posthog_exec

20-run — report writing from handoffs

21-outro — outro

22-outro — outro — 7/8 steps, report on disk

23-mcp — mcp screen

24-slack-connect — slack connect

🤖 Generated with Claude Code