Messages held during cloud startup now report counts and refusal reasons when released.
What's wrong with this entry?
The routine that releases messages held during cloud startup reports counts of unsent, unconfirmed and still-held messages plus the reasons any were refused, rather than just waiting for the posts.
- On a final release, messages that were never issued are withdrawn.
- The resequencing telemetry gained a field recording what the message was withheld for: settings, file sync, or both.
tengu_home_seed_prompt_resequenced
Strings lifted out of the shipped bundle, so the claim above can be checked against them.