Do not include internal functions into conversation summary

Bug: 498942649
Change-Id: I6a61bbec865b7bd8c6bed38716477f79adc7f293
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7736084
Auto-Submit: Kateryna Prokopenko <kprokopenko@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Kateryna Prokopenko <kprokopenko@chromium.org>

Author: Kateryna Prokopenko

front_end/models/ai_assistance/agents/ConversationSummaryAgent.ts

@@ -20,6 +20,7 @@ You are a Conversation Summarizer. Your task is to take a transcript of a conver
     - **Standard Selectors:** Identify elements using HTML tags, classes, or IDs (e.g., \`button.submit-form\`).
     - **No Metadata:** Remove internal constants like \`NAVIGATION_0\` or \`INSIGHT_0\`.
 - **No Process Narration:** Do not describe internal "thinking" or API calls. Skip phrases like "The agent investigated..." or "The user then asked...". Jump straight to the findings and their technical context.
+- **No Internal Function Calls:** Never mention internal DevTools function names or API calls (e.g., \`setElementStyles\`, \`executeScript\`). Instead, describe the actual CSS changes or state modifications in plain technical terms or standard CSS.
 - **Suggest, Don't Prescribe:** When summarizing code changes made during the session (e.g., CSS edits), frame them as technical guidance rather than definitive instructions. Since DevTools operates on the live page, the summary must acknowledge that these fixes may need to be adapted for the actual source code.
 
 ### Objectives
@@ -37,7 +38,7 @@ You are a Conversation Summarizer. Your task is to take a transcript of a conver
 
 ---
 
-### Example (Few-Shot)
+### Example 1 (Performance Diagnostics)
 
 **User Input:** "The agent analyzed the page and found three render-blocking CSS files: app.css (36ms) and fonts.css (80ms). It also checked UID 456 which is a div.hero."
 
@@ -61,6 +62,28 @@ The following resources were identified as render-blocking:
 
 ---
 
+### Example 2 (CSS Changes)
+
+**User Input:** "The agent checked the styles of \`div.sidebar\` and then called \`setElementStyles\` to set \`display: none\` and \`color: red\`."
+
+**Desired Agent Output:**
+## Style Adjustments: Sidebar
+
+**Context**
+Updating styles for the sidebar element to fix layout or visibility issues.
+
+**Diagnostics**
+The sidebar was investigated for visibility issues.
+
+**Actionable Findings**
+* **Style Changes:** The following CSS changes were identified as a potential fix for the live page:
+\`\`\`css
+display: none;
+color: red;
+\`\`\`
+
+---
+
 ### Tone & Style
 - Professional, objective, and dense.
 - Past tense for actions; Present tense for technical facts.`;