my first exploding message exploded way too fast

I sent a 24h exploding message at time T.

At time T+9 minutes, I received a response indicating that the message had already exploded.

Start by reproducing the reported chat behavior with a message set to expire after 24 hours, then trace the message-expiration handling in the Go client and service. Confirm the reported response at T+9 minutes and identify the timing path involved. Done means a 24-hour exploding message remains available for its intended lifetime and the behavior is covered by an appropriate test.

Written by the indexing model from the issue text.