Skip to content

ci: align trusted Waza auth with current Copilot SDK - #45

Merged
svg153 merged 1 commit into
mainfrom
ci/current-copilot-waza-auth
Sep 17, 2026
Merged

svg153 merged 1 commit into
mainfrom
ci/current-copilot-waza-auth

Conversation

@svg153

@svg153 svg153 commented Sep 17, 2026

Copy link
Copy Markdown
Member

Closes #44.
Refs #35.

Summary

Aligns the existing trusted Waza workflow with the current Copilot SDK authentication contract. It removes the obsolete COPILOT_SDK_TOKEN assumption already corrected in svg153/skills#53.

Authentication paths

  • prefer an explicitly configured COPILOT_GITHUB_TOKEN when present;
  • otherwise, because this repository is organization-owned, use the built-in GITHUB_TOKEN with copilot-requests: write when the organization has enabled the required Copilot Actions billing/policy;
  • do not commit any credential.

Evidence integrity

  • a scheduled run without supported auth reports that model evidence was skipped;
  • a manually requested run without supported auth fails rather than returning a misleading green result;
  • artifacts upload only when a model-backed evaluation was actually attempted;
  • the existing Waza suite, prompt, thresholds, and canonical skill remain unchanged.

Passing PR checks prove workflow/security/static correctness only. #35 counts behavioral evidence only after Waza/model steps execute and produce evidence.

@svg153
svg153 merged commit 70646d6 into main Sep 17, 2026
4 checks passed
@svg153
svg153 deleted the ci/current-copilot-waza-auth branch September 17, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: align trusted Waza auth with current Copilot SDK contract

1 participant