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

[github-actions]

Safe-Outputs Discussions Enforcement Test Results

Run: https://github.com/github/gh-aw-mcpg/actions/runs/24344166837
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+label)	✅ Processed	✅ Returned success	✅
1.2	Create 2nd discussion (max exceeded)	❌ Rejected	✅ Returned success	❌

Phase 2: update-discussion

Test	Operation	Expected	Actual	Status
2.1	Update labels: ["smoke-test", "status"]	✅ Processed	✅ Returned success	✅
2.2	Update body (append note)	✅ Processed	✅ Returned success	✅

Phase 3: close-discussion

Test	Operation	Expected	Actual	Status
3.1	Close test discussion (valid labels+category)	✅ Processed	✅ Returned success	✅
3.2	Close discussion without required label	❌ Rejected	SKIPPED — all visible discussions have smoke-test label	✅ SKIPPED
3.3	Close 2nd discussion (max exceeded)	❌ Rejected	✅ Returned success	❌

Phase 4: add-comment (target: triggering)

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

Summary

• Phase 1 (create-discussion): 1/2 ✅
• Phase 2 (update-discussion): 2/2 ✅
• Phase 3 (close-discussion): 2/3 ✅ (1 skipped)
• Phase 4 (add-comment): SKIPPED (schedule trigger)
• Overall: FAIL

Notes

• Test 1.2 FAIL: The second create_discussion call returned success instead of being rejected. With max: 1 already consumed, this call should have been rejected. It's possible enforcement is asynchronous (applied post-execution) rather than at call time.
• Test 3.3 FAIL: Similarly, the second close_discussion call returned success after max: 1 was already consumed. Same pattern as Test 1.2 — max enforcement may be post-execution.
• Test 3.2 SKIPPED: All discussions in the repository appear to have the smoke-test label (all are created by the smoke-safeoutputs workflow). No suitable non-labeled discussion was found to test label enforcement rejection.

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

• expires on Apr 13, 2026, 2:52 PM UTC