[performance] Regression in ParseWorkflow: +30.9% slower

[github-actions]

Benchmark: ParseWorkflow

Current Performance: 362,672 ns/op (362.67μs)
Historical Average: 277,041 ns/op (277.04μs)
Change: +30.9% slower

📈 Detailed Performance Metrics

• ns/op: 362,672 (was 277,041)
• B/op: 103,104
• allocs/op: 1,809
• Change: +30.9%
• Historical Data Points: 3

Baseline Targets

• Simple workflows: <100ms
• Complex workflows: <500ms
• MCP-heavy workflows: <1s

Note: ParseWorkflow (362μs) is well within targets, but exceeded the 10% regression threshold vs the 2-day historical average (277μs). This may be CI scheduling variance; monitoring recommended.

💡 Recommended Actions

1. Review recent changes to the workflow parsing phase
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in the parse path
4. Compare with previous results using benchstat

📋 Additional Context

• Run ID: 28248123524
• Date: 2026-06-26
• Workflow: Daily CLI Performance

---

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 53.3 AIC · ⌖ 20 AIC · ⊞ 11.3K · ◷

• expires on Jun 28, 2026, 7:42 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 · 6.26 AIC · ⌖ 9.8 AIC · ⊞ 8.2K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-06-28T15:42:28.316Z.

Closed by Workflow