Fix MCP OutputSchema Strict JSON-RPC Compliance and Zod Array Type Mapping

Architectural Problem

The MCP Client strict validation layer experienced Zod schema mismatches due to parsing bugs in the OS's internal OpenApiValidator which maps OpenAPI payload definitions to runtime .describe() Zod bindings.

Specifically:

1. Input Schema Arrays: Any array payload properties defined inside the OpenAPI specification were being hardcoded internally into string arrays (z.array(z.string())), fracturing endpoint bindings.
2. Output Schema Object Rule: The JSON-RPC Model Context Protocol specification demands that outputSchema instances parse strictly as type: "object". Certain endpoints (like get_computed_styles in neural-link) resolved correctly inside the target application, but returned root-level Array mappings via .send(), rendering them non-compliant and failing strict Client connection handshakes.

Solution

1. Recursive Node Generation: Pruned the hardcoded array switch() cases within buildZodSchema and transitioned map traversal down to buildZodSchemaFromNode directly, fully inheriting native types (numbers, integers, booleans, etc.) inherently resolving Input schema bounds.
2. Result Wrapper for Primitives & Arrays: The OpenApiValidator mapping was dynamically updated to force any OpenAPI definition whose resolved schema ($ref) does not structurally equate to an object to automatically wrap its structure within { result: value }.
3. Structured Content Sync: All 5 OS MCP servers (neural-link, memory-core, knowledge-base, file-system, github-workflow) explicitly adjusted their CallToolRequestSchema response returns to encapsulate primitives and arrays natively into mapping payloads so MCP-Client Zod failures bypass organically.