Issue builder commits on main are not reviewed

[markgar]

Problem

The dedicated issue builder (builder-N with --role issue) works directly on main, but no reviewer watches its commits:

• Branch-attached reviewers only watch builder-N/* feature branches — the issue builder doesn't use a feature branch.
• No reviewer is spawned for the issue builder — the orchestrator explicitly skips it (milestone_builder_count = num_builders - 1).
• Milestone reviewer only triggers on completed milestones, not arbitrary main commits.

This means the issue builder's fix commits go in unreviewed.

Options

1. Have the issue builder work on its own branch with a dedicated reviewer
2. Have an existing reviewer also watch non-builder commits on main
3. Accept the gap — fixes are for already-reviewed/filed issues, so they're implicitly review-driven

Context

Discovered while monitoring a 4-builder Stretto run (3 milestone builders + 1 issue builder). The issue builder picked up 3 findings from reviewer-1 and fixed them directly on main with no review.

Relevant code: src/agentic_dev/orchestrator.py lines 258-261

[markgar]

Note: reviewer clone already exists for the issue builder

The orchestrator already clones a reviewer-N/ directory for the issue builder — it just never launches a reviewer in it. This happens in three places:

1. New project flow (orchestrator.py ~line 379): range(2, num_builders + 1) clones reviewer-N for every builder including the issue builder
2. _clone_all_agents (~line 112): range(1, num_builders + 1) does the same
3. _pull_all_clones (~line 131): same range, creates the clone if missing

So if option 1 (dedicated branch + reviewer) is chosen, the clone directory is already there — just need to launch a reviewer process in it.

If option 1 is NOT chosen, these three loops should be fixed to use num_builders - 1 for reviewers (when num_builders > 1) to avoid creating a wasted clone.