feat: open new Linear issue when agent finds unrelated problems

[mr-j90]

Summary

• Agents can now surface unrelated bugs/issues discovered during a run by writing .symphony/findings.json to their workspace
• After each agent turn the orchestrator reads this file, creates a Linear issue per finding (with context linking back to the source issue), then removes the file
• Turn-1 prompts are automatically extended with instructions explaining the findings protocol so agents know how to use it

Changes

• internal/model/types.go — new Finding struct (title, description)
• internal/linear/client.go — FetchTeamID and CreateIssue methods
• internal/orchestrator/orchestrator.go — processFindings helper, wired into both Codex and Claude worker loops; buildTurnPrompt appends findings instructions on turn 1
• internal/linear/client_test.go — tests for FetchTeamID and CreateIssue (success, GraphQL error, success=false cases)

Test plan

• go test ./internal/linear/... passes (includes new TestFetchTeamID_* and TestCreateIssue_* tests)
• go test ./internal/orchestrator/... passes
• Manually verify: place a .symphony/findings.json in a workspace between turns and confirm a new Linear issue is created and the file is removed

🤖 Generated with Claude Code

[linear]

ZYX-78 If our agent finds issues while working on a issue that is unrelated to the current issue we should opena new linear issue with out findings.