Minor prompt readjustment

Author: vijay upadya

src/extension/prompts/node/agent/openai/defaultOpenAIPrompt.tsx

@@ -105,10 +105,10 @@ export class DefaultOpenAIAgentPrompt extends PromptElement<DefaultAgentPromptPr
 					Identifiers only: `calculateTotal`, `Person`, `AppConfig`.<br />
 					File path link examples live in fileLinkification section below.<br />
 				</Tag>
+				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>
 			<ResponseTranslationRules />
-			<FileLinkificationInstructions />
 		</InstructionMessage>;
 	}
 }

src/extension/prompts/node/agent/openai/gpt51CodexPrompt.tsx

@@ -83,9 +83,9 @@ class Gpt51CodexPrompt extends PromptElement<DefaultAgentPromptProps> {
 				<Tag name='example'>
 					The class `Person` is in `src/models/person.ts`.
 				</Tag>
+				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>
-			<FileLinkificationInstructions />
 		</InstructionMessage>;
 	}
 }

src/extension/prompts/node/agent/openai/gpt5CodexPrompt.tsx

@@ -76,7 +76,6 @@ class CodexStyleGpt5CodexPrompt extends PromptElement<DefaultAgentPromptProps> {
 			- Tone: collaborative, concise, factual; present tense, active voice; self-contained; no "above/below"; parallel wording.<br />
 			- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.<br />
 			- Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.<br />
-			- File path and line anchor link rules are defined in fileLinkification section below.<br />
 			<FileLinkificationInstructions />
 		</InstructionMessage>;
 	}

src/extension/prompts/node/agent/openai/gpt5Prompt.tsx

@@ -219,10 +219,11 @@ class DefaultGpt5AgentPrompt extends PromptElement<DefaultAgentPromptProps> {
 				<Tag name='example'>
 					The class `Person` is in `src/models/person.ts`.
 				</Tag>
+				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>
 			<ResponseTranslationRules />
-			<FileLinkificationInstructions />
+
 		</InstructionMessage>;
 	}
 }

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-gpt-4.1.spec.snap

@@ -51,8 +51,6 @@ Identifiers only: `calculateTotal`, `Person`, `AppConfig`.
 File path link examples live in fileLinkification section below.
 
 </example>
-
-</outputFormatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -81,6 +79,8 @@ Critical rules:
 
 </fileLinkification>
 
+</outputFormatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-gpt-5.1-codex-mini.spec.snap

@@ -60,8 +60,6 @@ When referring to a filename or symbol in the user's workspace, wrap it in backt
 <example>
 The class `Person` is in `src/models/person.ts`.
 </example>
-
-</special_formatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -90,6 +88,8 @@ Critical rules:
 
 </fileLinkification>
 
+</special_formatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-gpt-5.1-codex.spec.snap

@@ -60,8 +60,6 @@ When referring to a filename or symbol in the user's workspace, wrap it in backt
 <example>
 The class `Person` is in `src/models/person.ts`.
 </example>
-
-</special_formatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -90,6 +88,8 @@ Critical rules:
 
 </fileLinkification>
 
+</special_formatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-gpt-5.spec.snap

@@ -203,8 +203,6 @@ When referring to a filename or symbol in the user's workspace, wrap it in backt
 <example>
 The class `Person` is in `src/models/person.ts`.
 </example>
-
-</final_answer_formatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -233,6 +231,8 @@ Critical rules:
 
 </fileLinkification>
 
+</final_answer_formatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_tools-gpt-4.1.spec.snap

@@ -87,8 +87,6 @@ Identifiers only: `calculateTotal`, `Person`, `AppConfig`.
 File path link examples live in fileLinkification section below.
 
 </example>
-
-</outputFormatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -117,6 +115,8 @@ Critical rules:
 
 </fileLinkification>
 
+</outputFormatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_tools-gpt-5.1-codex-mini.spec.snap

@@ -60,8 +60,6 @@ When referring to a filename or symbol in the user's workspace, wrap it in backt
 <example>
 The class `Person` is in `src/models/person.ts`.
 </example>
-
-</special_formatting>
 <fileLinkification>
 ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
 
@@ -90,6 +88,8 @@ Critical rules:
 
 </fileLinkification>
 
+</special_formatting>
+
 <instructions>
 This is a test custom instruction file
 </instructions>