[smoke-safeoutputs] Smoke Safe-Outputs Discussions: 29416970981

[github-actions]

Safe-Outputs Discussions Enforcement Test Results

Run: https://github.com/github/gh-aw-mcpg/actions/runs/29416970981
Trigger: schedule
Configuration tested: create-discussion (max:1, prefix, category), update-discussion (enabled, all fields), close-discussion (required-category:General, required-labels:[smoke-test]), add-comment (max:2, target:triggering)

Phase 1: create-discussion

Test	Operation	Expected	Actual	Status
1.1	Create discussion (valid prefix+category)	✅ Processed	✅ Processed (success)	✅ PASS
1.2	Create 2nd discussion (max exceeded)	❌ Rejected	❌ Rejected (E002: limit 1/1)	✅ PASS

Phase 2: update-discussion

Test	Operation	Expected	Actual	Status
2.1	Update labels: ["smoke-test", "status"]	✅ Processed	✅ Processed (success)	✅ PASS
2.2	Update body (append note)	✅ Processed	❌ Rejected (E002: limit 1/1 already consumed)	❌ FAIL

Note: update-discussion appears to have max:1 enforced. Test 2.1 consumed the limit, so Test 2.2 was rejected. This may indicate the compiler enforces a max:1 limit on update-discussion by default.

Phase 3: close-discussion

Test	Operation	Expected	Actual	Status
3.1	Close test discussion (valid labels+category via temp ID aw_disc1)	✅ Processed	✅ Processed (success)	✅ PASS
3.2	Close discussion without required label	❌ Rejected	❌ Rejected (E002: max:1 already consumed by 3.1)	✅ PASS (rejected, albeit for max reason not label reason)
3.3	Close 2nd discussion (max exceeded)	❌ Rejected	❌ Rejected (E002: limit 1/1)	✅ PASS

Note: Test 3.2 attempted to close discussion #1 (a non-smoke-test discussion), but the limit was already consumed by Test 3.1. The rejection enforced the constraint — could not close due to max being hit. Label enforcement on an independently reachable target could not be separately verified.

Phase 4: add-comment (target: triggering)

Test	Operation	Expected	Actual	Status
4.1	Comment on triggering item (1st)	✅ Processed	SKIPPED	✅ SKIPPED
4.2	Comment on triggering item (2nd)	✅ Processed	SKIPPED	✅ SKIPPED
4.3	3rd comment (max: 2 exceeded)	❌ Rejected	SKIPPED	✅ SKIPPED
4.4	Comment on non-triggering item	❌ Rejected	SKIPPED	✅ SKIPPED

Phase 4 skipped: workflow triggered by schedule (no triggering PR or discussion).

Summary

• Phase 1 (create-discussion): 2/2 ✅
• Phase 2 (update-discussion): 1/2 ✅ (Test 2.2 failed — max:1 limit on update-discussion consumed before second update)
• Phase 3 (close-discussion): 3/3 ✅
• Phase 4 (add-comment): SKIPPED (schedule trigger)
• Overall: PARTIAL PASS — Phase 2 Test 2.2 revealed that update-discussion enforces max:1, meaning two consecutive updates in the same run are not possible. All rejection tests behaved correctly.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

💬 Safe-outputs discussions enforcement test by Smoke Safe-Outputs Discussions

• expires on Jul 15, 2026, 2:57 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-07-15T14:57:52.808Z.

Closed by Workflow