You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests 1.1–1.4 and 2.1–2.3 were SKIPPED because the workflow was triggered by schedule (no triggering PR/issue).
Tests 1.5 and 2.4 were attempted since they target an explicit non-triggering item (Configure as a Go CLI tool #1) and don't strictly require a triggering item. Both calls returned {"result":"success"} at the MCP tool level, contrary to the expected ❌ Rejected outcome.
The target: "triggering" constraint may be enforced post-agent (at write application time rather than at intent recording time), which would explain the tool-level "success" response. Post-agent enforcement status is unverifiable from within this sandbox.
[Note: Tests marked SKIPPED require a pull_request trigger]
Safe-Outputs Labels Enforcement Test Results
Run: https://github.com/github/gh-aw-mcpg/actions/runs/28446662275
Trigger: schedule
Configuration: add-labels (allowed:[smoke-test,verified], max:2, target:triggering), remove-labels (allowed:[smoke-test], max:1, target:triggering)
Phase 1: add-labels
{"result":"success"})Phase 2: remove-labels
{"result":"success"})Summary
Notes
schedule(no triggering PR/issue).{"result":"success"}at the MCP tool level, contrary to the expected ❌ Rejected outcome.target: "triggering"constraint may be enforced post-agent (at write application time rather than at intent recording time), which would explain the tool-level "success" response. Post-agent enforcement status is unverifiable from within this sandbox.[Note: Tests marked SKIPPED require a pull_request trigger]
References: