[performance] Regression in ParseWorkflow: +12.0% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkParseWorkflow
Current Performance: 3,472,142 ns/op (≈3.5ms)
Historical Average: 3,101,092 ns/op (≈3.1ms)
Change: +12.0% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	3,472,142	3,101,092	+12.0%
B/op	819,637	—	—
allocs/op	15,557	—	—

Historical Data Points: 7

Recent values (ns/op):

• 2026-03-16: 6,829,453 ← outlier (early weeks had higher parse times)
• 2026-03-17: 2,098,370
• 2026-03-18: 2,515,996
• 2026-03-19: 2,978,489
• 2026-03-20: 2,306,997
• 2026-03-21: 2,791,402
• 2026-03-22: 2,186,942
• 2026-03-23: 3,472,142 ← today

Note: The 7-entry rolling average is slightly skewed by the 2026-03-16 outlier. The recent baseline (Mar 17–22) averages ~2.5ms; current is ~3.5ms, which is a +40% increase over that recent trend.

💡 Recommended Actions

1. Review changes to the frontmatter parser in pkg/parser since 2026-03-22
2. Run selective benchmark: go test -bench=BenchmarkParseWorkflow -benchmem ./pkg/workflow/
3. Check if the regression is consistent or an artifact of machine load
4. Compare parse logic with previous commits using git log --oneline pkg/parser/

📋 Additional Context

• Run ID: §23443107623
• Date: 2026-03-23
• Benchmark: BenchmarkParseWorkflow in pkg/workflow
• Regression threshold: 10% (current: +12.0%)

References:

• §23443107623

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 25, 2026, 2:48 PM 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 coding agent.

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 · ◷