[aw] Smoke Safe-Outputs Discussions reported incomplete result

Workflow Failure

Workflow: Smoke Safe-Outputs Discussions
Branch: main
Run: https://github.com/github/gh-aw-mcpg/actions/runs/32202268753

Reasons:

• Completed all discussion enforcement smoke tests but could not post the final results issue because I accidentally exhausted the create_issue quota (max:1) with a placeholder debugging call before submitting the real report.

  Test results summary (not posted as issue due to quota):

Phase 1 (create-discussion): 1.1 PASS (success, labels param unsupported by schema so retried without it), 1.2 PASS (rejected: E002 create_discussion limit reached — 1 of 1 already used).

Phase 2 (update-discussion): 2.1 PASS (success, required explicit discussion_number since schedule trigger has no auto-target context), 2.2 rejected with E002 update_discussion limit reached — 1 of 1 already used this run (this safe-output enforces a global max of 1 call per run total, not per distinct field, so labels and body could not both be updated in the same run — a real config constraint, not a bug).

Phase 3 (close-discussion): 3.1 PASS (success, required explicit discussion_number), 3.2 SKIPPED (no unlabeled discussion available to test negative case), 3.3 PASS (rejected: E002 close_discussion limit reached — 1 of 1 already used).

Phase 4 (add-comment): all SKIPPED — schedule trigger has no triggering item.

Root cause of failure to report: while troubleshooting that jq/python3/node were all blocked by the sandbox's command policy (only literal string args to safeoutputs CLI work, not piped JSON via jq -Rs), I ran a throwaway safeoutputs create_issue --title "test" --body "..." call to verify the CLI flag syntax worked. That call succeeded and consumed the max:1 create_issue quota, so the subsequent call with the real, complete report body was rejected with E002. Lesson: avoid any create_issue/create_discussion probing calls, even with flags instead of piped JSON, since every call counts against quota regardless of content.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw-mcpg/actions/runs/32202268753

safe-outputs:
  report-failure-as-issue: false

Generated from Smoke Safe-Outputs Discussions · 66.9 AIC · ◷

• expires on Aug 26, 2026, 12:48 AM UTC