runtime-picklisted

# Runtime Pick ## Purpose Help the lead decide which specialist to dispatch and on which runtime. Reduces friction in mixed-runtime projects where the "right" choice depends on task type, cost sensitivity, and runtime capabilities. ## Scope - **In:** task description, project's available agents, project's `.yakos.yml` per-domain rules, agent capability matrix. - **Out:** a single recommendation: `<agent>` on `<runtime>` with one-line reasoning, plus 1–2 alternatives ranked. - Does NOT dispatch — that's the lead's decision after seeing the recommendation. ## When to use - Mixed-runtime project where the operator isn't sure which combo is right for a given task. - Lead's first call into a new task type — getting the routing right early saves a re-dispatch. - Cost-sensitive contexts: should this go on a `cheap` model alias on gemini, or `balanced` on claude? ## When NOT to use - Project has a clear default and no codex/gemini agents — the routing is obvious. - Read-only tasks — the `troubleshooter` or `architect` agent on the default runtime is almost always right. ## Automated pass 1. Read the project's agents: ```sh yakos agents lint --project "$PROJECT" 2>/dev/null yakos start "$PROJECT" --print-agents | jq 'keys' ``` 2. Read the project's .yakos.yml if present (for domain routing): ```sh cat "$PROJECT/.yakos.yml" 2>/dev/null ``` 3. Read the runtime capability matrix: ```sh yakos auth status ``` 4. Score candidate (ag