{"version":"2.1.221","anchor":"background-session-pin-store-drops-its-legacy-sidecar-migrat","canonical_anchor":"background-session-pin-store-drops-its-legacy-sidecar-migrat","heading":"Background-session pin store drops its legacy sidecar migration","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/background-session-pin-store-drops-its-legacy-sidecar-migrat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Background-session pin store drops its legacy sidecar migration\n\nBackground sessions pinned only by the very old marker file will no longer show as pinned.\n\n**What**\n\nReading the pinned-session set no longer falls back to scanning background session directories for an old marker file.\n\n**Details**\n\n- previously, a missing pins file triggered a scan for a legacy \"pinned\" marker per session, migrated the result into the pins file, and fired a dead-probe event\n- now a missing pins file just writes an empty list and returns an empty set; the probe event no longer exists in the build\n- sessions pinned only by the old sidecar marker would no longer be recognised\n\n**Evidence**\n\n`pins.json`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}