Add $comment validation documentation to stdio_mcp_tool in included schema

[Copilot]

The stdio_mcp_tool definition in included_file_schema.json was missing validation constraint documentation present in main_workflow_schema.json, creating inconsistent developer experience across schema files.

Changes

Added $comment fields to stdio_mcp_tool definition in pkg/parser/schemas/included_file_schema.json:

• command property: Documents mutual exclusion with container
• container property: Documents mutual exclusion with command
• network property: Documents dependency on container (network only applies to container-based servers)
• stdio_mcp_tool root: Comprehensive validation constraints explaining:
  1. Mutual exclusion between command and container
  2. Requirement for either command or container
  3. Network dependency on container
  4. Type constraints for stdio/local modes

Example

The added documentation clarifies validation behavior:

mcp-servers:
  example:
    type: stdio
    command: node server.js    # ✓ Valid
    # container: node:20       # ✗ Cannot specify both command and container
    
  container-based:
    type: stdio
    container: myorg/mcp-server
    network:                   # ✓ Network requires container
      allowed: [api.example.com]

Schema size increased by 824 bytes. Binary rebuild required due to //go:embed schema embedding.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[plan] Add validation documentation to stdio_mcp_tool in included schema</issue_title>
<issue_description>## Objective

Add the missing $comment field to stdio_mcp_tool definition in included_file_schema.json to match the documentation in main_workflow_schema.json.

Context

The main schema includes 780 bytes of validation constraint documentation in the stdio_mcp_tool.$comment field that explains:

• Mutual exclusion between command and container
• Requirement for either command or container
• Dependency of network on container
• Type constraints for stdio/local modes

This documentation is missing from the included schema, creating inconsistent developer experience.

Approach

1. Open pkg/parser/schemas/main_workflow_schema.json
2. Copy the $comment field from $defs.stdio_mcp_tool
3. Open pkg/parser/schemas/included_file_schema.json
4. Add the same $comment field to $defs.stdio_mcp_tool
5. Verify JSON formatting is valid

Files to Modify

• pkg/parser/schemas/included_file_schema.json - Add $comment to stdio_mcp_tool

Acceptance Criteria

• $comment field exists in included_file_schema.json stdio_mcp_tool definition
• Comment text matches main_workflow_schema.json exactly
• JSON schema remains valid
• Schema file size difference between main and included is reduced
  Related to [plan] Fix schema consistency issues found in analysis #8804

AI generated by Plan Command for discussion #8801

Comments on the Issue (you are @copilot in this section)

• Fixes [plan] Add validation documentation to stdio_mcp_tool in included schema #8806

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.