# fix\(web\): stop mis-marking recovered and text-reported tool failures in the v2 work log · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/df71f0824da7d41485ba26d1c30f9856a49a902b)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: df71f0824da7d41485ba26d1c30f9856a49a902b

Requested commit: df71f0824da7d41485ba26d1c30f9856a49a902b

Commit: df71f0824da7d41485ba26d1c30f9856a49a902b

Tree: e8a7988f5f7abf719813c1bccb4e87350853b192

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(web): stop mis-marking recovered and text-reported tool failures in the v2 work log

Ports main's #7999/#7893 failure policy onto the v2 turn-item work log:
output text that reports a failure (command not found, ENOENT, nonzero
exit markers) now flags a row even when the provider item completed
"successfully", while the rendered row judges only its displayed result —
a command that merely greps for failure strings stays calm. Success now
also requires the failure check to pass, so recovered failures no longer
get the blue check.

The server half of #7893 needs no port: CodexAdapterV2 already projects
item.status directly, so a failed item never masquerades as completed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [fca1f3dab227a5dc2b1ff52522031e5adf84a516](https://git.cafe/pingdotgg/t3code/commit/fca1f3dab227a5dc2b1ff52522031e5adf84a516?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/df71f0824da7d41485ba26d1c30f9856a49a902b?format=markdown)