[performance] Regression in ParseWorkflow: 63.7% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkParseWorkflow

Current Performance: 1,387,952 ns/op (1.39ms)
Historical Average: 847,890 ns/op (847.89μs)
Change: +63.7% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 1,387,952 (was 847,890)
• Change: +63.7%
• Memory: 158,625 B/op
• Allocations: 2,870 allocs/op
• Historical Data Points: 9

Baseline Targets

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

💡 Recommended Actions

1. Review recent changes to the workflow parsing phase (pkg/workflow/parser or pkg/parser)
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in the parse step
4. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: §24622185734
• Date: 2026-04-19
• Workflow: Daily CLI Performance

Generated by Daily CLI Performance Agent · ● 1.1M · ◷

• expires on Apr 21, 2026, 5:55 AM UTC

[github-actions]

🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

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! 🍪> [!CAUTION]

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 16.6K · ◷