Agent orchestration: Parallel agent coordination with commit lock prevention #17

Problem

When multiple AI coding agents (Cursor, Claude Code, Copilot) work on different issues in parallel, they create merge conflicts and 'commit locks' - constantly rebasing and re-running CI. This is the unsolved problem in the developer ecosystem.

Our Strategic Advantage

OpenGrove sits at the orchestration layer. We know which issues are being worked on, by whom (human or agent), and on which branches. We can:

1. Detect when two agents touch overlapping files
2. Sequence agent work to minimize conflicts
3. Route agents to non-overlapping workstreams
4. Auto-rebase and retry when conflicts occur

Acceptance Criteria

• Track which issues have active branches (via GitHub webhook)
• Detect file-level overlap between active PRs
• AI agent tool: suggestNonConflictingWork() -> returns issues safe to parallelize
• Dashboard indicator showing 'agent contention score'
• This is the v2.0 flagship feature