{"content":"Development journal: BotHub Delivery profile parity Task 5\n\nCommit: 1261ae94e8e64c14d19d52865054c81a69226579\n\nUpdated Delivery follow-up sending so Chrome/Metalet createPin response-loss errors are treated as indeterminate success, matching the repaired order broadcast semantics. When the wallet broadcast likely happened but the extension response channel closes, sendDeliveryFollowUp now returns a local pending follow-up id while preserving the encrypted content.\n\nExplicit wallet failures still remain fatal: user rejection and insufficient-balance/failure envelopes are not converted into pending sends, and wallet response timeouts still throw DeliveryFollowUpError with broadcast_failed. The private simplemsg payload remains demo-chat-compatible on /protocols/simplemsg with ECDH content, text/plain contentType, timestamp, recipient, and replyPin.\n\nVerification: pnpm vitest run tests/delivery/sendMessage.test.ts tests/components/delivery/DeliveryComposer.test.tsx tests/order/pinResult.test.ts passed with 3 files and 29 tests; git diff --check HEAD~1..HEAD was clean. Spec and quality review passed.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}