Devin FoleyandClaude Opus 5.5 7edbc1fc07 fix(server): keep a successor's issue lock when a finalizing native run releases its checkout (#19156) ...

`release_checkout` now clears `checkoutRunId` and the execution lock only when they belong to the committing run, so a successor that claimed the issue while its predecessor was finalizing keeps its claim and passes reviewed-chat attestation.

`attestReviewedExternalChatRun` reports the first failed check as a closed label. Setup failures store it in `resultJson.reviewedChatBinding.denialReason`, and Sentry run-failure diagnostics export it as `execution.reviewedChatBindingDenialReason` (no IDs or text). The error message is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-04 17:49:03 -08:00

..

git-connection-failure.test.ts

Keep proven external connection failures out of Sentry (#15590)

2026-10-08 10:19:40 -07:00

mcp-connection-failure.test.ts

Keep proven external connection failures out of Sentry (#15590)

2026-10-08 10:19:40 -07:00

process-loss-diagnostics.test.ts

Retain bounded orphan process-loss diagnostics (#15475)

2026-10-07 12:05:21 -07:00

run-failure-diagnostics.test.ts

fix(server): keep a successor's issue lock when a finalizing native run releases its checkout (#19156)

2026-11-04 17:49:03 -08:00

run-failure-report.test.ts

fix(sentry): prove a native capacity retry from its successor run (#19051)

2026-11-04 14:38:53 -08:00

sentry-run-links.test.ts

feat(sentry): link run errors to task and run pages (#16803)

2026-10-19 06:47:47 -05:00