**Problem** Messages the device sends on its own (bot auto-replies, on-device keyboard input) never reach the companion app — there's no frame for them. Mainline firmware doesn't send messages on its own, so this doesn't affect it directly — but it would make life easier for custom firmwares that do. **Proposal** Add `RESP_CODE_CONTACT_MSG_SENT_V3` / `RESP_CODE_CHANNEL_MSG_SENT_V3`, reusing the RECV_V3 layout with the pubkey field meaning *recipient* instead of sender: ``` [0] RESP_CODE_CONTACT_MSG_SENT_V3 (new code) [1..3] reserved [4..9] recipient pubkey prefix [10] path_len used, or 0xFF [11] txt_type [12..15] timestamp (uint32) [16..] text (UTF-8) ``` Delivery reuses the existing pipe: offline queue → `PUSH_CODE_MSG_WAITING` → app's existing `CMD_SYNC_NEXT_MESSAGE`.