What problem does it solve? Polish or German search queries fail to retrieve the correct English documentation in a RAG system even when the equivalent English query works, because the multilingual query-expansion glossary lacks entries for those foreign-language terms. ## Core Features & Use Cases - Diagnose language gaps: Distinguish a true language gap from indexing, scoring, or weighting problems by testing the English query first. - Dual-file glossary updates: Add new entries with English anchor terms and PL/DE patterns to both the Python (tools/rag/multilingual-glossary.yaml) and .NET (tools/rag-dotnet/multilingual-glossary.yaml) glossary copies. - Query-time validation: Test expansion via a Python REPL smoke test, a live MCP query_docs call, and the full eval benchmark — no re-indexing required. - Use Case: A German query like "Entitäts-Bezeichner TypedId Domänenmuster" returns wrong documents; add a glossary entry mapping bezeichner/kennung/entitäts to the English anchor "TypedId entity identifier typed domain primitive" and confirm the target doc ranks #1. ## Quick Start Ask the assistant to add a glossary entry so that the failing Polish or German query retrieves the correct English document, providing the failing query and the target document.