Under the hood
Useful1 Signal0
Two changes in hook spawning and MCP state are renames only, with identical behaviour.
What's wrong with this entry?
Anonymous. No account, no email.
What
In 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.
Evidence
replaceOnly: te,
Strings lifted out of the shipped bundle, so the claim above can be checked against them.