Add priority tags (CRITICAL/HIGH/MEDIUM/LOW) to all issues

server.js

@@ -39,7 +39,7 @@ What this file does and whether it has any business existing in its current form
 ## Code Quality
 Tear into readability, naming, structure, anti-patterns, code smells, and idiom violations. For EVERY issue use this exact structure:
 
-**Line 42:** Short summary of the problem — what is wrong and why it matters.
+**[CRITICAL|HIGH|MEDIUM|LOW] Line 42:** Short summary of the problem — what is wrong and why it matters.
 
 \`\`\`diff
 - disgraceful_code()
@@ -53,7 +53,7 @@ Tear into readability, naming, structure, anti-patterns, code smells, and idiom
 ## Performance
 Find the inefficiencies the author was too lazy to notice. Unnecessary allocations, O(n²) where O(n) was trivial, needless copies, hot-path bloat, allocations in loops. For EVERY issue use this exact structure:
 
-**Lines X-Y:** Short summary of the inefficiency — name the wasted work.
+**[CRITICAL|HIGH|MEDIUM|LOW] Lines X-Y:** Short summary of the inefficiency — name the wasted work.
 
 \`\`\`diff
 - slow_version()
@@ -67,7 +67,7 @@ Find the inefficiencies the author was too lazy to notice. Unnecessary allocatio
 ## Security
 Input validation gaps, injection vectors (SQL, XSS, command, path traversal), secrets in code, broken auth, race conditions, unchecked boundaries. If there's nothing, say so in one sentence — don't invent problems. For EVERY issue use this exact structure:
 
-**Line X:** Short summary of the vulnerability — name the attack surface.
+**[CRITICAL|HIGH|MEDIUM|LOW] Line X:** Short summary of the vulnerability — name the attack surface.
 
 \`\`\`diff
 - vulnerable_code()
@@ -81,7 +81,7 @@ Input validation gaps, injection vectors (SQL, XSS, command, path traversal), se
 ## Suggestions
 Numbered list of concrete improvements, ranked ruthlessly by impact. No hand-wavy "consider maybe possibly" language. EVERY suggestion MUST include a \`\`\`diff block — no exceptions. A suggestion without a diff is useless; show the exact code change. Use this exact structure:
 
-1. **Line X:** Short summary of what to improve and why.
+1. **[CRITICAL|HIGH|MEDIUM|LOW] Line X:** Short summary of what to improve and why.
 
 \`\`\`diff
 - current_code()
@@ -111,7 +111,8 @@ Rules:
 - Do NOT pad the review with praise or pleasantries. Respect the reader's time.
 - If the code is genuinely excellent in some area, one dry sentence of acknowledgment is sufficient.
 - Be merciless but never wrong. Every criticism must be technically defensible.
-- NO DUPLICATES: Each issue appears in ONE section only. If a bug is a security vulnerability, put it in Security — not also in Code Quality. If a performance fix is also a suggestion, put it in Performance only. Pick the most relevant section and move on.`;
+- NO DUPLICATES: Each issue appears in ONE section only. If a bug is a security vulnerability, put it in Security — not also in Code Quality. If a performance fix is also a suggestion, put it in Performance only. Pick the most relevant section and move on.
+- PRIORITY TAGS: Every issue MUST start with [CRITICAL], [HIGH], [MEDIUM], or [LOW]. CRITICAL = crashes, data loss, security exploits. HIGH = significant bugs or performance problems. MEDIUM = code smells, minor inefficiencies. LOW = style nitpicks, minor improvements.`;
 
 function buildUserMessage(meta, code) {
   const numbered = code