[taras]

Why

An independent reviewer can finish its provider turn with a progress marker instead of a verdict. The workflow needs to give that reviewer one chance to finish the review without treating the marker as a formatting error or starting a new reviewer.

What changes

When a joined review turn returns exactly {"status":"in_progress"}, the workflow saves the reply and asks the same reviewer, in the same conversation, to finish. This one continuation has a five-minute prompt timeout and does not spend the formatting retry allowance. If the continuation cannot finish, the workflow records the hold before asking for a disposition, including under a single-reviewer policy.

How to verify it

• Delivery Markdown tests passed at 5e474e607eb0e6319e4f42ac39fb8a78ac33d706. They exercise the bounded same-session continuation and the single-reviewer failure path with simulated reviewers.
• Fable reviewed the exact commit and returned PASS with no blocking findings.
• Branch CI is pending.

Scope

Stacked on #1203 at 40d6cf0874afa5186ce8f4db6453d23f84450818 to review the continuation separately from the guide and provider launch changes. This applies to independent review only. It does not resume already-held implementation runs, such as #1234, or treat unmarked progress prose as a continuation request.

Scope confirmation

• Every changed file supports the purpose described above.
• Unrelated cleanup and formatting changes are excluded.
• The description matches the final diff and test results.

[github-actions]

PR #1235: Continue a progress-only independent review once

13 files, +212 / -23

Scope

✅ PR scope looks good.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.