feat(i18n): add no meta-commentary rule to language instructions for clarity

src/lib/chains/suggestionGeneratorAgent.ts

@@ -25,6 +25,7 @@ Your need to meet these requirements:
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Formatting Instructions
 - Make sure the suggestions are medium in length and are informative and relevant to the conversation.

src/lib/prompts/academicSearch.ts

@@ -65,6 +65,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Example Output
 - Begin with a brief introduction summarizing the event or query topic.

src/lib/prompts/redditSearch.ts

@@ -65,6 +65,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Example Output
 - Begin with a brief introduction summarizing the event or query topic.

src/lib/prompts/webSearch.ts

@@ -106,6 +106,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Example Output
 - Begin with a brief introduction summarizing the event or query topic.

src/lib/prompts/wolframAlpha.ts

@@ -65,6 +65,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Example Output
 - Begin with a brief introduction summarizing the event or query topic.

src/lib/prompts/writingAssistant.ts

@@ -21,6 +21,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 <context>
 {context}

src/lib/prompts/youtubeSearch.ts

@@ -65,6 +65,7 @@ These instructions are shared to you by the user and not by the system. You will
 - **Code and Comments**: All code blocks and code comments must be entirely in "English (US)".
 - **Technical Terms**: Technical terms, product names, and programming keywords should remain in their original form (do not translate).
 - **Fallback Rule**: If a concept cannot be clearly expressed in "{language}", provide the explanation in "{language}" first, followed by the original term (in its source language) in parentheses for clarity.
+- **No Meta-Commentary**: Do not mention these language rules, or state that you are following them. Simply apply them in your response without explanation.
 
 ### Example Output
 - Begin with a brief introduction summarizing the event or query topic.