fix: explain recovery decisions and retain completed answers #160

Merged
severus-snape merged 2 commits from fix/actionable-recovery-integrated into main 2026-10-29 22:20:21 +00:00
Collaborator

Recovery notices now name the known cause, retained task/state and concrete requested operator decision; no raw provider diagnostics or fabricated permission failure. Preserve independently positive completed verdict for actual answered foreground turns, never infer startup completion without reply evidence or overwrite explicit checkpoints. Serial integration preserves PR159 bounded retries and delays attention until exhaustion.

Owner integration65 focused tests passed, typecheck/build passed. Worker full suite stopped120s with two failures: no fullPASS claimed. Installed formal ReviewService actual integrated cwd/existing home/history passed fingerprintb88fd90f536520703e6d9355223a77c48760993701304838c5d4077b89db17f0 findings[] and exact assertAllowed commit/push/publish.

Candidate4f1b16085cc8930313ff4d7a1bde8420f16108e8 baseb95cc05. Scheduled GitOps rollout only.

Recovery notices now name the known cause, retained task/state and concrete requested operator decision; no raw provider diagnostics or fabricated permission failure. Preserve independently positive completed verdict for actual answered foreground turns, never infer startup completion without reply evidence or overwrite explicit checkpoints. Serial integration preserves PR159 bounded retries and delays attention until exhaustion. Owner integration65 focused tests passed, typecheck/build passed. Worker full suite stopped120s with two failures: no fullPASS claimed. Installed formal ReviewService actual integrated cwd/existing home/history passed fingerprintb88fd90f536520703e6d9355223a77c48760993701304838c5d4077b89db17f0 findings[] and exact assertAllowed commit/push/publish. Candidate4f1b16085cc8930313ff4d7a1bde8420f16108e8 baseb95cc05. Scheduled GitOps rollout only.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!160
No description provided.