[performance] Regression in ParseWorkflow: +191.6% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkParseWorkflow

Current Performance: 1,053,266 ns/op (1.05ms)
Historical Average: 361,162 ns/op (361.16μs)
Change: +191.6% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Average	Change
ns/op	1,053,266	361,162	+191.6%
B/op	160,225	139,509	+14.8%
allocs/op	2,834	2,072	+36.8%

Historical Data Points Used: 2

💡 Recommended Actions

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

📋 Additional Context

• Run ID: §24923879653
• Date: 2026-04-25
• Related: See also BenchmarkValidation (+275.9%) and BenchmarkCompileSimpleWorkflow (+177.5%) regressions in the same run.

⚠️ Note: Benchmarks ran with only 3 iterations each. High variance is possible; monitor over subsequent runs to confirm the regression.

References:

• Workflow Run §24923879653

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

• expires on Apr 27, 2026, 5:50 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 · ● 17.9K · ◷