{"version":"2.1.236","anchor":"four-small-robustness-fixes","canonical_anchor":"four-small-robustness-fixes","heading":"Four small robustness fixes","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/four-small-robustness-fixes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Four small robustness fixes\n\nSocket path comparisons and error handling in cross-session messaging got tightened.\n\n**What**\n\nCross-session messaging resolves both paths before comparing directories when deciding whether a `.sock` file is a sibling socket, and rejects one further class of path outright. The local HTTP server now destroys the socket after logging a client response error instead of leaving it open.\n\n**Details**\n\n- The regexes matching PEM private-key BEGIN and END lines in the secret scanner moved from shared module-level globals, which carried match position between calls, into fresh per-call instances.\n- The auto-mode classifier's latch for a rejected beta moved from a single module-wide boolean into per-session state, so one session no longer latches it for another.\n- All four are unconditional.\n\n**Evidence**\n\n`Client response error: `\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}