Merge branch 'main' into luabud-patch-1

Author: luabud

.github/instructions/learning.instructions.md

@@ -0,0 +1,34 @@
+---
+applyTo: '**'
+description: This document describes how to deal with learnings that you make. (meta instruction)
+---
+
+This document describes how to deal with learnings that you make.
+It is a meta-instruction file.
+
+Structure of learnings:
+
+-   Each instruction file has a "Learnings" section.
+-   Each learning has a counter that indicates how often that learning was useful (initially 1).
+-   Each learning has a 1 sentence description of the learning that is clear and concise.
+
+Example:
+
+```markdown
+## Learnings
+
+-   Prefer `const` over `let` whenever possible (1)
+-   Avoid `any` type (3)
+```
+
+When the user tells you "learn!", you should:
+
+-   extract a learning from the recent conversation
+    _ identify the problem that you created
+    _ identify why it was a problem
+    _ identify how you were told to fix it/how the user fixed it
+    _ generate only one learning (1 sentence) that helps to summarize the insight gained
+-   then, add the reflected learning to the "Learnings" section of the most appropriate instruction file
+
+Important: Whenever a learning was really useful, increase the counter!!
+When a learning was not useful and just caused more problems, decrease the counter.

.github/instructions/testing_feature_area.instructions.md

@@ -0,0 +1,79 @@
+---
+mode: edit
+---
+
+Analyze the specified part of the VS Code Python Extension codebase to generate or update implementation instructions in `.github/instructions/<component>.instructions.md`.
+
+## Task
+
+Create concise developer guidance focused on:
+
+### Implementation Essentials
+
+-   **Core patterns**: How this component is typically implemented and extended
+-   **Key interfaces**: Essential classes, services, and APIs with usage examples
+-   **Integration points**: How this component interacts with other extension parts
+-   **Common tasks**: Typical development scenarios with step-by-step guidance
+
+### Content Structure
+
+````markdown
+---
+description: 'Implementation guide for the <component> part of the Python Extension'
+---
+
+# <Component> Implementation Guide
+
+## Overview
+
+Brief description of the component's purpose and role in VS Code Python Extension.
+
+## Key Concepts
+
+-   Main abstractions and their responsibilities
+-   Important interfaces and base classes
+
+## Common Implementation Patterns
+
+### Pattern 1: [Specific Use Case]
+
+```typescript
+// Code example showing typical implementation
+```
+````
+
+### Pattern 2: [Another Use Case]
+
+```typescript
+// Another practical example
+```
+
+## Integration Points
+
+-   How this component connects to other VS Code Python Extension systems
+-   Required services and dependencies
+-   Extension points and contribution models
+
+## Essential APIs
+
+-   Key methods and interfaces developers need
+-   Common parameters and return types
+
+## Gotchas and Best Practices
+
+-   Non-obvious behaviors to watch for
+-   Performance considerations
+-   Common mistakes to avoid
+
+```
+
+## Guidelines
+- **Be specific**: Use actual class names, method signatures, and file paths
+- **Show examples**: Include working code snippets from the codebase
+- **Target implementation**: Focus on how to build with/extend this component
+- **Keep it actionable**: Every section should help developers accomplish tasks
+
+Source conventions from existing `.github/instructions/*.instructions.md`, `CONTRIBUTING.md`, and codebase patterns.
+
+If `.github/instructions/<component>.instructions.md` exists, intelligently merge new insights with existing content.
+```

.github/prompts/extract-impl-instructions.prompt.md

@@ -0,0 +1,30 @@
+---
+mode: edit
+---
+
+Analyze the user requested part of the codebase (use a suitable <placeholder>) to generate or update `.github/instructions/<placeholder>.instructions.md` for guiding developers and AI coding agents.
+
+Focus on practical usage patterns and essential knowledge:
+
+-   How to use, extend, or integrate with this code area
+-   Key architectural patterns and conventions specific to this area
+-   Common implementation patterns with code examples
+-   Integration points and typical interaction patterns with other components
+-   Essential gotchas and non-obvious behaviors
+
+Source existing conventions from `.github/instructions/*.instructions.md`, `CONTRIBUTING.md`, and `README.md`.
+
+Guidelines:
+
+-   Write concise, actionable instructions using markdown structure
+-   Document discoverable patterns with concrete examples
+-   If `.github/instructions/<placeholder>.instructions.md` exists, merge intelligently
+-   Target developers who need to work with or extend this code area
+
+Update `.github/instructions/<placeholder>.instructions.md` with header:
+
+```
+---
+description: "How to work with the <placeholder> part of the codebase"
+---
+```

.github/prompts/extract-usage-instructions.prompt.md

@@ -2,7 +2,7 @@
     "name": "python",
     "displayName": "Python",
     "description": "Python language support with extension access points for IntelliSense (Pylance), Debugging (Python Debugger), linting, formatting, refactoring, unit tests, and more.",
-    "version": "2025.15.0-dev",
+    "version": "2025.17.0-dev",
     "featureFlags": {
         "usingNewInterpreterStorage": true
     },
@@ -1244,6 +1244,13 @@
                     "when": "controllerId == 'python-tests'"
                 }
             ],
+            "testing/item/gutter": [
+                {
+                    "command": "python.copyTestId",
+                    "group": "navigation",
+                    "when": "controllerId == 'python-tests'"
+                }
+            ],
             "commandPalette": [
                 {
                     "category": "Python",