Documents previously-undocumented surface area surfaced by onboarding feedback
and the bench discoverability report:
- README: collection filtering (-c semantics), collection show/include/exclude/
update-cmd, --intent/--no-rerank/-C/--full-path, --format <kind> (legacy
output booleans noted as aliases), vector-search/deep-search aliases, embed
memory flags, a sample --explain trace, MCP tool parameter reference, qmd
doctor/init, get :from:count + --no-line-numbers, and a Benchmarking section
for qmd bench.
- README: removed the misleading `qmd update --pull` example; --pull is parsed
but never consumed, so it points to `qmd collection update-cmd` (the real
per-collection pre-reindex mechanism) instead.
- docs/SYNTAX.md: drop the non-existent `q` MCP parameter (the query tool/REST
endpoint accept only `searches`); add a Scoping section.
- server.ts: buildInstructions now advertises the plural `collections` parameter
to match the schema (singular was silently stripped, yielding unscoped
results), and the `get` instruction documents the full file.md:from:count
range suffix instead of only file.md:100.
Refs #25, #181, #217, #372, #520, #576
Add optional `intent` parameter that steers query expansion, reranking,
chunk selection, and snippet extraction without searching on its own.
When a query like "performance" is ambiguous (web-perf vs team health vs
fitness), intent provides background context that disambiguates results
across all pipeline stages:
- expandQuery: includes intent in LLM prompt ("Query intent: {intent}")
- rerank: prepends intent to rerank query for Qwen3-Reranker
- chunk selection: intent terms scored at 0.5x weight vs query terms
- snippet extraction: intent terms scored at 0.3x weight
- strong-signal bypass: disabled when intent provided
Available via CLI (--intent flag or intent: line in query documents),
MCP (intent field on query tool), and programmatic API.
Adapted from PR #180 (thanks @vyalamar).
