[codex] harden progressive tool discovery

[ignaciojimenezr]

Summary:

• Backend: preserve server names through progressive discovery catalogs, meta-tool search/load responses, chat-v2 orchestration, HTTP tool flattening, harness traces, and hosted stream finish metadata.
• Eval tracing: persist serverName on tool spans and label discovery meta-tool rows clearly as MCPJam discovery activity.
• Frontend: add the header Auto/On/Off progressive-tools override and surface active discovery status from assistant message metadata.

Verification:

• npm run test --workspace @mcpjam/inspector -- shared/tests/progressive-tool-discovery.test.ts server/utils/tests/progressive-tool-meta-tools.test.ts client/src/components/shared/tests/ClientContextHeader.test.tsx client/src/components/evals/tests/trace-timeline.test.tsx
• npm run typecheck:client --workspace @mcpjam/inspector
• npm run sdk:build --workspace @mcpjam/inspector
• npm run build:server --workspace @mcpjam/inspector
• git diff --check

[chelojimenez]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

Internal preview

Preview URL: https://mcp-inspector-pr-3036.up.railway.app
Deployed commit: 1a61617
PR head commit: dd009d1
Backend target: staging fallback.
Health: ✅ Convex reachable
Access is employee-only in non-production environments.