implementation-dispatchlisted

# Symphony Implementation Dispatch Use this as Symphony's second lane: approved Linear work packet in, fresh implementation thread out. ## Contract - Dispatch only after the requirement is approved and represented in Linear, or Pedro explicitly asks to create the issue and dispatch in the same step. - Do not implement product code in the current thread. - Create a new Codex thread so the implementation agent has fresh context and Pedro can follow up there. - The Linear issue is the implementation source of truth; source messages and docs are pointers the implementation agent must reread. - The implementation thread remains the default owner for later review rework and merge/release execution. When Pedro approves merge, the parent Symphony thread should send the merge request back to this worker thread instead of merging from the parent thread. ## Preconditions Before dispatching: 1. Verify the Linear issue title, state, URL/ID, and scope. 2. Verify the target repo/worktree path and branch expectations when available. 3. Check whether an active worker, branch, PR, or thread already exists for that issue. If one exists, report it instead of starting a duplicate unless Pedro asks for a restart. 4. If the issue was materially rewritten after work started, make the restart boundary explicit. ## Thread Tools When running inside Codex, search for the thread-management tool before dispatching: - `create_thread` - `send_message_to_thread` - `set_thread_ti