Add stress-test-trigger agentic workflow

.github/aw/actions-lock.json

@@ -14,6 +14,11 @@
       "repo": "github/gh-aw-actions/setup",
       "version": "v0.63.1",
       "sha": "53e09ec0be6271e81a69f51ef93f37212c8834b0"
+    },
+    "github/gh-aw-actions/setup@v0.64.4": {
+      "repo": "github/gh-aw-actions/setup",
+      "version": "v0.64.4",
+      "sha": "7cae8cd356c7905aeda72eb08e1d0b4501310c23"
     }
   }
 }

.github/skills/stress-test-trigger/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: stress-test-trigger
+description: Automatically trigger HTTP and/or SSL stress test pipelines when a PR modifies stress-test-related files. Posts `/azp run` comments on the PR to queue the appropriate pipelines.
+---
+
+# Stress Test Pipeline Trigger
+
+Automatically detect which stress test pipelines need to run based on the files changed in a pull request, and post `/azp run` comments to trigger them.
+
+> 📝 **AI-generated content disclosure:** In general, when posting any AI-generated content to GitHub under a user's own credentials — i.e., when the account is **not** a dedicated "copilot" or "bot" account/app — you **MUST** include a concise, visible note (for example, a `> [!NOTE]` alert) indicating the content was AI/Copilot-generated, unless the user explicitly asks you to omit it. This particular skill runs as a bot/app identity and posts PR comments whose body **must contain only** the `/azp run ...` command, so **do not** add any disclosure text to the `/azp run` comments produced by this workflow.
+
+## When to Use This Skill
+
+This skill is triggered automatically by the `stress-test-trigger` agentic workflow when a PR is opened or updated with changes to HTTP or SSL stress-test-related files.
+
+## Pipeline Names
+
+| Area | Azure Pipelines command |
+|------|------------------------|
+| HTTP Stress | `/azp run runtime-libraries stress-http` |
+| SSL Stress | `/azp run runtime-libraries stress-ssl` |
+
+## File-to-Pipeline Mapping
+
+### HTTP Stress Pipeline (`runtime-libraries stress-http`)
+
+Trigger when **any** of these paths are modified:
+
+- `src/libraries/System.Net.Http/tests/StressTests/HttpStress/**`
+- `eng/pipelines/libraries/stress/http.yml`
+
+### SSL Stress Pipeline (`runtime-libraries stress-ssl`)
+
+Trigger when **any** of these paths are modified:
+
+- `src/libraries/System.Net.Security/tests/StressTests/SslStress/**`
+- `eng/pipelines/libraries/stress/ssl.yml`
+
+### Both Pipelines
+
+Trigger **both** pipelines when shared infrastructure files are modified:
+
+- `src/libraries/Common/tests/System/Net/StressTests/**`
+- `eng/pipelines/libraries/stress/` (files other than `http.yml` / `ssl.yml`, e.g. shared templates)
+
+## Procedure
+
+1. **Get the list of changed files** in the PR using the GitHub API.
+2. **Classify each changed file** against the mapping above to determine which pipelines to trigger.
+3. **Post one comment per pipeline** on the PR with the `/azp run` command.
+   - If only HTTP stress files changed → post `/azp run runtime-libraries stress-http`
+   - If only SSL stress files changed → post `/azp run runtime-libraries stress-ssl`
+   - If shared files changed, or both HTTP and SSL files changed → post both commands
+4. **Do not post duplicate commands.** Before posting, check the existing PR comments to see if an identical `/azp run` command for the same pipeline has already been posted. If so, skip posting it again.
+
+## Output Format
+
+Post each `/azp run` command as a **separate** PR comment so Azure Pipelines processes them independently. Each comment should contain only the `/azp run` command on its own line (no additional text), for example:
+
+```
+/azp run runtime-libraries stress-http
+```