hero-scenarios: switch to hero-scenarios.md and support fork PRs (#42268)

* Switch hero-scenarios from README.md to hero-scenarios.md

Update workflow definition and guidelines to generate hero-scenarios.md
instead of README.md, since most service README files contain only
AutoRest configuration and are not suitable for hero scenarios.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Switch hero-scenarios trigger to label_command

Use the label_command trigger instead of manual pull_request+labeled
filtering. This auto-removes the label after firing (re-triggerable)
and adds workflow_dispatch for manual testing.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* hero-scenarios: switch to pull_request_target for fork PR support

- Replace label_command with pull_request_target + forks to support
  PRs from forks while maintaining the same label-driven UX
- Add on.steps label removal in pre_activation job
- Add explicit workflow_dispatch trigger for manual runs
- Recompile with gh-aw v0.68.0

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* address review: upgrade to actions/github-script@v9

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Deyaa Eldeen <deyaaeldeen@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: deyaaeldeen

.github/aw/actions-lock.json

@@ -10,6 +10,16 @@
       "version": "v7",
       "sha": "f28e40c7f34bde8b3046d885e986cb6290c5673b"
     },
+    "actions/github-script@v8": {
+      "repo": "actions/github-script",
+      "version": "v8",
+      "sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
+    },
+    "actions/github-script@v9": {
+      "repo": "actions/github-script",
+      "version": "v9",
+      "sha": "373c709c69115d41ff229c7e5df9f8788daa9553"
+    },
     "actions/github-script@v9.0.0": {
       "repo": "actions/github-script",
       "version": "v9.0.0",

.github/prompts/hero-scenarios-guidelines.md

@@ -14,21 +14,19 @@
 4. If no specification surface was changed, post a single message saying
    no hero scenarios are applicable and stop.
 
-## Step 1 — Check for Existing README
+## Step 1 — Check for Existing Hero Scenarios
 
-Check whether the service already has a `README.md` with hero scenarios.
+Check whether the service already has a `hero-scenarios.md` file.
 Look in the top-level service directory (e.g.,
-`specification/loadtestservice/README.md`) and in each spec subdirectory
-(e.g., `resource-manager/Microsoft.LoadTestService/loadtesting/readme.md`,
-`data-plane/loadtesting/readme.md`).
-
-- **If no README with hero scenarios exists** (or all READMEs only
-  contain AutoRest configuration), you will generate a full suggested
-  `README.md` in Step 3.
-- **If a README already exists** with substantive service documentation,
-  read it and note the existing hero scenarios. In Step 3, you will only
-  suggest new scenarios that cover API surface introduced by this PR and
-  not already covered.
+`specification/loadtestservice/hero-scenarios.md`) and in each spec subdirectory
+(e.g., `resource-manager/Microsoft.LoadTestService/loadtesting/hero-scenarios.md`,
+`data-plane/loadtesting/hero-scenarios.md`).
+
+- **If no `hero-scenarios.md` exists**, you will generate a full suggested
+  `hero-scenarios.md` in Step 3.
+- **If a `hero-scenarios.md` already exists**, read it and note the existing
+  hero scenarios. In Step 3, you will only suggest new scenarios that cover
+  API surface introduced by this PR and not already covered.
 
 ## Step 2 — Analyze the API Surface
 
@@ -250,27 +248,27 @@ For each scenario, include:
 
 ## Step 4 — Post the Suggestion
 
-**If no README exists**, use `add-comment` to post a PR comment with a
-full suggested README:
+**If no `hero-scenarios.md` exists**, use `add-comment` to post a PR comment
+with a full suggested file:
 
 ```
-## 📖 Suggested README.md
+## 📖 Suggested hero-scenarios.md
 
-> **Path:** `specification/{service}/{specDir}/README.md`
+> **Path:** `specification/{service}/{specDir}/hero-scenarios.md`
 >
-> This service directory has no README documenting the service and its
-> hero scenarios. Consider adding one:
+> This service directory has no `hero-scenarios.md` documenting hero
+> scenarios. Consider adding one:
 
-<the README content as raw markdown — do NOT wrap it in a code fence>
+<the hero-scenarios.md content as raw markdown — do NOT wrap it in a code fence>
 ```
 
-The README should include:
+The file should include:
 1. **Service name and one-paragraph description** — what the service
    does, who it is for, and what problem it solves.
 2. **Hero scenarios** — the scenarios generated in Step 3.
 
-**If a README already exists**, post an inline code suggestion on the
-README file using `create-pull-request-review-comment`. Place the
+**If a `hero-scenarios.md` already exists**, post an inline code suggestion on
+the file using `create-pull-request-review-comment`. Place the
 comment at the end of the file and use a GitHub suggestion block so the
 author can apply it with one click:
 
@@ -283,6 +281,6 @@ author can apply it with one click:
 Then submit the review using `submit-pull-request-review` with event
 `COMMENT` and a one-sentence body summarizing what was suggested.
 
-If the existing README already covers all the API surface in this PR,
-submit a `COMMENT` review with a one-sentence body confirming no new
-scenarios are needed.
+If the existing `hero-scenarios.md` already covers all the API surface in
+this PR, submit a `COMMENT` review with a one-sentence body confirming no
+new scenarios are needed.