docs: add note about ElicitationCapability being kept local

ElicitationCapabilitySchema is kept as a local definition in types.ts
because it has z.preprocess for backwards compatibility (handling empty
objects as { form: {} }).

ClientCapabilitiesSchema and ServerCapabilitiesSchema are also kept local
because they use AssertObjectSchema for better type safety.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: ochafik

scripts/generate-schemas.ts

@@ -118,6 +118,7 @@ const DISCRIMINATED_UNIONS: Record<string, string> = {
 const DERIVED_CAPABILITY_TYPES: Record<string, { parent: string; property: string }> = {
     'ClientTasksCapability': { parent: 'ClientCapabilities', property: 'tasks' },
     'ServerTasksCapability': { parent: 'ServerCapabilities', property: 'tasks' },
+    // Note: ElicitationCapability is kept local in types.ts because it has z.preprocess for backwards compat
 };
 
 // =============================================================================

src/types.ts

@@ -540,7 +540,7 @@ export const ClientCapabilitiesSchema = z.object({
 
 /**
  * Elicitation capability schema - extracted from ClientCapabilitiesSchema.
- * Includes preprocessing to handle empty objects as { form: {} }.
+ * Has special preprocessing to handle empty objects as { form: {} } for backwards compatibility.
  */
 export const ElicitationCapabilitySchema = ClientCapabilitiesSchema.shape.elicitation.unwrap();