{"version":"2.1.224","anchor":"schemas-across-the-binary-rewritten-onto-internal-builders","canonical_anchor":"schemas-across-the-binary-rewritten-onto-internal-builders","heading":"Schemas across the binary rewritten onto internal builders","tier":"internal","area":"Build","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/schemas-across-the-binary-rewritten-onto-internal-builders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Schemas across the binary rewritten onto internal builders\n\nNearly every schema was rewritten onto smaller internal builders with no change in behaviour.\n\n**What**\n\nNearly every declared schema in the build, covering tools, hooks, settings, MCP config and message envelopes, plugin manifests, browser listings, LSP operations and sandbox settings, was rewritten from the zod-style `object`\/`string`\/`enum`\/`array`\/`union`\/`discriminatedUnion`\/`preprocess`\/`strictObject` calls onto compact internal equivalents. Field names, description text and validation messages are unchanged, so validated shapes and error output stay the same.\n\n**Details**\n\n- Some explicit unions became a helper call, and strict objects moved to a strict-object helper.\n- The MCP v1\/v2 module tripwire is untouched by the rewrite.\n\n**Evidence**\n\n`protocol must be an RFC 6455 token`, `url contains control characters that would be hidden in the approval dialog`\n\n- Area: Build\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}