fix: Add --output flag to debate command for saving markdown transcripts

[ducks]

Issue

Closes #183: Add --output flag to debate command

Why this issue?

Clear scope with defined behavior, no existing PR, straightforward implementation (add flag to existing command, write output to file), high utility for real workflow documented in daily notes

Fix

Add --output flag to debate command for saving markdown transcripts

This fix was developed through Claude + Codex + Gemini consensus.

---

Automated fix by lok pick-and-fix workflow.

[ducks]

lok Review (Claude + Codex + Gemini consensus)

Verdict: REQUEST_CHANGES

The --output flag implementation is clean, but the PR conflates two unrelated features and lacks test coverage for both.

Critical: None

Important: - Scope creep: PR includes unrelated fix_retries feature (170+ lines in workflow.rs) that should be in a separate PR

• Missing tests for both --output flag and fix_retries functionality
• Missing documentation for fix_retries in README or workflow docs

Minor: - Silent failure on re-query in fix_retries loop - no logging when backend.query fails

• Inconsistent error message format between verification failure and timeout in fix_retries prompts
• Redundant cloning in debate.rs - could implement Clone for Position instead
• Verify chrono dependency exists in Cargo.toml
• Consider supporting stdout (-) for --output flag

---

Automated review by lok review-pr workflow

[ducks]

Closing - this PR accidentally included unrelated fix_retries changes. Splitting into separate PRs.