You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
When an inbound cross-session message is held by an explicit setting, the notice names the settings layer responsible instead of giving a single generic cause.
Details
the old single hold cause "explicit-setting" was replaced by source attribution, including managed-setting
policy settings render "Your organization's managed settings set \"crossSessionInbound\" to \"hold\"."
project and local settings render "This repository's settings set \"crossSessionInbound\" to \"hold\" (your own \"accept\" cannot override a repo tightening)."
a WeakMap holds the last-reported cause so a notice is re-emitted only when the cause changes
Evidence
managed-setting
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
