You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P1] Preserve send receipts and distinguish rejected, accepted, and unknown delivery #34
Summary: Make Codex/Grok send outcomes machine-readable across rejection, acceptance, post-acceptance interaction failure, and transport ambiguity.
Why: turn IDs and receipts are discarded on some errors; disconnect after turn/start can mean delivery unknown, causing duplicate retries. gbot_send always renders “Sent” and approval handling is connection-wide.
Acceptance criteria: define delivery vs execution states; preserve IDs on all errors; classify post-write loss as unknown; validate acknowledgments; add stable correlation IDs using existing clientNonce/replyToId; scope callbacks; never change approval policy automatically; test lost responses, delayed/unrelated interactions, and malformed acknowledgments.
Activity
P1 bridge follow-ups: send receipts, bounded WS transport, bounded th…
ScriptedAlchemy commentedon Sep 15, 2026
Addressed via merged #40 + follow-up #43 (6 Pro hold then small fixes). Closing if acceptance is satisfied.