Pinned MCP tool schemas have drifted from upstream nexus-agents (repo no longer catches drift)

[williamzujkowski]

Problem

This repo's stated purpose (README + src/schemas.ts header) is to pin nexus-agents code-intelligence tool input schemas so any upstream drift fails the test suite. The schemas have already drifted, and the tests pass green anyway because they only validate the local (stale) copies.

Observed drift against the live tools:

• RepoAnalyzeInputSchema (src/schemas.ts) models { url, depth: enum['shallow','full'] }. The live repo_analyze tool takes { repo, depth: enum['shallow','deep'] } — wrong field name (url vs repo) and wrong depth enum value (full vs deep).
• RepoSecurityPlanInputSchema models { url, includeSecrets }. The live repo_security_plan tool takes { repo, categories[], maxScanners }.

Suggested fix

1. Re-sync all four schemas in src/schemas.ts to the current upstream tool definitions.
2. Re-verify extract_symbols and search_codebase schemas while doing so.
3. Replace (or supplement) the hand-maintained mirror with a test that fetches/compares against the real tool inputSchema (e.g. via the MCP tool listing) so future drift fails automatically instead of silently passing.