Saim Shafique 6b55de017b fix(mcp): bound capture comparison input schema depth (#1005) ... * fix(mcp): advertise JSON values without recursive schemas `z.json()` projects a self-referential `$defs/__schema0` entry. Twenty tool input schemas and 123 output schemas carried it, and clients or model APIs that reject recursive JSON Schemas refuse the whole tool list. Every JSON value satisfies `{}`, so the shared JSON value schema now advertises that. Runtime parsing still admits only JSON values. Refs #919 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(mcp): keep advertised input schemas within model function-calling limits Some model providers reject the whole tool list when any input schema contains a recursive $ref or nests deeper than 10 levels (fixes #919). Sanitize the advertised wire projection: break cyclic $refs, bound nesting depth, and drop unreachable $defs. Canonical Zod contracts are untouched. --------- Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: sx4im <sx4im@users.noreply.github.com> Co-authored-by: N0zoM1z0 <1705004398@qq.com>		2026-10-08 12:26:00 +08:00
..
managed-conformance-ledger.json	refactor!: simplify runtime tools and remove replay engines (#572)	2026-10-05 21:15:04 +08:00
managed-conformance-manifest.json	fix(mcp): bound capture comparison input schema depth (#1005)	2026-10-08 12:26:00 +08:00