[WIP] Fix performance regression in BenchmarkFindIncludesInContent

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[performance] Regression in BenchmarkFindIncludesInContent: +51.4% slower</issue_title>
<issue_description>### 📊 Performance Regression Detected

Benchmark: BenchmarkFindIncludesInContent

Current Performance: 42,474 ns/op (42.47μs)
Historical Average: 28,049 ns/op (28.05μs)
Change: +51.4% slower
Historical Data Points: 7

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	42,474	28,049	+51.4%
B/op	14,557	—	—
allocs/op	52	—	—

Baseline Targets

• CLI helper functions should remain in the microsecond range
• Simple workflows: <100ms total

💡 Recommended Actions

1. Review recent changes to FindIncludesInContent in pkg/cli/ or pkg/workflow/
2. Check if include/import scanning logic was updated (regex changes, additional file traversal)
3. Run make bench-memory to profile memory allocations
4. Use go tool pprof to identify where the slowdown occurs
5. Consider if new include patterns were added that increase scanning complexity

📋 Additional Context

• Run ID: §24598094273
• Date: 2026-04-18
• Workflow: Daily CLI Performance
• Regression threshold: 10% slowdown triggers an issue

---

Automatically generated by Daily CLI Performance workflow

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

• expires on Apr 20, 2026, 5:48 AM UTC

Comments on the Issue (you are @copilot in this section)