[performance] Regression in ExtractWorkflowNameFromFile: 26.5% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: ExtractWorkflowNameFromFile

Current Performance: 9,255 ns/op
Historical Average: 7,314 ns/op
Change: +26.5% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 9,255 (was 7,314)
• Change: +26.5%
• Memory: 262 B/op
• Allocations: 7 allocs/op
• Historical Data Points: 1 (2026-07-07 baseline)

Benchmark Context

This benchmark measures the time to extract a workflow name from a file path — a CLI helper used frequently during workflow discovery and compilation.

Baseline Targets

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

💡 Recommended Actions

1. Review recent changes to workflow name extraction in the CLI helpers
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: §29030948461
• Date: 2026-07-09
• Workflow: Daily CLI Performance
• Note: Comparison is based on 1 data point (2026-07-07). More data points will improve accuracy.

Other Notable Changes (2026-07-09)

• ✨ Validation: -34.9% faster
• ✨ YAMLGeneration: -17.8% faster
• ⚡ CompileSimpleWorkflow: +5.7% (warning)
• ⚡ CompileMemoryUsage: +6.5% (warning)

---

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 67.8 AIC · ⌖ 37.3 AIC · ⊞ 11.4K · ◷

• expires on Jul 11, 2026, 8:03 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.36 AIC · ⌖ 6.03 AIC · ⊞ 8.4K · ◷