[performance] Regression in CompileMCPWorkflow: +10.1% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: CompileMCPWorkflow

Current Performance: 365,587 ns/op (≈ 365.6 μs)
Historical Average: 332,027 ns/op (≈ 332.0 μs)
Change: +10.1% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 365,587 (was 332,027)
• Change: +10.1%
• Historical Data Points: 3
• Memory: 128,192 B/op
• Allocations: 2,265 allocs/op

Baseline Targets

• Simple workflows: <100ms ✅
• Complex workflows: <500ms ✅
• MCP-heavy workflows: <1s ✅ (but trending up)

💡 Recommended Actions

1. Review recent changes to the compilation pipeline for MCP workflows
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots
4. Compare with previous benchmark results: benchstat

📋 Additional Context

• Run ID: 28804975960
• Date: 2026-07-06
• Workflow: Daily CLI Performance

---

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 39.1 AIC · ⌖ 17.9 AIC · ⊞ 11.5K · ◷

• expires on Jul 8, 2026, 8:09 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 1.78 AIC · ⌖ 4.72 AIC · ⊞ 5.4K · ◷