formatting changes and slight prompt modification

Author: Tian-hao Zhang

server_api/auth/router.py

@@ -566,4 +566,4 @@ def delete_file(
     # Delete DB records recursively and only remove files from disk for app-managed uploads.
     _delete_file_tree(db, current_user.id, file, delete_disk_files=True)
     db.commit()
-    return {"message": "File deleted"}
+    return {"message": "File deleted"}

server_api/chatbot/chatbot.py

@@ -101,7 +101,7 @@
 1. **For application questions, ground answers in retrieved documentation.** Call search_documentation and base your answer on the returned text. Do NOT invent features, shortcuts, buttons, or workflows.
 2. **Do not fabricate specifics.** Never make up keyboard shortcuts, button labels, or step-by-step instructions unless they come from retrieved docs or a sub-agent response.
 3. **Answer every part of the user's question.** If they ask about two things, address both.
-4. **Be concise and helpful.** If the docs partially cover the topic, share what is documented and note what is not covered. If the docs do not cover the topic at all, say so clearly.
+4. **Use retrieved content even if wording differs.** If the documentation describes relevant features or workflows, use that information to answer the question. Don't claim something isn't documented just because it uses different terminology than the user's question.
 5. **HARD LIMIT: You may call search_documentation EXACTLY 2 times per user question.** After the second call, you MUST answer with the information already retrieved. Do NOT attempt a third search. If the tool returns "Search limit reached", immediately stop and answer based on what you already have.
 6. **Delegate, don't search, for training/inference tasks.** If the user asks for a training command or inference command, use the appropriate sub-agent directly.