fix: retry inconclusive recovery checks honestly #194

Merged

severus-snape merged 1 commit from fix/recovery-inconclusive-real-behavior into main

2026-10-31 21:15:28 +00:00

severus-snape commented

2026-10-31 21:14:44 +00:00

Collaborator

Purpose

Fix actual recovery retry behavior: distinguish technical assessment failure from semantic uncertainty, retry inconclusive checks, and preserve actionable technical attention. Imports only the necessary diagnostic path from #178; no unrelated branch history.

Base f56f80289c; reviewed final tree 75aff60551; eight files. Current main matches the base, no production integration conflict.

Verification

Independent exact-patch review: no P0/P1; eight focused tests green versus two pass/six red on base. Fresh owner ReviewService review passed without findings; original #178 round retained and attributed, 2/3 rounds consumed, no reset/grant. Exact changeset fingerprint 34baadd50a1dbb56188b7b60cb0a354f9da90de9b69e82d43ea95fda614b5475 stable after commit. Fresh typecheck and focused tests pass. Regular image CI remains the full-suite/build/release boundary; absent premerge status is not claimed as green.

Explicit P2 limitation

Many distinct uncertain tasks can still produce many notices. This is not a universal classifier correction or full recovery-notification spam fix. The optional cross-task UX redesign does not block the correct retry slice. Technical failure versus semantic uncertainty remains honest.

#178 remains unchanged; this PR incorporates its necessary diagnostic code with the actual behavior fix. No claim that its previous approval covers this tree.

## Purpose Fix actual recovery retry behavior: distinguish technical assessment failure from semantic uncertainty, retry inconclusive checks, and preserve actionable technical attention. Imports only the necessary diagnostic path from #178; no unrelated branch history. Base f56f80289ca21a2efc55501c5957eaa67e59d94e; reviewed final tree 75aff60551f4259f04c98d25fd2c11ec977766d4; eight files. Current main matches the base, no production integration conflict. ## Verification Independent exact-patch review: no P0/P1; eight focused tests green versus two pass/six red on base. Fresh owner ReviewService review passed without findings; original #178 round retained and attributed, 2/3 rounds consumed, no reset/grant. Exact changeset fingerprint 34baadd50a1dbb56188b7b60cb0a354f9da90de9b69e82d43ea95fda614b5475 stable after commit. Fresh typecheck and focused tests pass. Regular image CI remains the full-suite/build/release boundary; absent premerge status is not claimed as green. ## Explicit P2 limitation Many distinct uncertain tasks can still produce many notices. This is not a universal classifier correction or full recovery-notification spam fix. The optional cross-task UX redesign does not block the correct retry slice. Technical failure versus semantic uncertainty remains honest. #178 remains unchanged; this PR incorporates its necessary diagnostic code with the actual behavior fix. No claim that its previous approval covers this tree.

severus-snape added 1 commit

2026-10-31 21:14:45 +00:00

fix: retry inconclusive recovery checks without false technical attention 4b92023054

severus-snape merged commit 102e6b16f7 into main

2026-10-31 21:15:28 +00:00

severus-snape referenced this pull request from a commit

2026-10-31 21:15:30 +00:00

Merge pull request 'fix: retry inconclusive recovery checks honestly' (#194) from fix/recovery-inconclusive-real-behavior into main