Smoke Copilot: enforce add_comment budget in prompt (#34611)

Author: Copilot

.github/workflows/smoke-copilot.md

@@ -145,6 +145,15 @@ Talk like a caveman in all your responses and outputs. Use short, broken sentenc
 
 **IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.**
 
+## Hard Limit: `add_comment` Budget
+
+`safe-outputs.add-comment.max` is `2`. Never exceed 2 total `add_comment` calls in this run.
+
+- Call #1 is required for the discussion interaction test (comment on latest discussion).
+- Call #2 depends on trigger:
+  - `pull_request` event: post the brief PR summary comment, and **skip** the fun discussion follow-up comment.
+  - non-`pull_request` event: **skip** the PR summary comment and post the fun discussion follow-up comment.
+
 ## Tool Access Overview
 
 This workflow uses `cli-proxy: true`. The following MCP servers are **NOT available as MCP tools** — they are mounted exclusively as **shell CLI commands** (see `<mcp-clis>` section above). You **must** use them via the `bash` tool:
@@ -208,7 +217,7 @@ These are **not** MCP protocol tools — they are bash executables. Call them wi
    - Overall status: PASS or FAIL
    - Mention the pull request author and any assignees
 
-4. Use the `add_comment` tool to add a **fun and creative comment** to the newly created discussion (use the temporary ID `aw_smoke_discussion` from step 11) - be playful and entertaining in your comment
+4. **Only if this workflow was NOT triggered by a pull_request event**: Use the `add_comment` tool to add a **fun and creative comment** to the newly created discussion (use the temporary ID `aw_smoke_discussion` from step 11) - be playful and entertaining in your comment
 
 5. Use the `send_slack_message` tool to send a brief summary message (e.g., "Smoke test ${{ github.run_id }}: All tests passed! ✅")
 

pkg/workflow/testdata/TestWasmGolden_CompileFixtures/smoke-copilot.golden

@@ -240,6 +240,15 @@ jobs:
 
           **IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.**
 
+          ## Hard Limit: `add_comment` Budget
+          
+          `safe-outputs.add-comment.max` is `2`. Never exceed 2 total `add_comment` calls in this run.
+          
+          - Call #1 is required for the discussion interaction test (comment on latest discussion).
+          - Call #2 depends on trigger:
+            - `pull_request` event: post the brief PR summary comment, and **skip** the fun discussion follow-up comment.
+            - non-`pull_request` event: **skip** the PR summary comment and post the fun discussion follow-up comment.
+          
           ## Test Requirements
 
           1. **GitHub MCP Testing**: Review the last 2 merged pull requests in __GH_AW_GITHUB_REPOSITORY__
@@ -270,13 +279,13 @@ jobs:
                - Timestamp
                - Pull request author and assignees
 
-          2. Add a **very brief** comment (max 5-10 lines) to the current pull request with:
+          2. **Only if this workflow was triggered by a pull_request event**: Add a **very brief** comment (max 5-10 lines) to the current pull request with:
              - PR titles only (no descriptions)
              - ✅ or ❌ for each test result
              - Overall status: PASS or FAIL
              - Mention the pull request author and any assignees
 
-          3. Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
+          3. **Only if this workflow was NOT triggered by a pull_request event**: Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
 
           4. Use the `send_slack_message` tool to send a brief summary message (e.g., "Smoke test __GH_AW_GITHUB_RUN_ID__: All tests passed! ✅")
 
@@ -899,4 +908,3 @@ jobs:
             setupGlobals(core, github, context, exec, io, getOctokit);
             const { main } = require('${{ runner.temp }}/gh-aw/actions/check_membership.cjs');
             await main();
-

pkg/workflow/testdata/wasm_golden/WasmBinary/smoke-copilot.golden

@@ -240,6 +240,15 @@ jobs:
 
           **IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.**
 
+          ## Hard Limit: `add_comment` Budget
+          
+          `safe-outputs.add-comment.max` is `2`. Never exceed 2 total `add_comment` calls in this run.
+          
+          - Call #1 is required for the discussion interaction test (comment on latest discussion).
+          - Call #2 depends on trigger:
+            - `pull_request` event: post the brief PR summary comment, and **skip** the fun discussion follow-up comment.
+            - non-`pull_request` event: **skip** the PR summary comment and post the fun discussion follow-up comment.
+          
           ## Test Requirements
 
           1. **GitHub MCP Testing**: Review the last 2 merged pull requests in __GH_AW_GITHUB_REPOSITORY__
@@ -270,13 +279,13 @@ jobs:
                - Timestamp
                - Pull request author and assignees
 
-          2. Add a **very brief** comment (max 5-10 lines) to the current pull request with:
+          2. **Only if this workflow was triggered by a pull_request event**: Add a **very brief** comment (max 5-10 lines) to the current pull request with:
              - PR titles only (no descriptions)
              - ✅ or ❌ for each test result
              - Overall status: PASS or FAIL
              - Mention the pull request author and any assignees
 
-          3. Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
+          3. **Only if this workflow was NOT triggered by a pull_request event**: Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
 
           4. Use the `send_slack_message` tool to send a brief summary message (e.g., "Smoke test __GH_AW_GITHUB_RUN_ID__: All tests passed! ✅")
 
@@ -899,4 +908,3 @@ jobs:
             setupGlobals(core, github, context, exec, io, getOctokit);
             const { main } = require('${{ runner.temp }}/gh-aw/actions/check_membership.cjs');
             await main();
-

pkg/workflow/testdata/wasm_golden/fixtures/smoke-copilot.md

@@ -113,6 +113,15 @@ strict: true
 
 **IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.**
 
+## Hard Limit: `add_comment` Budget
+
+`safe-outputs.add-comment.max` is `2`. Never exceed 2 total `add_comment` calls in this run.
+
+- Call #1 is required for the discussion interaction test (comment on latest discussion).
+- Call #2 depends on trigger:
+  - `pull_request` event: post the brief PR summary comment, and **skip** the fun discussion follow-up comment.
+  - non-`pull_request` event: **skip** the PR summary comment and post the fun discussion follow-up comment.
+
 ## Test Requirements
 
 1. **GitHub MCP Testing**: Review the last 2 merged pull requests in ${{ github.repository }}
@@ -143,13 +152,13 @@ strict: true
      - Timestamp
      - Pull request author and assignees
 
-2. Add a **very brief** comment (max 5-10 lines) to the current pull request with:
+2. **Only if this workflow was triggered by a pull_request event**: Add a **very brief** comment (max 5-10 lines) to the current pull request with:
    - PR titles only (no descriptions)
    - ✅ or ❌ for each test result
    - Overall status: PASS or FAIL
    - Mention the pull request author and any assignees
 
-3. Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
+3. **Only if this workflow was NOT triggered by a pull_request event**: Use the `add_comment` tool to add a **fun and creative comment** to the latest discussion (using the `discussion_number` you extracted in step 7) - be playful and entertaining in your comment
 
 4. Use the `send_slack_message` tool to send a brief summary message (e.g., "Smoke test ${{ github.run_id }}: All tests passed! ✅")