Add punctuation and capitalisation consistency rules to all agent prompts

Adds an IMPORTANT instruction block to all 5 agent prompt templates
(legal, brand, channel best practices, channel tech specs, lead) that
enforces: capitalisation after full stops and in labels, consistent
bullet-point ending style, and "e.g." without a trailing comma.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

backend/app/agents/brand_agent.py

@@ -149,6 +149,10 @@ If the proof is nonsensical, not a marketing material, or cannot be analyzed, se
 - IMPORTANT: Use British English spelling throughout all output (e.g. "authorised" not "authorized", "colour" not "color", "capitalise" not "capitalize", "organised" not "organized", "centre" not "center", "analysed" not "analyzed").
 - IMPORTANT: Never use the words "violation", "violates", or "violated" in your output. Use constructive alternatives such as "issue", "doesn't align with", "doesn't meet", or "conflicts with".
 - IMPORTANT: Use Plain English throughout. Choose simple, clear words over complex vocabulary. Prefer: "add" over "incorporate/integrate", "about" over "regarding", "qualifies as" over "constitutes", "use" over "utilise", "before" over "prior to", "to" over "in order to", "try" over "endeavour", "then" over "subsequently", "put in place" over "implement", "keep/contain" over "constrain", "standard interest rate" over "reversion rate". Avoid unnecessary jargon (e.g. use "exaggerated claim" instead of "puffery"). Feedback should be easy to understand for all users.
+- IMPORTANT: Apply consistent punctuation and capitalisation throughout:
+  (a) Always capitalise the first word after a full stop, including labels like "Recommendation:" and "Issue:".
+  (b) End every bullet point with a full stop if it is a complete sentence. If bullets are short fragments, omit the full stop — but be consistent within the same output.
+  (c) Write "e.g." with no comma after it (e.g. "Apply rotation" not "e.g., Apply rotation").
 """
 
         # Determine if revision fields should be included

backend/app/agents/channel_best_practices_agent.py

@@ -142,6 +142,10 @@ If the proof is nonsensical, not a marketing material, or cannot be analyzed, se
 - IMPORTANT: Use British English spelling throughout all output (e.g. "authorised" not "authorized", "colour" not "color", "capitalise" not "capitalize", "organised" not "organized", "centre" not "center", "analysed" not "analyzed").
 - IMPORTANT: Never use the words "violation", "violates", or "violated" in your output. Use constructive alternatives such as "issue", "doesn't align with", "doesn't meet", or "conflicts with".
 - IMPORTANT: Use Plain English throughout. Choose simple, clear words over complex vocabulary. Prefer: "add" over "incorporate/integrate", "about" over "regarding", "qualifies as" over "constitutes", "use" over "utilise", "before" over "prior to", "to" over "in order to", "try" over "endeavour", "then" over "subsequently", "put in place" over "implement", "keep/contain" over "constrain", "standard interest rate" over "reversion rate". Avoid unnecessary jargon (e.g. use "exaggerated claim" instead of "puffery"). Feedback should be easy to understand for all users.
+- IMPORTANT: Apply consistent punctuation and capitalisation throughout:
+  (a) Always capitalise the first word after a full stop, including labels like "Recommendation:" and "Issue:".
+  (b) End every bullet point with a full stop if it is a complete sentence. If bullets are short fragments, omit the full stop — but be consistent within the same output.
+  (c) Write "e.g." with no comma after it (e.g. "Apply rotation" not "e.g., Apply rotation").
 """
 
         # Determine if revision fields should be included

backend/app/agents/channel_tech_specs_agent.py

@@ -150,6 +150,10 @@ If the proof is nonsensical, not a marketing material, or cannot be analyzed, se
 - IMPORTANT: Use British English spelling throughout all output (e.g. "authorised" not "authorized", "colour" not "color", "capitalise" not "capitalize", "organised" not "organized", "centre" not "center", "analysed" not "analyzed").
 - IMPORTANT: Never use the words "violation", "violates", or "violated" in your output. Use constructive alternatives such as "issue", "doesn't align with", "doesn't meet", or "conflicts with".
 - IMPORTANT: Use Plain English throughout. Choose simple, clear words over complex vocabulary. Prefer: "add" over "incorporate/integrate", "about" over "regarding", "qualifies as" over "constitutes", "use" over "utilise", "before" over "prior to", "to" over "in order to", "try" over "endeavour", "then" over "subsequently", "put in place" over "implement", "keep/contain" over "constrain", "standard interest rate" over "reversion rate". Avoid unnecessary jargon (e.g. use "exaggerated claim" instead of "puffery"). Feedback should be easy to understand for all users.
