tool-rename-deprecation

To keep prompts working after renaming a tool, you must add the old tool references to legacy mapping arrays. This preserves backward compatibility by ensuring old names remain resolvable across tool enablement and auto-approval logic.

Renaming a toolset breaks prompt resolution and activation because existing configurations and events still reference the old names. Without maintaining legacy name mappings, the system cannot resolve the previous identifiers.

Yes, you need to update legacy tool references for extension-provided tools. Maintaining legacy name mappings applies to both internal TypeScript tools and extension tools to ensure consistent lookups across all configurations.

The best way to maintain backward compatibility is enforcing the use of legacyToolReferenceFullNames and legacyFullNames arrays. This updates prompt resolution, tool enablement, and auto-approval logic across all consumers automatically.

To add old tool names during registration changes, identify the renamed tool or tool set and insert the previous name into the appropriate legacy array. This maintains compatibility so all old references keep functioning correctly.

Without using legacy full name arrays when renaming tools, old references in prompts and configurations become unresolvable. This breaks tool enablement, auto-approval logic, and activation events across all system consumers.