threnody-fullstacklisted

# Threnody full-stack parallel build Threnody has no dedicated "app builder" mode. Use **contract-first DAG planning** so frontend and backend agents align before parallel execution. ## Mandatory: spawn subagents Full-stack orchestration uses the same contract as `threnody-task` and `threnody-swarm`: - **Spawn one host `Task`/`Agent` per subtask** in each wave. - **Never** implement wave work yourself with Write/Edit — even for low-tier integration subtasks. - Expect `host_execution_contract: spawn_subagents` on plan/swarm responses. ## Recommended wave shape ```text Wave 1: Define API contract - OpenAPI spec, shared DTOs, route table - produces: api-contract (openapi.yaml, shared types) Wave 2: Parallel implementation (depends_on wave 1) - Backend service/API handlers consumes: api-contract - Frontend UI + client SDK consumes: api-contract Wave 3: Integration - Wire frontend to backend, smoke tests, fix drift - depends_on: backend + frontend subtasks ``` Frontend and backend run **in the same parallel wave** only after the contract lands — not before. ## Which MCP entry point? | Goal | Tool | Topology | |------|------|----------| | Plan once, host executes | `decompose_task` or `plan_task` | Ask planner for DAG + `depends_on` | | Persistence, budget, resume | `execute_swarm` | `topology: dag` or `auto` | Both return **`host_spawn_waves`** with `spawn_subagents` contract. Spawn one host `Task`/`Agent` per subtask per wave — parallel wave 2