Document the key reliability gaps and recommended solutions for handling
runtime loss and app restart in orchestration workflows:
- Treat message waits as replayable database queries with reconnect support
- Close the read-before-response window via cursor/receipt protocol
- Persist coordinator identity on dispatches for stable routing
- Add startup reconciliation to preserve live workers and fail only definitive exits
- Extend idempotency to mutations like worktree.create
Recommends incremental approach: recovery semantics (I0), transport resume
with replay (I1), identity-complete dispatches and startup reconciliation
(I2), and durable idempotent mutations (I3).
Status: Brainstorm/recommended design, not an implementation plan of record.
Jinjing
68079db5fd