Motivation
Renaming a configured agent, tool, model, or other component currently breaks every consumer immediately. Applications need a controlled migration path where an old component name can resolve to the new registration without duplicating component objects.
Proposal
Extend ComponentManagerBase with explicit alias registration and removal. Aliases should resolve through the normal copy/strict/default behavior, reject collisions and missing targets, and be visible through an introspection API.
Acceptance criteria
- bare component names can be registered as aliases for existing components
- aliases return the same kind of defensive copy as canonical lookups
- collisions, missing targets, and alias cycles are rejected
- removing an alias never removes the target component
- registered aliases can be inspected
- unit tests and English/Chinese documentation are included
Motivation
Renaming a configured agent, tool, model, or other component currently breaks every consumer immediately. Applications need a controlled migration path where an old component name can resolve to the new registration without duplicating component objects.
Proposal
Extend
ComponentManagerBasewith explicit alias registration and removal. Aliases should resolve through the normal copy/strict/default behavior, reject collisions and missing targets, and be visible through an introspection API.Acceptance criteria