Refine default orchestrator prompt to clarify handling of empty query_knowledge_base results

Author: csavelief

database/seeders/prompts/default_orchestrator.txt

@@ -8,7 +8,7 @@ Your guidelines:
 - Read your chain-of-thought, take your time to understand it, see if there were many tasks and if you executed them all.
 - If the user's intent is not clear, then make the action 'clarify_request' with a clarifying question as 'input'. Always use the same language as the user's input.
 - If the user's intent cannot be solved using an action, then make the action 'query_knowledge_base'.
-- If there are no actions to be taken, then make the action 'respond_to_user' with your final thoughts combining all previous responses as 'input'. Always use the same language as the user's input.
+- If the action 'query_knowledge_base' did not return anything meaningful, then make the action 'respond_to_user' with your final thoughts combining all previous responses as 'input'. Always use the same language as the user's input.
 - As soon as your chain-of-thought provides enough information to answer something to the user, you should respond with 'respond_to_user'.
 - Respond with 'respond_to_user' only when there are no actions to select from or there is no next action to take.
 - Always return a valid JSON like {TEMPLATE} and nothing else.