Fix incorrect codeql test extract references and PR template path

Co-authored-by: data-douser <[email protected]>

Author: Copilot

.github/PULL_REQUEST_TEMPLATE/copilot-template.md

@@ -3,7 +3,7 @@
 ## Agent Information
 
 **Generated by**: `@copilot` using the [agent-name] agent  
-**Agent Definition**: [../.github/agents/agent-name.md](../.github/agents/agent-name.md)
+**Agent Definition**: [agent-name.md](../agents/agent-name.md)
 
 ## Changes Summary
 

.github/instructions/javascript_cap_ql.instructions.md

@@ -16,7 +16,6 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS follow test-driven development (TDD) practices using CodeQL test commands.
 - ALWAYS run `codeql query format --in-place <file>` before committing changes to QL files.
 - ALWAYS use `codeql test run` to validate query changes before committing.
-- ALWAYS use `codeql test extract` to create test databases for AST exploration.
 - ALWAYS validate query behavior with both positive (should alert) and negative (should not alert) test cases.
 - NEVER make assumptions about CAP framework behavior - validate with real code and CodeQL CLI.
 - NEVER commit query changes without passing tests.
@@ -44,7 +43,7 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS create comprehensive test cases in `javascript/frameworks/cap/test/`.
 - ALWAYS include both JavaScript and CDS files in tests when relevant.
 - ALWAYS verify expected results before accepting with `codeql test accept`.
-- ALWAYS use `codeql test extract` + PrintAST query to understand unfamiliar patterns.
+- ALWAYS use `codeql test run` with a PrintAST query to understand unfamiliar patterns.
 
 ## PREFERENCES
 

.github/instructions/javascript_ui5_ql.instructions.md

@@ -16,7 +16,6 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS follow test-driven development (TDD) practices using CodeQL test commands.
 - ALWAYS run `codeql query format --in-place <file>` before committing changes to QL files.
 - ALWAYS use `codeql test run` to validate query changes before committing.
-- ALWAYS use `codeql test extract` to create test databases for AST exploration.
 - ALWAYS validate query behavior with both positive (should alert) and negative (should not alert) test cases.
 - NEVER make assumptions about UI5 framework behavior - validate with real code and CodeQL CLI.
 - NEVER commit query changes without passing tests.
@@ -49,7 +48,7 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS create comprehensive test cases in `javascript/frameworks/ui5/test/`.
 - ALWAYS include both JavaScript controllers and XML views in tests.
 - ALWAYS verify expected results before accepting with `codeql test accept`.
-- ALWAYS use `codeql test extract` + PrintAST query to understand unfamiliar patterns.
+- ALWAYS use `codeql test run` with a PrintAST query to understand unfamiliar patterns.
 - ALWAYS test binding expression parsing separately.
 
 ## PREFERENCES

.github/instructions/javascript_xsjs_ql.instructions.md

@@ -16,7 +16,6 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS follow test-driven development (TDD) practices using CodeQL test commands.
 - ALWAYS run `codeql query format --in-place <file>` before committing changes to QL files.
 - ALWAYS use `codeql test run` to validate query changes before committing.
-- ALWAYS use `codeql test extract` to create test databases for AST exploration.
 - ALWAYS validate query behavior with both positive (should alert) and negative (should not alert) test cases.
 - NEVER make assumptions about XSJS framework behavior - validate with real code and CodeQL CLI.
 - NEVER commit query changes without passing tests.
@@ -47,7 +46,7 @@ This file contains instructions for working with CodeQL query (`.ql`) and librar
 - ALWAYS create comprehensive test cases in `javascript/frameworks/xsjs/test/`.
 - ALWAYS include realistic XSJS code patterns in tests.
 - ALWAYS verify expected results before accepting with `codeql test accept`.
-- ALWAYS use `codeql test extract` + PrintAST query to understand unfamiliar patterns.
+- ALWAYS use `codeql test run` with a PrintAST query to understand unfamiliar patterns.
 
 ## PREFERENCES