autopilot

From README

Named stage profiles (v1) Select a configured profile only with /autopilot --workflow . A profile is an autopilot-owned stage schedule, not a command, mode, plugin, filename, or separate state identity. Without --workflow, autopilot retains its legacy lifecycle and behavior. Named workflow profiles require Linux with the flock utility in v1 because their transcript evidence boundary uses Linux no-follow file-descriptor traversal and their recoverable mutation lock uses kernel advisory locking. Unsupported environments reject explicit --workflow activation before state mutation; use legacy autopilot instead. Profiles are configured in project or user JSONC as autopilot.workflows. . Every v1 profile has exactly version: 1 and stages; no other profile keys are accepted. The only admitted stage sequences are: ralplan creates the plan consumed by execution; execution creates the implemented workspace required by ralph and qa.