fix: add actions:read permission to retro role#835
Conversation
The retro agent needs to access workflow run logs and download artifacts to analyze agent behavior, but was getting 403 Forbidden errors. The rolePermissions map was missing "actions": "read" for the retro role, despite the design spec explicitly stating the agent should have read access to workflow runs and artifacts. Fixes #834 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
fullsend review is working on this — view logs |
Site previewPreview: https://a8888937-site.fullsend-ai.workers.dev Commit: |
Review: #835Head SHA: 245dd4d SummaryThis is a correct, minimal fix that adds FindingsInfo
FooterOutcome: approve |
|
Closing in favor of #828 which now includes this change (cherry-picked). |
Summary
actions: readpermission to the retro role's installation tokenProblem
The retro agent was getting 403 Forbidden errors when attempting to:
gh run view --logThis prevented the agent from performing root cause analysis on agent runs, forcing it to hedge with statements like "cannot confirm definitively without log access (403 Forbidden)".
Evidence from run 25748112694:
Forbidden, preventing verification of whatfullsend post-reviewactually did"fullsend-reviewartifacts to inspectagent-result.json"Solution
The token mint service (
internal/mint/main.go) defines arolePermissionsmap that specifies which GitHub API permissions each agent role receives. Theretrorole was missing"actions": "read", which is required to access workflow runs and their artifacts.The design spec (
docs/superpowers/specs/2026-05-04-retro-agent-design.md:187) explicitly states:This one-line change adds the missing permission.
Deployment
After merge, the token mint Cloud Function needs to be redeployed with the updated
rolePermissionsmap. Future retro agent runs will then receive tokens withactions: readpermission.Test plan
make lint(passes)Fixes #834
🤖 Generated with Claude Code