tool-rename-deprecation

To maintain backward compatibility when renaming tools in TypeScript, add the old tool identifier to the `legacyToolReferenceFullNames` array. This ensures existing prompts and configurations referencing the old name continue to resolve correctly.

If you change a tool reference name without keeping legacy names, prompt file resolution, tool enablement, and auto-approval configurations will break. Existing setups referencing the old identifier will fail to locate the renamed tool.

Yes, when renaming a tool set you need to update package.json contributions. You must add the old reference name to the `legacyFullNames` array to preserve backward compatibility for external configurations and registrations.

The best way to catch dropped legacy tool names during code maintenance is to run a deprecation check. This identifies missing old names in legacy arrays during direct modifications or code reviews, preventing regressions.

You need to use legacy arrays for tool renames whenever a `toolReferenceName` or tool set `referenceName` is modified. This preserves the old identifiers so backward compatibility is maintained across internal and external registrations.