+- IMPORTANT: Apply consistent punctuation and capitalisation throughout:
+  (a) Always capitalise the first word after a full stop, including labels like "Recommendation:" and "Issue:".
+  (b) End every bullet point with a full stop if it is a complete sentence. If bullets are short fragments, omit the full stop — but be consistent within the same output.
+  (c) Write "e.g." with no comma after it (e.g. "Apply rotation" not "e.g., Apply rotation").
 """
 
         # Determine if revision fields should be included

backend/app/agents/lead_agent.py

@@ -150,6 +150,10 @@ Your summary should:
 - IMPORTANT: Use British English spelling throughout all output (e.g. "authorised" not "authorized", "colour" not "color", "capitalise" not "capitalize", "organised" not "organized", "centre" not "center", "analysed" not "analyzed").
 - IMPORTANT: Never use the words "violation", "violates", or "violated" in your output. Use constructive alternatives such as "issue", "doesn't align with", "doesn't meet", or "conflicts with".
 - IMPORTANT: Use Plain English throughout. Choose simple, clear words over complex vocabulary. Prefer: "add" over "incorporate/integrate", "about" over "regarding", "qualifies as" over "constitutes", "use" over "utilise", "before" over "prior to", "to" over "in order to", "try" over "endeavour", "then" over "subsequently", "put in place" over "implement", "keep/contain" over "constrain", "standard interest rate" over "reversion rate". Avoid unnecessary jargon (e.g. use "exaggerated claim" instead of "puffery"). Feedback should be easy to understand for all users.
+- IMPORTANT: Apply consistent punctuation and capitalisation throughout:
+  (a) Always capitalise the first word after a full stop, including labels like "Recommendation:" and "Issue:".
+  (b) End every bullet point with a full stop if it is a complete sentence. If bullets are short fragments, omit the full stop — but be consistent within the same output.
+  (c) Write "e.g." with no comma after it (e.g. "Apply rotation" not "e.g., Apply rotation").
 {revision_context}
 Here are the specialist reviews:
 {self._format_reviews(reviews)}

backend/app/agents/legal_agent.py

@@ -152,6 +152,10 @@ If the proof is nonsensical, not a marketing material, or cannot be analyzed, se
 - IMPORTANT: Use British English spelling throughout all output (e.g. "authorised" not "authorized", "colour" not "color", "capitalise" not "capitalize", "organised" not "organized", "centre" not "center", "analysed" not "analyzed").
 - IMPORTANT: Never use the words "violation", "violates", or "violated" in your output. Use constructive alternatives such as "issue", "doesn't align with", "doesn't meet", or "conflicts with".
 - IMPORTANT: Use Plain English throughout. Choose simple, clear words over complex vocabulary. Prefer: "add" over "incorporate/integrate", "about" over "regarding", "qualifies as" over "constitutes", "use" over "utilise", "before" over "prior to", "to" over "in order to", "try" over "endeavour", "then" over "subsequently", "put in place" over "implement", "keep/contain" over "constrain", "standard interest rate" over "reversion rate". Avoid unnecessary jargon (e.g. use "exaggerated claim" instead of "puffery"). Feedback should be easy to understand for all users.
+- IMPORTANT: Apply consistent punctuation and capitalisation throughout:
+  (a) Always capitalise the first word after a full stop, including labels like "Recommendation:" and "Issue:".
+  (b) End every bullet point with a full stop if it is a complete sentence. If bullets are short fragments, omit the full stop — but be consistent within the same output.
+  (c) Write "e.g." with no comma after it (e.g. "Apply rotation" not "e.g., Apply rotation").
 """
 
         # Determine if revision fields should be included