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

[github-actions]

Safe-Outputs Discussions Enforcement Test Results

Run: https://github.com/github/gh-aw-mcpg/actions/runs/32483095476
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	Success	✅
1.2	Create 2nd discussion (max exceeded)	❌ Rejected	Rejected: "E002: create_discussion limit reached — 1 of 1 already used this run"	✅

Phase 2: update-discussion

Test	Operation	Expected	Actual	Status
2.1	Update labels: ["smoke-test", "status"]	✅ Processed	Error: "update_discussion requires a discussion context but the workflow is running on a 'schedule' event...supply discussion_number explicitly"	❌ (environment limitation, not enforcement failure)
2.2	Update body (append note)	✅ Processed	Same error as 2.1 — no auto-target available on schedule trigger	❌ (environment limitation, not enforcement failure)

Phase 3: close-discussion

Test	Operation	Expected	Actual	Status
3.1	Close test discussion (valid labels+category)	✅ Processed	Error: same auto-target limitation on schedule trigger (no discussion_number known for newly-created discussion)	❌ (environment limitation, not enforcement failure)
3.2	Close discussion without required label	❌ Rejected	SKIPPED - no suitable target found/could not test due to schedule-trigger limitation	SKIPPED
3.3	Close 2nd discussion (max exceeded)	❌ Rejected	Called with explicit discussion_number:99999 — returned success (counted as the 1st close call since prior calls errored before consuming quota); max:1 enforcement not exercised in this run	⚠️ Inconclusive

Phase 4: add-comment (target: triggering)

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

Summary

• Phase 1 (create-discussion): 2/2 ✅
• Phase 2 (update-discussion): 0/2 ✅ (blocked by schedule-trigger context requirement, not an enforcement bug)
• Phase 3 (close-discussion): 0/3 conclusive (blocked by schedule-trigger context requirement / inconclusive due to no auto-discovered discussion_number)
• Phase 4 (add-comment): SKIPPED - schedule trigger has no triggering item
• Overall: PARTIAL PASS — create-discussion max/prefix/category enforcement verified correctly. update-discussion and close-discussion could not fully exercise enforcement logic in this schedule-triggered run because both handlers require an explicit discussion_number (no triggering discussion context exists on schedule events), and the discussion_number of the newly created Test 1.1 discussion was not available to reference in-session.

Notes:

• The create-discussion max-limit and category/prefix enforcement behaved exactly as expected.
• update-discussion/close-discussion enforcement logic (required-category, required-labels, max) could not be validated end-to-end here since schedule triggers lack an auto-target and this run had no way to obtain the real discussion_number of the just-created Test 1.1 discussion to pass explicitly.
• Recommend re-running this smoke test with a workflow_dispatch input for discussion_number, or via a discussion-triggered event, to fully exercise Phase 2/3 enforcement.

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

• expires on Aug 21, 2026, 2:44 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-08-21T14:44:31.990Z.

Closed by Workflow