auto

Run the full pipeline autonomously per .saas-factory/config.json. Tip: /saas-factory:go "" wraps brief→init→auto in one command. Announce the plan, then loop. $ARGUMENTS may cap the run (stop-after) or resume (continue).

Loop (resumable — state is all on disk):

1. No store? → run /saas-factory:init (this is a hard human gate: stack + config interview).
2. No approved REQs? → /saas-factory:brainstorm or :import (human gate for approval unless gate=yolo and REQs came from an import file).
3. sf active-phase empty? → next planned phase → building; none planned? → /saas-factory:plan next slice. All phases approved + no REQs left → DONE: final integrator pass + summary + total spend.
4. Guards before every batch: sf budget check (exit 2 → pause, present spend + options: raise cap / continue once / stop). Circuit breaker: sf phase-stats fail ratio ≥ config threshold → pause phase, escalate with the failed notes (the plan is wrong — do not brute-force it).
5. /saas-factory:build (canary first — if the canary fails twice, treat as circuit-break: re-plan before building the rest of the phase).
6. Phase tasks all verified → /saas-factory:demo. Gate per config.phases.gate: strict = human reviews every phase; standard = human reviews demo, auto-continue if approved quickly; yolo = auto-approve on green e2e + screenshots, checkpoint, continue — but ALWAYS stop for: budget, circuit breaker, canary failure, sf failed escalations, and the final phase.
7. Checkpoint via /saas-factory:phase approve (which also runs the retrospective — the factory gets stricter every phase), next iteration.

Report one line per iteration (phase, verified/total, spend). Long runs: state survives /clear and new sessions — rerun /saas-factory:auto continue.