threnody-routinglisted

# Threnody routing Threnody is a **meta-harness**: the MCP host shell executes work; Threnody coordinates routing, planning, and optional utility delegation. The portable contract is `host_spawn` / `host_spawn_waves`. Claude Code Dynamic Workflow emission is an optional Claude-only optimization; do not depend on it for behavior that must work across Codex, Cursor, Copilot, Junie, or OpenCode. ## Default path (always try first) 1. Call `route_task(task=...)` (MCP: Threnody). 2. Read `execution_hint.mode`: - `host_native` — use host `Task`/`Agent` (`host_spawn` in response). - `delegate` — only when `delegation_utilities_enabled` is true and targets are utilities. 3. Follow `recommended_action` and `host_native_model` / `host_native_method`. ## Handoff precedence When a prior `plan_task`, `fleet_plan`, or `execute_swarm` response includes `host_spawn_waves` or `host_execution_contract: spawn_subagents`, **always spawn** per agent — `host_native_method: direct_edit` does not apply. `direct_edit` is only for lone `route_task` results with no pending handoff (`execution_hint.active_handoff` is not set). ## Utility-only delegation `execute_subtask` is **not** general cross-CLI orchestration. | Condition | Result | |-----------|--------| | `delegation_utilities_enabled: false` | No utility delegation; host-native only | | Enabled + `provider_id` in allowlist | OpenCode, Aider, local loopback endpoints | | Host CLI as target (Copilot, Codex, Cursor, Junie, Claude) | *