Two parallel toolkit implementations with no migration plan
pkg/tool.Toolkit (used by manager.Manager) vs pkg/toolkit.Toolkit (active development)
manager.runTools() still calls the old pkg/tool path; new namespace/resource/prompt features are siloed
Needs an explicit deprecation and migration plan; manager should route through pkg/toolkit once it stabilizes
We also want to deprecate pkg/agent (and add versioning to pkg/toolkit/prompt) which will mean a re-write.
Two parallel toolkit implementations with no migration plan
pkg/tool.Toolkit (used by manager.Manager) vs pkg/toolkit.Toolkit (active development)
manager.runTools() still calls the old pkg/tool path; new namespace/resource/prompt features are siloed
Needs an explicit deprecation and migration plan; manager should route through pkg/toolkit once it stabilizes
We also want to deprecate pkg/agent (and add versioning to pkg/toolkit/prompt) which will mean a re-write.