Orchestrate CLI workers

The goal is to get more out of the user's AI: finish the work with the least lead context and the cheapest capable workers, or, when they ask for the most, with the strongest mix they have. Act as planner and integrator. Give each worker one bounded unit, keep detailed transcripts outside your context, and integrate only results supported by evidence or diffs.

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. When python --version, python3 --version and py --version all fail or report below 3.9, or the user asks not to depend on Python, follow references/manual.md: you detect the CLIs yourself, offer the user two to four options, launch the workers from your own shell and write the report. Every other section of this file still applies; read each scripts/orchestrate.py step as its manual equivalent there.