Internal peer and session-freshness tracking was rewritten from identity-based caches to id-based ones with a new offered set
Two internal tracking mechanisms, one for tracking peers in a shared ledger and one for tracking remote sessions, were rewritten. They previously used WeakMap-based storage keyed by object identity, with a per-entry invalidation flag; they now use an id-keyed store built around an incrementing global counter (an "era"). The remote session tracker also gained a new offered set, which is cleared whenever a session registers.
This is an internal rework of how Claude Code tracks freshness and offers for peers and remote sessions. The finding doesn't specify what user-visible problem it fixes, but it changes the underlying bookkeeping these features rely on.
What user-visible effect this internal rework has, if any, is not stated.