jedarden d70657171f fix(multi-search): use configured over_fetch_factor instead of hardcoded 1 ... The multi-search route was hardcoding over_fetch_factor to 1 instead of using the configured vector_search.over_fetch_factor value. This meant vector searches in multi-query batches didn't benefit from over-fetching, leading to incorrect global ranking on sparse semantic matches. Changes: - Added HeaderMap parameter to multi_search handler - Extract X-Miroir-Over-Fetch header for per-request override (plan §13.12) - Pass over_fetch_factor into the executor closure - Use over_fetch_factor when building SearchRequest Closes: bf-5204 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-26 08:11:17 -04:00
..
miroir-core	feat(reshard): implement backfill phase with pagination and rehashing	2026-05-26 08:05:45 -04:00
miroir-ctl	style: code formatting cleanup	2026-05-26 03:44:20 -04:00
miroir-proxy	fix(multi-search): use configured over_fetch_factor instead of hardcoded 1	2026-05-26 08:11:17 -04:00