[SaladDay]

Claude environment:none Sessions now support HTTP MCP required:true. All Claude HTTP MCP requests use one native SDK startup path; required-server readiness is checked before releasing the first input. Native identity, inventory, hooks, credential handling and the existing execution lifecycle remain in force. There is no fallback to a previous execution path.

Validation on zju_a100_2:

• make check, focused/race suites, SDK tests and API generation passed.
• Fixed official SDK 3.13.0/raw HTTP with real Kimi K3 passed required MCP plus public functions, cold history continuation and optional MCP regression.
• Failed/delayed initialization and cancellation before readiness made zero model Messages requests; provider request timestamps confirm initialization precedes successful model execution.
• Native readiness probes and production-entrypoint tests cover held input, cancellation, missing/ambiguous readiness and history identity. No provider key was found in retained public-test artifacts.

This is the existing none HTTP MCP profile only. Hosted MCP, additional native naming/schema support, images and self-hosted integration remain outside the batch. Native startup deadlines are retained; pending initialization is rejected without an adapter retry loop. Evidence: ~/.parsar/remediation/20260919/claude-required-mcp/.