[plan] Fix cross-schema consistency issues in workflow schemas

[github-actions]

Overview

This tracking issue addresses the 8 cross-schema consistency issues discovered in the analysis of main_workflow_schema.json, included_file_schema.json, and mcp_config_schema.json.

Source: Discussion #7935

The analysis revealed significant inter-schema maintenance burden and feature parity gaps that need to be addressed to improve schema consistency and reduce ongoing maintenance overhead.

Background

The schema analysis identified:

• 5 critical issues requiring immediate action
• 3 moderate issues for schema quality improvement
• 3 new issues not previously documented
• 2 confirmed previous issues

Planned Tasks

This work will be completed through the following sub-issues:

1. Fix engine field duplication - Eliminate $ref vs inline duplication risk
2. Add missing permissions shortcuts - Restore UX consistency for included files
3. Add network firewall configuration - Restore security feature parity
4. Document tool restrictions - Clarify intentional design limitations
5. Standardize enum vs const usage - Improve schema quality consistency

Success Criteria

• All engine field changes use $ref (no inline duplication)
• Permissions shortcuts work in both main and included schemas
• Network firewall configuration available in included files
• Tool restrictions are documented in schema descriptions
• Schema style is consistent (enum vs const)

Files Affected

• pkg/parser/schemas/main_workflow_schema.json
• pkg/parser/schemas/included_file_schema.json
• pkg/parser/schemas/mcp_config_schema.json

Priority

HIGH - These issues create maintenance burden and feature parity gaps that affect workflow authors.

---

AI generated by Planning Assistant for #7935

AI generated by Plan Command for discussion #7935