Orchestrate CLI workers

Finish the work with the least lead context and the cheapest capable workers, or the strongest mix when the user asks. Plan, delegate bounded units, and integrate results supported by evidence.

• Playbook = the phases and roles.
• Profile = which models each tier uses (base, savings, aggressive).
• Goal = how eagerly to delegate while a mode is on (save, balanced, max).
• Runner strategy = how one wave runs (economy, balanced, quality, research, parallel, rescue).

Choose the backend

Honor an explicit request for the local skill or no MCP. It always wins. Otherwise run scripts/orchestrate.py policy show and use its backend: skill selects this runner, mcp selects alethe_* tools when present, and auto prefers those tools when available.

Python is optional. If python --version, python3 --version and py --version all fail or report below 3.9, or the user asks, follow references/manual.md for detection, options, background workers and reporting. All other sections still apply through manual equivalents.