Held peer messages now cancel their approval prompts cleanly instead of leaving stale ones hanging around.
What's wrong with this entry?
The inbound-hold hook keeps a per-message record with an abortable approval prompt, so held peer messages can be superseded, dropped or released cleanly instead of leaving orphaned prompts.
- Superseded, dropped and released holds have their approval prompts cancelled via the stored abort handle.
- When the approval surface returns, the expiry deadline is re-armed rather than being counted against the time with no surface available.
- An approval or denial that lands after the message was already resolved by a mode or setting change posts a warning instead of acting.
That held message was already resolved before your
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross