The headless RPI phase runner duplicated what `ao rpi` already does,
without its ratchet tracking, telemetry, or phased-state integration.
The real value was the test helper improvements and standards doc.
- Add bin/run-rpi-headless.sh: chains RPI phases as separate headless
Claude invocations, each invoking the actual skills (/research, /plan,
/crank, /vibe, /post-mortem) so the full skill chain executes
- Add docs/contracts/headless-invocation-standards.md: documents when to
use --dangerously-skip-permissions (skill chains) vs --allowedTools
(controlled prompts), timeout strategy, and session chaining
- Update test-helpers.sh: add --no-session-persistence, --max-budget-usd,
configurable ALLOWED_TOOLS env var (default: skip-permissions for tests)
- Update release-smoke-test.sh: add --no-session-persistence,
--max-budget-usd, scoped --allowedTools for fast test (no skill exec)
Key insight: skills chain skills — --allowedTools constrains the entire
session including tools used inside skill execution, so skill-invoking
workflows must use --dangerously-skip-permissions with timeout/budget
as the safety rails instead.
Boden Fuller