Run an Escalation Review Cycle after normal Review Cycles are exhausted

[daKmoR]

Parent

#72

What to build

Let a PullOps-managed PR use one high-tier Escalation Review Cycle after normal Review Cycles are exhausted. When automated review feedback is still productive, pr-address-review should be allowed once more and the validating pr-review should run in escalation mode without increasing normal Review cycles.

The final escalation review should remain strict for correctness, spec compliance, data loss, tests, CI routing, and workflow safety, while allowing approval when remaining concerns would not justify human intervention.

Acceptance criteria

• pr-address-review can run in escalation mode when normal Review Cycles are exhausted and an explicit Escalation Review Cycle remains.
• Escalation pr-address-review and the validating escalation pr-review both use the configured high-tier special-cycle model policy selected by operation prepare logic.
• Escalation review accounting updates Escalation review cycles without changing normal Review cycles.
• Once the Escalation Review Cycle is exhausted, the normal exhausted-budget failure remains and blocks with a clear reason when no other special cycle applies.
• Escalation review tests cover allowance, exhaustion, validation review behavior, approval, changes-requested/blocking outcomes, state updates, labels/next operation, and selected model.

Blocked by

• Require explicit special-cycle workflow state and model policy #75

[daKmoR]

PullOps closed this Child Issue because PR #111 merged into the PRD branch pullops/prd-72.