{"version":"2.1.271","anchor":"runner-session-management-cosmetic-renames-only","canonical_anchor":"runner-session-management-cosmetic-renames-only","heading":"Runner session-management: cosmetic renames only","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/runner-session-management-cosmetic-renames-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Runner session-management: cosmetic renames only\n\nSelf-hosted session runner code was renamed internally with no behavior change found\n\n**What**\n\nThe code that manages self-hosted session runners (handling inference token refresh, spawning and monitoring child processes, and guarding against stale runner instances) was reorganized internally with different variable names. The observable log messages, such as \"epoch fence tripped\" when another runner has taken over, and the session failure codes, are unchanged.\n\n**Why**\n\nThis is internal cleanup only; there is no behavior change for anyone running self-hosted session runners.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}