fix(server): stop boundary claims on hook abort and read only queued runs

An aborted PostToolBatch or Stop hook interrupts its claim; the claim no
longer recovers that interruption and goes on promoting updates whose hook
response Claude has discarded. Only promotion refusals are ignored.

The claim runs at every tool batch, so it now reads only queued runs and
their messages (a new runStatuses record filter) instead of every user
message and run in the thread.

The t3_thread_send description says a queued Claude update may join the
running turn after its current tool call, and that t3_thread_wait follows it.

Co-Authored-By: Claude Opus 5.5 at high effort <noreply@anthropic.com>
Co-Authored-By: GPT-6.1 Sol at xhigh effort, review subagent <noreply@openai.com>
d4ac7c1029Alb11747 committed on 10/20/2026, 6:42:01 AMparented47e6f

Checks

5 successful · 1 skipped
All checks passed
4 files changedLine totals unavailable