3708c4f6ce
* fix(mobile): report interrupted native chat sends as delivery-unknown, not failed A terminal.send interrupted mid-flight showed a definite "Message not sent" even when the desktop may have already delivered the text. Three paths were misclassified as definite failures: - Logical relay/direct cutover: migrateTo rejects in-flight requests with LogicalClientCutoverError, which mapped to 'rejected'. Now maps to 'unknown' (held unconfirmed + transcript-echo verification; never retried since terminal.send is non-idempotent). - Suspend/close of a half-open session: the stable logical client blanket- rejected in-flight pendings with plain 'Client suspended'/'Client closed', preempting the physical layer's delivery-unknown marking. It now lets the physical close settle them, so post-write failures stay marked and pre-write failures stay definite. - Relay path: mobile-relay-rpc-session never marked delivery ambiguity at all (timeout, close, link failure). Post-write rejections are now marked; pending entries only exist after the frame reached the authenticated link. Permission, ask-answer, and cancel-Escape surfaces now show "unconfirmed — check chat before retrying" instead of a definite "not sent" on ambiguous outcomes (still not-accepted, never retried). Also consolidates a private copy of isLogicalClientCutoverError in worktree-create-retry. Co-authored-by: Orca <help@stably.ai> * chore(skills): regenerate skill-bundle manifest artifacts --------- Co-authored-by: Orca <help@stably.ai> |
||
|---|---|---|
| .. | ||
| app-icons | ||
| build | ||
| darwin/bin | ||
| icon-source | ||
| linux | ||
| notification-sounds | ||
| onboarding/feature-wall | ||
| skills | ||
| tray | ||
| win32/bin | ||
| claude.webp | ||
| ghostty.svg | ||
| gremlin.webp | ||
| gwindows_logo.svg | ||
| icon-dev.png | ||
| icon.png | ||
| logo.svg | ||
| minimax-icon.svg | ||
| openclaude-logo.png | ||
| opencode.webp | ||
