Module pi 

Pi coding-agent harness adapter.

Launches pi -p "<prompt>" in non-interactive print mode. The prompt is POSITIONAL — -p is a boolean flag (not the prompt carrier, and not stdin transport like Claude’s stream-json). --no-approve is always passed: --approve trusts project-local extensions/skills/settings that execute UNSANDBOXED (Pi ships no sandbox), and a fresh per-phase worktree establishes no trust decision — that is a security boundary, not a convenience.

No --model/--provider wiring in the launch argv: model/provider selection is Pi’s own. The health check probes the provider a launch will actually use — settings.json’s defaultProvider (this machine: litellm), falling back to Pi’s built-in --provider default (google) when unset — never a hardcoded provider and never “any ready provider in models.json”.

Note: Pi has NO -- end-of-options convention — passing -- is rejected as an unknown option, so the prompt is passed raw. DevFlow’s own stage prompts never begin with -, so the leading-dash hazard (a markdown - [ ] list) is a Phase 37 concern, not something a -- can guard here.

Structs

PiDriver

The modular driver for Pi (37-03): print-mode -p launch, pi auth check health, and the de-Claude-ified workflow-reference prompt. NO JSON unwrapper or monitor/CloseRule integration here — that is 37.1/38 (CONTEXT D-04).