{"content":"IDBots dev journal — fix/online-chat-message-order @ 3e36379b8 (3/3)\n\nfix: fulfill owed-reply promises across restarts and escalate give-ups to the owner.\n\nForensics on the 2026-11-21 02:10 dangling promise (session c3171c2c): the turn settled [NO_REPLY], wake 1 fired at 02:25 and re-decided silence — the wake model cannot see its own promise because wait-notice rows are filtered from turn context — wake 2 was scheduled for 04:26 on the generic +2h ladder, and the 03:10 process restart erased the in-memory wake Map. The promise dangled forever with no retraction and no owner signal. Census: 214 wait notices in active sessions, 208 fulfilled, 6 dangling — every dangling case died inside the generic +2h window between wake 1 and wake 2.\n\nFour fixes, one lifecycle: (D1) the wake prompt now carries the exact promise text and forbids [NO_REPLY] while it stands; (D2) broadcast notices record a kv-backed promise ledger plus a transcript sweep seeding pre-ledger promises (24h TTL), and daemon start re-arms the wake chain at its persisted ladder step — restarts no longer kill the retry loop, and stale records self-heal; (D3) promise-bearing rows use a dense [10min,30min,2h] ladder instead of [15min,2h,12h]; (D4) only at final death does the peer-facing retraction fire, together with a session system row and a desktop push telling the human what was promised and that the machine gave up. Boot never writes to the peer chain; >24h promises are retired with a log only.\n\nTests: wake suite extended to 10 cases (final-death retraction + owner notification + D1 injection; delivery settles the ledger; boot restore from ledger; boot sweep seeding; TTL retirement; promise ladder unit). Gates: compile:electron clean; private-chat battery 52/52; bridge-adjacent 75/75; tsx 24/24; test:release-regressions-extra 160+68+22 = 250 tests, 0 failed. Branch now carries A+B+C+D and awaits merge approval.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}