[diegosouzapw]

Problem and change

A routed model such as aihorde/deepseek/deepseek-v4-flash inherited DeepSeek tool support and context limits after static-spec lookup recursively removed its upstream namespace. This made AI Horde appear eligible for tool requests despite its provider restriction.

Already-scoped capability lookups now preserve the remaining namespace. Public spec lookups retain their provider-prefix behavior by default, and the existing vision-only leaf fallback remains intact. The indexed lookup is reused; no new cache or scan is introduced.

Validation

• Existing provider-tools and path-shaped vision regressions failed on release 858d6022270b73489dfa8d89eee6fcc9a6a9e214 before the fix.
• Focused capability/lookup suites: 17 passed; public-lookup compatibility suite after adding two cases: 5 passed.
• Adjacent registry, provider-prefix overrides, Mistral vision, command-code/Codex text-only and Claude effort suites: 53 passed.
• Core TypeScript, changed-file ESLint/Prettier, file-size, changelog and commit hooks passed. No baseline changes.
• Local tests used Node24.20.0, reused dependencies and isolated DATA_DIR. Full remote CI/Quality admission remains required.

The wider release diagnostic still has unrelated failures; this PR only fixes static capability namespace leakage.

[github-actions]

CI Coverage Report

• Coverage job: skipped
• PR test policy: success

Coverage artifact was not available for this run.