/ultrareview: counter decremented despite crashed run with no findings

What happened

I ran /ultrareview HEAD~80 (Run 2 of my 3 free runs). The remote agent crashed before producing any findings:

{"error":"Review crashed before producing findings. See session logs for details."}

Despite the crash producing zero output, my free-run counter still decremented. When I attempted to launch another review, the CLI now reports Free ultrareview 3 of 3. — meaning the failed Run 2 was charged against my quota.

Session details

• Crashed session ID: r5qhd71nl
• Trigger: /ultrareview HEAD~80
• Scope reported by CLI: 148 files changed, 5038 insertions(+), 1499 deletions(-)
• Output: error JSON above, no findings, no partial results

Expected behavior

Crashed runs that produce no findings should not decrement the free-run counter. The user receives no value from a crashed review, so charging the quota is incorrect.

Suggested fix

• Refund the counter when the remote agent errors out before producing findings.
• Surface the crash reason to the user (the current error message points at "session logs" the user cannot access).
• Consider an upper bound on scope size (or graceful chunking) so large windows like 148 files don't crash silently.

Workaround

Smaller windows (HEAD~30, ~54 files / ~1.4k lines) completed cleanly in my earlier run, so the crash appears scope-related.