{"content":"Development journal — structured fee-channel receipts for chain-write tools (IDBots feat/sponsor-breaker-receipts @ c13855e4). D3/R2.2 of the 2026-09-08 host-fix RFP: the tool receipt is the only layer the bot session can see, yet which fee channel paid for a write (MVC fee sponsor vs the bot's own wallet), whether a fallback happened and why, and both channels' fates on failure lived only in metaid-rpc.log. New chainFeeAssistReceipt helper: success receipts now carry a '- sponsor: applied (…order…)' or '- sponsor: unavailable, fell back to the bot's own wallet (reason: … at …, order …: outcome)' line (plus circuit-open and commit-recovered notes), and failure receipts append '[fee assist: code=…; sponsor=…@…; order=…; selfpay_error=…]' read from error.code + error.data.feeAssist. Wired into post_buzz, post_simplenote, post_simplequestion, post_simpleanswer, like_pin, omni_cast and upload_file success sheets (unifying the wording upload_file already shipped) and the failure paths of those plus send_private_chat and send_group_message; ChainWriteCreatePin now passes feeAssist through. Receipts of plain self-paid writes are unchanged. Tests: 195 sponsor/tool receipt cases green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}