{"version":"2.1.275","anchor":"runner-session-cleanup-appears-to-be-pure-identifier-churn","canonical_anchor":"runner-session-cleanup-appears-to-be-pure-identifier-churn","heading":"runner session cleanup: appears to be pure identifier churn, no behavioral diff found","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/runner-session-cleanup-appears-to-be-pure-identifier-churn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### runner session cleanup: appears to be pure identifier churn, no behavioral diff found\n\nRunner session cleanup code was renamed internally with no behavioral change found\n\n**What**\n\nThe block of code that handles cleanup when a session fails to spawn or is released\u2014unmounting, running the post-session hook, flushing debug logs, and removing worktree and session state\u2014is structurally the same as before. The only differences found were internal variable renames from the build process.\n\n**Why**\n\nThis appears to be incidental renaming rather than a change to how session cleanup behaves.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}