lsm / neokai / 22647166951

84%

push

github

feat: mark orphaned sent messages as failed instead of re-dispatching (#179)

* wip: save work in progress from stuck session

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: prevent synthetic/tool_result messages from being re-dispatched on recovery

Skip isSynthetic=true messages and messages with tool_result-only content
in MessageRecoveryHandler to avoid incorrectly re-queuing SDK-internal
messages as orphaned user input on session restart.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* feat: mark orphaned sent messages as failed instead of re-dispatching

When the server crashes mid-flight, messages stuck in 'sent' status were
previously reset to 'saved' for automatic retry on next start. This caused
problems: tool_result messages (SDK-internal) could be re-dispatched, and
any partial side effects from the original run could be duplicated.

New approach:
- Mark orphaned messages as 'failed' so they surface in the UI as "not delivered"
- Skip synthetic (isSynthetic=true) and tool_result-only messages entirely
- User sees what was lost without any automatic re-dispatch

Changes:
- Add 'failed' to SendStatus type and DB CHECK constraint (migration 15)
- Recovery handler marks orphaned messages as 'failed' (not 'saved')
- SDK message query surfaces 'failed' messages to UI with sendStatus field
- SDKUserMessage.tsx shows "not delivered" badge for failed messages
- SDKUserMessage type gets optional sendStatus?: 'failed' field

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* style: apply biome formatting

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2641 of 3114 branches covered (84.81%)

Branch coverage included in aggregate %.

35 of 48 new or added lines in 3 files covered. (72.92%)

21436 of 26650 relevant lines covered (80.44%)

258.09 hits per line