query (string, required):
 - Method name in Russian (e.g., "СтрРазделить")
 - Description of functionality (e.g., "разделить строку")
 - Platform feature (e.g., "работа с файлами")
 - Can be partial match (e.g., "Стр" finds СтрДлина, СтрРазделить, etc.)

Structure:
 - Top N search results (typically 5-10)
 - Each result contains:
 - Method/function name
 - Full documentation text
 - Parameters description
 - Return value description
 - Usage examples (if available)
 - Relevance score

Format: Plain text with markdown formatting

User: "Как использовать СтрРазделить?"

Action:
 user-1c-help-docsearch(query="СтрРазделить")

Expected result:
 ---
 СтрРазделить(Строка, Разделитель)
 
 Разделяет строку на части по указанному разделителю.
 
 Параметры:
 - Строка (Строка) - исходная строка
 - Разделитель (Строка) - символ-разделитель
 
 Возвращаемое значение:
 - Массив - массив строк
 
 Пример:
 Результат = СтрРазделить("один;два;три", ";");
 // Результат = ["один", "два", "три"]
 ---

User: "Как работать с файлами в 1С?"

Action:
 user-1c-help-docsearch(query="работа с файлами")

Expected result:
 Multiple results about file operations:
 - НайтиФайлы()
 - КопироватьФайл()
 - УдалитьФайлы()
 - ПолучитьИмяВременногоФайла()
 - etc.

User: "Какие есть функции для работы со строками?"

Action:
 user-1c-help-docsearch(query="функции строки")

Expected result:
 - СтрДлина()
 - СтрРазделить()
 - СтрЗаменить()
 - СтрНайти()
 - СтрСравнить()
 - etc.

User: "Как создать HTTP-соединение?"

Action:
 user-1c-help-docsearch(query="HTTP соединение")

Expected result:
 - HTTPСоединение - конструктор
 - HTTPЗапрос - создание запроса
 - HTTPОтвет - обработка ответа
 - Examples of usage

Situation: Query returns no results

Possible reasons:
 - Method is from БСП (not platform) → try search_bsp_functions
 - Typo in method name → try alternative spelling
 - Method is project-specific → try project MCP tools
 - Method doesn't exist → inform user

Action:
 1. Try alternative query (e.g., "Стр" instead of "СтрРазделить")
 2. If still no results, try search_bsp_functions
 3. If still no results, inform user and suggest alternatives

Situation: Query returns 50+ results

Possible reasons:
 - Query too broad (e.g., "функции")
 - Need more specific query

Action:
 1. Ask user to be more specific
 2. Or: Show top 5-10 results with note "Found 50+ results, showing top 10"
 3. Suggest refining query

Situation: User asks in English

Action:
 1. Translate to Russian (1C docs are in Russian)
 2. Search with Russian query
 3. Return results in Russian (with English summary if needed)

Example:
 User: "How to split string?"
 Query: user-1c-help-docsearch(query="разделить строку")
 Result: СтрРазделить() documentation

Situation: Query could mean multiple things

Example: "Получить данные"
 - Could be: HTTP request, database query, file read, etc.

Action:
 1. Return multiple relevant results
 2. Let user choose or refine query
 3. Explain differences between results

search_1c_docs → search_bsp_functions:
 - If platform method not found, try БСП
 - Example: "ОбщегоНазначения.ПолучитьДанные" → search_bsp_functions

search_1c_docs → search_1c_templates:
 - After finding method, get code example
 - Example: Found СтрРазделить() → get template for string processing

search_1c_docs → check_bsl_syntax:
 - After learning syntax, validate code
 - Example: Wrote code using new method → check syntax

Step 1: Learn method
 user-1c-help-docsearch(query="СтрРазделить")

Step 2: Get template
 user-1c-templates-templatesearch(query="разделение строки")

Step 3: Write code
 (AI generates code using learned method)

Step 4: Validate
 user-1c-syntax-checker-syntaxcheck(code="...")

Step 1: Broad search
 user-1c-help-docsearch(query="работа с файлами")

Step 2: User picks specific method
 (User: "Расскажи подробнее про НайтиФайлы")

Step 3: Specific search
 user-1c-help-docsearch(query="НайтиФайлы")

Step 4: Show examples
 user-1c-templates-templatesearch(query="поиск файлов")

Symptoms:
 - Timeout errors
 - Connection refused
 - No results

Diagnosis:
 1. Check server status: curl http://YOUR_SERVER:8003/health
 2. Check Docker container: ssh YOUR_SERVER "pct exec 100 -- docker ps | grep help-mcp"
 3. Check logs: ssh YOUR_SERVER "pct exec 100 -- docker logs help-mcp --tail 50"

Solutions:
 - Server not deployed: Deploy via docker-compose
 - Server crashed: Restart container
 - Network issue: Check Tailscale connection

Symptoms:
 - Search takes >5 seconds
 - Timeout warnings

Possible causes:
 - First query after restart (loading embeddings)
 - Large result set
 - Server overloaded

Solutions:
 - Wait for first query to complete (cache warm-up)
 - Refine query to reduce results
 - Check server resources (memory, CPU)

Symptoms:
 - Results don't match query
 - Irrelevant documentation returned

Possible causes:
 - Query too vague
 - Semantic search found related but not exact match
 - Documentation incomplete

Solutions:
 - Use exact method name instead of description
 - Try alternative query phrasing
 - Check if method is from БСП (use search_bsp_functions)

Typical response time: <1s
First query after restart: 3-5s (cache warm-up)
Memory usage: ~2GB (with full documentation loaded)
Disk usage: ~16.8GB (documentation + embeddings)

Optimization tips:
 - Use specific queries (faster than broad searches)
 - Cache results in RLM for repeated queries
 - Batch multiple queries if possible

Deployment cost:
 - Docker image: ~16.8GB download (one-time)
 - Disk space: ~16.8GB persistent
 - Memory: ~2GB RAM during operation
 - CPU: Minimal (<5% average)

Runtime cost:
 - Embedding model: OpenRouter (qwen/qwen3-embedding-8b)
 - Cost: ~$0.0001 per query (negligible)
 - Alternative: Use local Ollama (free, but slower)