Retry malformed review JSON per call

[Vilin97]

A malformed JSON response in one portion forced #394 to restart an entire review. Retry the identical model input at most twice for JSON decoding failures, preserving all completed portions and their evidence. Other worker errors and persistent malformed output still fail. Attempt counts include the failed calls, and unavailable token usage remains explicitly partial.

Validation: all 389 Python tests pass; Ruff check/format and diff checks pass. Tests cover Azure/direct decoding errors, the retry bound, accounting, and a complete portioned review in which only the malformed portion is retried.

A live Azure test injected one format failure, then successfully retried through the deployed worker with the same input.

[greptile-apps]

Advisory cross-file review against Lean Pool's supervisory rubric. This is not by itself a significance, source-verification, or merge verdict.

The PR appears safe to merge, with a non-blocking observability issue in how non-rubric reviews disclose incomplete token accounting after retries.

Findings

1.  Partial usage stays hidden ▶

Summary

• Retries the identical request up to two additional times for recognized direct and Azure decoding failures.
• Keeps unrelated and persistent failures fatal.
• Adds accounting, retry-bound, and portion-preservation tests.
• Updates Azure review documentation, though non-rubric output still needs an explicit partial-usage disclosure after retries.

_{Reviews (1) · Last reviewed commit: "Retry malformed review JSON without repe..."}

[greptile-apps]

Partial usage stays hidden

When malformed output is retried during a non-rubric review, accounted() sets usage to None, but the non-rubric renderer does not explain that the token totals are partial. Refactor, challenge, and solution review comments can therefore hide both the retry and the incomplete accounting, even though successful calls still have known usage. Preserve and display the partial-usage state in this path.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!