[Code Quality] Increase test coverage for compiler orchestrator modules

[github-actions]

Description

The compiler orchestrator modules have excellent architecture (5 focused modules with clear separation of concerns) but low test coverage at 22% (274 test lines / 1,225 source lines). This is below the project's typical 50%+ standard and leaves critical compilation logic undertested.

Current coverage:

• compiler_orchestrator_*.go files: 274 test lines / 1,225 source lines = 22%
• Target: 60%+ coverage (project standard)

Gap:

• Missing integration tests for ParseWorkflowFile() orchestration flow
• Error handling at each orchestration phase undertested
• Edge cases in engine detection and tool processing not covered

Suggested Changes

Add comprehensive test coverage focusing on:

1. Integration tests for orchestration flow:

   • End-to-end ParseWorkflowFile() with valid inputs
   • Error propagation through orchestration layers
   • Phase coordination and result passing

2. Unit tests for each module:

   • compiler_orchestrator_engine.go: Engine detection, setup, imports
   • compiler_orchestrator_frontmatter.go: Frontmatter parsing, validation
   • compiler_orchestrator_tools.go: Tool config, MCP setup
   • compiler_orchestrator_workflow.go: Workflow data assembly

3. Edge case coverage:

   • Invalid frontmatter formats
   • Missing engine configurations
   • Tool processing failures

Files Affected

Source files (1,225 lines):

• pkg/workflow/compiler_orchestrator.go (8 lines)
• pkg/workflow/compiler_orchestrator_engine.go (239 lines)
• pkg/workflow/compiler_orchestrator_frontmatter.go (167 lines)
• pkg/workflow/compiler_orchestrator_tools.go (274 lines)
• pkg/workflow/compiler_orchestrator_workflow.go (537 lines)

Test files (need expansion):

• pkg/workflow/compiler_orchestrator_test.go (or create module-specific test files)

Success Criteria

• Test coverage reaches 60%+ (target: ~735 test lines)
• All orchestration phases have integration tests
• Error handling paths are tested
• Typed result structures validated
• All existing tests pass

Source

Extracted from Daily Compiler Code Quality Report discussion #13034

Finding excerpt:

"Current coverage: 0.22 (274 test lines / 1,225 source lines)... Only 22% test coverage is below the project's typical standards... Recommendation: Add integration tests for orchestration flow"

Quality score: 89/100 (Excellent architecture, needs better test coverage)

Priority

High - Critical compilation logic needs robust test coverage for stability. Aligns with release mode focus on quality.

AI generated by Discussion Task Miner - Code Quality Improvement Agent

• expires on Feb 9, 2026, 9:06 AM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster