YAML orchestrator duration values: inconsistent parsing between versions

[denash84]

Problem

The orchestrator: section in YAML config files has inconsistent duration parsing behavior across agentpipe versions:

• v0.7.0 (brew release): Silently ignores turn_timeout and response_delay values entirely. CLI flags (--timeout, --delay) are the only way to set these.
• Patched/HEAD binary: Requires Go time.Duration format strings (e.g., 120s, 2s). Plain integers like 120 cause a startup crash:

ERR failed to load configuration error="failed to parse config file: yaml: unmarshal errors:
  line 51: cannot unmarshal !!int `120` into time.Duration
  line 52: cannot unmarshal !!int `2` into time.Duration"

Impact

• Users writing YAML configs don't know if turn_timeout: 120 or turn_timeout: 120s is correct
• The official example (examples/codex-brainstorm.yaml) uses 60s format, but v0.7.0 ignores these values anyway
• No documentation clarifies which format to use or that CLI flags are required in v0.7.0

Suggested fix

1. Accept both formats: integers (as seconds) and duration strings (120s)
2. If YAML values are actually parsed, document that CLI flags override them
3. If YAML values are intentionally ignored in v0.7.0, document that too

Environment

• agentpipe v0.7.0 (brew) vs patched binary from HEAD
• macOS (arm64)