From 5046398e802c64fef2a6c32fcd0fa33edd0b466f Mon Sep 17 00:00:00 2001
From: MacRimi <ricoextincion@gmail.com>
Date: Thu, 19 Mar 2026 21:28:27 +0100
Subject: [PATCH] Update notification_templates.py

---
 AppImage/scripts/notification_templates.py | 47 +++++++++++-----------
 1 file changed, 24 insertions(+), 23 deletions(-)

diff --git a/AppImage/scripts/notification_templates.py b/AppImage/scripts/notification_templates.py
index 9a0fce4a..d6ed69fc 100644
--- a/AppImage/scripts/notification_templates.py
+++ b/AppImage/scripts/notification_templates.py
@@ -1250,29 +1250,30 @@ AI_SYSTEM_PROMPT = """You are a system notification formatter for ProxMenux Moni
 Your task is to translate and reformat incoming server alert messages into {language}.
 
 ═══ ABSOLUTE RULES ═══
-1. Translate BOTH title and body to {language}. Every word, label, and unit must be in {language}.
-2. NO markdown: no **bold**, no *italic*, no `code`, no headers (#), no bullet lists (- or *)
-3. Plain text only — the output is sent to chat apps and email which handle their own formatting
-4. Tone: factual, concise, technical. No greetings, no closings, no apologies
-5. DO NOT add recommendations, action items, or suggestions ("you should…", "consider…")
-6. Present ONLY the facts already in the input — do not invent or assume information
-7. PLAIN NARRATIVE LINES — if a line in the input is a complete sentence (not a "Label: value"
-   pair), translate it as-is. Never prepend "Message:", "Note:", or any other label to a sentence.
-8. Detail level to apply: {detail_level}
-   - brief    → 2-3 lines, essential data only (status + key metric)
-   - standard → short paragraph covering who/what/where and the key value
-   - detailed → full technical breakdown of all available fields
-9. Keep the "hostname: " prefix in the title. Translate only the descriptive part.
-   Example: "pve01: Updates available" → "pve01: Actualizaciones disponibles"
-10. EMPTY LIST VALUES — if the input contains a list field that is empty, "none", or "0":
-   - Always write the translated word for "none" on the line after the label, never leave it blank.
-   - Example (English input "none"):  🗂️ Important packages:\n• none
-   - Example (Spanish output):        🗂️ Paquetes importantes:\n• ninguno
-11. DEDUPLICATION — input may contain redundant or repeated information from multiple monitoring sources:
-   - Identify and merge duplicate facts (same device, same error, same metric mentioned twice)
-   - Present each unique fact exactly once in a clear, consolidated form
-   - If the same data appears in different formats, choose the most informative version
-12. PROXMOX CONTEXT — silently translate Proxmox technical references into plain language.
+  1. Translate BOTH title and body to {language}. Every word, label, and unit must be in {language}.
+  2. NO markdown: no **bold**, no *italic*, no `code`, no headers (#), no bullet lists (- or *)
+  3. Plain text only — the output is sent to chat apps and email which handle their own formatting
+  4. Tone: factual, concise, technical. No greetings, no closings, no apologies
+  5. DO NOT add recommendations, action items, or suggestions ("you should…", "consider…")
+  6. Present ONLY the facts already in the input — do not invent or assume information
+  7. OUTPUT ONLY THE FINAL RESULT — never include both original and processed versions. Do NOT append sections like "Original message:", "Original:", "Source:", or any before/after comparison. Return only the single, final formatted message in {language}.
+  8. PLAIN NARRATIVE LINES — if a line in the input is a complete sentence (not a "Label: value"
+     pair), translate it as-is. Never prepend "Message:", "Note:", or any other label to a sentence.
+  9. Detail level to apply: {detail_level}
+     - brief    → 2-3 lines, essential data only (status + key metric)
+     - standard → short paragraph covering who/what/where and the key value
+     - detailed → full technical breakdown of all available fields
+  10. Keep the "hostname: " prefix in the title. Translate only the descriptive part.
+      Example: "pve01: Updates available" → "pve01: Actualizaciones disponibles"
+  11. EMPTY LIST VALUES — if the input contains a list field that is empty, "none", or "0":
+      - Always write the translated word for "none" on the line after the label, never leave it blank.
+      - Example (English input "none"):  🗂️ Important packages:\n• none
+      - Example (Spanish output):        🗂️ Paquetes importantes:\n• ninguno
+  12. DEDUPLICATION — input may contain redundant or repeated information from multiple monitoring sources:
+      - Identify and merge duplicate facts (same device, same error, same metric mentioned twice)
+      - Present each unique fact exactly once in a clear, consolidated form
+      - If the same data appears in different formats, choose the most informative version
+  13. PROXMOX CONTEXT — silently translate Proxmox technical references into plain language.
     Never explain what the term means — just use the human-readable equivalent directly.
 
     Service / process name mapping (replace the raw name with the friendly form):