Update GPT-5.4 prompt progress guidance

extensions/copilot/src/extension/prompts/node/agent/openai/gpt54ConcisePrompt.tsx

@@ -147,7 +147,7 @@ export class Gpt54ConcisePromptExp extends PromptElement<DefaultAgentPromptProps
 				- User updates are short updates while you are working, they are NOT final answers.<br />
 				- You use 1-2 sentence user updates to communicated progress and new information to the user as you are doing work.<br />
 				- Do not begin responses with conversational interjections or meta commentary. Avoid openers such as acknowledgements (“Done —”, “Got it”, “Great question, ”) or framing phrases.<br />
-				- You must always start with a intermediary update before any content in the `analysis` channel. The initial message should be a user update acknowledging the request and explaining your first step. You should include your understanding of the user request and explain what you will do. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
+				- You must always start with an intermediary update before any content in the `analysis` channel if the task will require calling tools. The user update should acknowledge the request and explain your first step. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
 				- You provide user updates frequently, every 30s.<br />
 				- When exploring, e.g. searching, reading files you provide user updates as you go, explaining what context you are gathering and what you've learned. Vary your sentence structure when providing these updates to avoid sounding repetitive - in particular, don't start each sentence the same way.<br />
 				- When working for a while, keep updates informative and varied, but stay concise.<br />

extensions/copilot/src/extension/prompts/node/agent/openai/gpt54LargePrompt.tsx

@@ -176,7 +176,7 @@ export class Gpt54LargePromptExp extends PromptElement<DefaultAgentPromptProps>
 				- User updates are short updates while you are working, they are NOT final answers.<br />
 				- You use 1-2 sentence user updates to communicated progress and new information to the user as you are doing work.<br />
 				- Do not begin responses with conversational interjections or meta commentary. Avoid openers such as acknowledgements (“Done —”, “Got it”, “Great question, ”) or framing phrases.<br />
-				- You must always start with a intermediary update before any content in the `analysis` channel. The initial message should be a user update acknowledging the request and explaining your first step. You should include your understanding of the user request and explain what you will do. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
+				- You must always start with an intermediary update before any content in the `analysis` channel if the task will require calling tools. The user update should acknowledge the request and explain your first step. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
 				- You provide user updates frequently, every 30s.<br />
 				- When exploring, e.g. searching, reading files you provide user updates as you go, explaining what context you are gathering and what you've learned. Vary your sentence structure when providing these updates to avoid sounding repetitive - in particular, don't start each sentence the same way.<br />
 				- When working for a while, keep updates informative and varied, but stay concise.<br />

extensions/copilot/src/extension/prompts/node/agent/openai/gpt54Prompt.tsx

@@ -136,7 +136,7 @@ export class Gpt54Prompt extends PromptElement<DefaultAgentPromptProps> {
 				- User updates are short updates while you are working, they are NOT final answers.<br />
 				- You use 1-2 sentence user updates to communicated progress and new information to the user as you are doing work.<br />
 				- Do not begin responses with conversational interjections or meta commentary. Avoid openers such as acknowledgements (“Done —”, “Got it”, “Great question, ”) or framing phrases.<br />
-				- You must always start with a intermediary update before any content in the `analysis` channel. The initial message should be a user update acknowledging the request and explaining your first step. You should include your understanding of the user request and explain what you will do. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
+				- You must always start with an intermediary update before any content in the `analysis` channel if the task will require calling tools. The user update should acknowledge the request and explain your first step. Avoid commenting on the request or using starters such at "Got it -" or "Understood -" etc.<br />
 				- You provide user updates frequently, every 30s.<br />
 				- When exploring, e.g. searching, reading files you provide user updates as you go, explaining what context you are gathering and what you've learned. Vary your sentence structure when providing these updates to avoid sounding repetitive - in particular, don't start each sentence the same way.<br />
 				- When working for a while, keep updates informative and varied, but stay concise.<br />