# 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/a365d988537c10a184e491931aea9c3d522f7fd1)

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

Visibility: public

Requested revision: a365d988537c10a184e491931aea9c3d522f7fd1

Requested commit: a365d988537c10a184e491931aea9c3d522f7fd1

Commit: a365d988537c10a184e491931aea9c3d522f7fd1

Tree: 61e0f846032a596fa524e8c77ff49d9b6ca90395

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

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

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