Cross-session messaging turned on late during shutdown no longer publishes a dead socket.
What's wrong with this entry?
If cross-session messaging turns on after startup via a feature-flag refresh, the late setup now checks for shutdown first and tears itself down instead of publishing a socket path that nothing will serve.
- The attempt is reported as
shutdown_discardedrather than as a successful late bind. - Still behind the same feature flag that enables late binding at all.
torn down, not published
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.