tool-rename-deprecation

To maintain backward compatibility when renaming tool references, add the old names to legacy arrays like legacyToolReferenceFullNames and legacyFullNames so existing prompts and configurations continue functioning.

Prompt files break after tool renaming if old references are not added to legacy arrays, which this process validates by checking prompt files, tool configurations, and auto-approval settings to ensure deprecated names are honored.

To deprecate a tool name without breaking configurations, map the old name as a legacy alias to the new name, ensuring that auto-approval settings and tool registrations preserve access to the deprecated references.

Yes, you can verify tool set renaming preserves legacy references by validating that old names are added to the legacyFullNames array and checking that all prompt files and tool configurations honor these deprecated names.

If legacy references are dropped during tool renaming, existing prompts and saved configurations will fail, making regression prevention critical to ensure old names are mapped correctly to the new tool names.

You need to run backward compatibility validation for deprecated tools whenever a built-in tool or tool set reference name is changed, ensuring all prompt files, configurations, and auto-approval settings honor the old names.