few prompt tweaks

Author: vijay upadya

src/extension/linkify/test/node/modelFilePathLinkifier.spec.ts

@@ -51,6 +51,12 @@ suite('Model File Path Linkifier', () => {
 		assertPartsEqual(result.parts, ['other']);
 	});
 
+	test('Should return label when text omits path', async () => {
+		const service = createTestLinkifierService('src/file.ts');
+		const result = await linkify(service, '[line 54](src/file.ts#L54)');
+		assertPartsEqual(result.parts, ['line 54']);
+	});
+
 	test('Should fallback for invalid anchor syntax', async () => {
 		const service = createTestLinkifierService('src/file.ts');
 		const result = await linkify(service, '[src/file.ts](src/file.ts#Lines10-12)');

src/extension/prompts/node/agent/fileLinkificationInstructions.tsx

@@ -9,18 +9,20 @@ import { Tag } from '../base/tag';
 export class FileLinkificationInstructions extends PromptElement<{}> {
 	render() {
 		return <Tag name='file_linkification'>
-			ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations:<br />
-			[path/to/file.ts](path/to/file.ts) - whole file<br />
-			[path/to/file.ts](path/to/file.ts#L10) - single line<br />
-			[path/to/file.ts](path/to/file.ts#L10-12) - line range<br />
-			When listing multiple references, start each item with the linked path, for example:<br />
-			[path/to/chatQuick.ts](path/to/chatQuick.ts#L142) - awaiting a call to open the chat view<br />
-			[path/to/chatQuick.ts](path/to/chatQuick.ts#L321) - awaiting the chat view widget<br />
+			ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations. Use links inside normal sentences, not as the entire answer.<br />
+			Format examples:<br />
+			- `The handler lives in [path/to/file.ts](path/to/file.ts#L10).` (single line)<br />
+			- `See [path/to/file.ts](path/to/file.ts#L10-12) for the range.`<br />
+			- `Configuration is defined in [path/to/file.ts](path/to/file.ts).` (whole file)<br />
+			When you need a bullet list of references, write a short description before the link, for example:<br />
+			- Await chat view: [path/to/chatQuick.ts](path/to/chatQuick.ts#L142)<br />
+			- Show widget: [path/to/chatQuick.ts](path/to/chatQuick.ts#L321)<br />
 			Examples:<br />
 			❌ `The function is in exampleScript.ts at line 25.`<br />
 			✓ `The function is in [exampleScript.ts](exampleScript.ts#L25).`<br />
 			Critical rules:<br />
-			- Link text = exact file path only (no backticks, no `#L` in the visible text, no extra wording). Keep any `#L` anchors in the link target, for example `[src/file.ts](src/file.ts#L25)`.<br />
+			- Link text must be the exact file path (no backticks, no `#L` in the visible text, no extra wording). Keep the `#L` anchor in the **link target**, e.g. `[src/file.ts](src/file.ts#L25)`.<br />
+			- Always include both brackets **and** parentheses. `[src/file.ts](src/file.ts#L25)` is valid; `[src/file.ts#L25]` is not.<br />
 			- Path format: Strip drive letters and workspace parent folders - use only path after workspace root<br />
 			- Transform `c:\Repos\workspace\src\file.ts` → `[src/file.ts](src/file.ts)`<br />
 			- Always use forward slashes `/`, never backslashes `\`<br />