[Code Quality] Remove included_file_schema references from documentation #12419
Description
The included_file_schema.json file was removed from the codebase as part of a schema consolidation, but documentation still references it in multiple places, causing developer confusion about the current schema architecture.
Source
Extracted from Schema Consistency Analysis discussion #11121
Problem
Schema Architecture Changed:
- Previous: 3 schemas (main_workflow_schema.json, included_file_schema.json, mcp_config_schema.json)
- Current: 2 schemas (main_workflow_schema.json for both main and included workflows, mcp_config_schema.json)
Status:
- ✅ Code: All parser and compiler code successfully updated (no references remain)
- ❌ Documentation: Still references old 3-schema architecture
Files Requiring Updates
specs/schema-validation.md:15, 91- Removeincluded_file_schemareferencesskills/developer/SKILL.md:1094- Update schema files table to show 2 schemas.github/workflows/schema-consistency-checker.md:85- Remove from key files list.github/workflows/schema-consistency-checker.lock.yml:690- Update workflow instructions
Current Architecture (Correct)
pkg/parser/schemas/
├── main_workflow_schema.json # Used for BOTH main AND included workflows
└── mcp_config_schema.json # Used for MCP tool configurations
Success Criteria
- All 4 files updated to reflect current 2-schema architecture
- No remaining references to
included_file_schema.json - Documentation accurately describes current schema structure
- Schema architecture section in developer docs is correct
Priority
High - Documentation mismatch causes developer confusion and wastes time. The code migration was completed cleanly; documentation needs to catch up.
Estimated Effort
2-3 hours - Need to review each file, update references, verify accuracy, and test documentation builds.
AI generated by Discussion Task Miner - Code Quality Improvement Agent
- expires on Feb 12, 2026, 1:34 AM UTC