Version: v0.5.0.
The CLI guide (§2) groups results "by layer priority before BM25 score". In a mature repository, a strong user-scope match never surfaces:
- query "commit changes" at limit 3;
- project hits score 2.43, 1.73 and 1.73;
- the user-scope match scores 15.94. It is dropped at limit 3, and ranked last at limit 10.
Request: an opt-in flag or MCP parameter (for example --rank relevance) that merges layers by score while keeping shadowing by id.
Related: #11 (the multi-bundle search design).
Version: v0.5.0.
The CLI guide (§2) groups results "by layer priority before BM25 score". In a mature repository, a strong user-scope match never surfaces:
Request: an opt-in flag or MCP parameter (for example
--rank relevance) that merges layers by score while keeping shadowing by id.Related: #11 (the multi-bundle search design).