In a multiplexed gateway the final send runs after the routed profile scope is reset, so delivery rows went to the launch profile while the same turn's reply_latency went to the owner. start_reply_clock now also remembers the owning home per (platform, chat) in a bounded map that outlives the clock, and records_delivery submits through it.