[plan] Fix schema consistency issues found in analysis

[github-actions]

Overview

This tracking issue addresses schema consistency problems identified in the Schema Consistency Check analysis.

Source: Discussion #8801

Key Issues

The analysis found 5 inconsistencies across the three JSON schemas:

1. Critical: MCP version type inconsistency - runtime accepts numbers but mcp_config_schema.json only allows strings
2. Moderate: Missing validation documentation in included_file_schema.json
3. Moderate: Missing engine default value in included schema
4. Moderate: Undocumented safe-outputs scope restriction
5. Moderate: Undocumented tools scope restriction

Planned Tasks

This work is broken down into focused sub-issues:

1. Fix MCP version type in mcp_config_schema.json (#aw_a1b2c3d4e5f6)
2. Add stdio_mcp_tool documentation to included schema (#aw_b2c3d4e5f6a7)
3. Standardize engine default value across schemas (#aw_c3d4e5f6a7b8)
4. Document safe-outputs scope restrictions (#aw_d4e5f6a7b8c9)
5. Document tools scope restrictions (#aw_e5f6a7b8c9d0)

Success Criteria

• All three schemas have consistent type definitions where appropriate
• Documentation matches implementation behavior
• Intentional differences are documented in reference docs
• Schema changes validated with existing workflows

AI generated by Plan Command for discussion #8801