Session storage is per-host now, so exit handling registers once instead of repeatedly.
What's wrong with this entry?
The single shared session-storage object was replaced by a per-host holder, with the practical effect that exit handling is now registered once instead of repeatedly.
- The holder exposes the writer-health failure streak, degraded-store state, exit re-stamp providers, exit drains and a new subscription for when a session file has been written to disk.
- The exit re-stamp and flush paths return early if the host check fails, and the process
exitlistener is only added when one is not already registered.
sessionFileMaterialized
Strings lifted out of the shipped bundle, so the claim above can be checked against them.