Performance: Address N+1 query patterns in router stream handlers

[jmanhype]

Context

PR #282 successfully modularized the router, but gemini-code-assist identified N+1 query patterns in stream handlers that could impact performance.

Issue

Stream handlers may be making repeated database queries when batch queries would be more efficient. Additionally, .genie profile loading is duplicated across multiple handlers.

Recommendations

1. Profile queries first - Measure actual performance impact before optimizing
2. Consolidate .genie profile loading - Create shared utility to avoid duplication
3. Review stream handlers - Identify opportunities for batch queries

Gemini Code Assist Quote

"I've identified a few instances of N+1 query patterns, particularly in stream handlers, which could impact performance. I've also noted some duplicated code for loading .genie profiles that could be centralized."

Related

• PR refactor: modularize router.rs into domain-specific route modules #282 - Router modularization (successfully implemented)
• forge-app/src/router.rs and related router modules
• Gemini code review feedback

Priority

Medium (Performance optimization - requires profiling to quantify impact)

Investigation Needed

• Profile database queries in stream handlers
• Measure actual performance impact
• Identify specific N+1 patterns
• Design batch query solution if warranted