Add Thermos tool slug resolver
@shreysingla11checks…fix/thermos-tool-slug-resolution → master7 files · +553 −10updated 5d agoloading diff…
@shreysingla11checks…fix/thermos-tool-slug-resolution → master7 files · +553 −10updated 5d ago@shreysingla11checks…fix/thermos-tool-slug-resolution → master7 files · +553 −10updated 5d agoAdds a facts-only Thermos endpoint for resolving requested tool slugs without returning full tool schemas.
Endpoint: POST /api/tools_/resolve
The response classifies each requested slug as:
current_canonicalcurrent_aliashistoricalunknownEach item can optionally include toolkit_slug. When present, resolution is scoped to that toolkit relationship. When omitted, resolution is slug-only for ToolRouter surfaces such as explicit preload.tools where the request does not carry a toolkit key.
ToolRouter needs to distinguish three cases without fetching full schemas:
The existing list/enums APIs are intentionally discovery-oriented and canonical by default; they do not return enough facts for this behavior without extra calls or schema payloads.
unknown as a normal 200 response item; unknown slugs do not make the endpoint 404.x-group group fallback behavior.Ran:
cd apps/thermos && go test ./handlers/tools ./ent/registrydb/utils