Debug

When a Symphony run stalls, retries endlessly, or fails mysteriously, this walks you through the correlation dance between Linear tickets and Codex sessions. You'll grep symphony.log for issue_identifier keys, extract session_ids, and trace the lifecycle from startup through completion or failure. The investigation flow is methodical: narrow by ticket, pull the timeline, classify whether it's a stall loop or turn failure or worker crash, then capture evidence with the right identifiers. The commands are straightforward rg oneliners, and the guidance on reading Codex session logs as a three-stage lifecycle (start, stream, terminal event) is actually clarifying. It assumes you know the Symphony runtime already but saves you from wandering through logs blind.