{"version":"2.1.237","anchor":"two-apparent-edits-are-renaming-only","canonical_anchor":"two-apparent-edits-are-renaming-only","heading":"Two apparent edits are renaming only","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237\/e\/two-apparent-edits-are-renaming-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237","markdown":"### Two apparent edits are renaming only\n\nTwo changes in hook spawning and MCP state are renames only, with identical behaviour.\n\n**What**\n\nIn the code that spawns hook commands, including the Windows branch that errors when neither `pwsh` nor `powershell` is on PATH, only local variable and module alias names changed; the spawn options are identical. In the MCP client state update, a line that looks dropped is a rename artifact, and all four empty-list fallbacks for disabled or failed servers (tools, commands, resources, resource templates) are still computed.\n\n**Evidence**\n\n`replaceOnly: te,`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}