feat(cli): watch repo-maintenance workflow after enable/disable repos

[ralphbean]

Summary

• After fullsend admin enable/disable repos updates config.yaml, the CLI now watches the repo-maintenance workflow run to completion and prints PR URLs from its ::notice:: annotations
• Adds GetWorkflowRunAnnotations to the forge interface (harvests check-run annotations via GitHub API)
• Simplifies e2e test polling loops — since the CLI waits for the workflow, the test no longer needs to poll for 2 minutes

Depends on #1612 (fix/e2e-lock-debug) — base branch set accordingly.

Test plan

• Unit tests for awaitRepoMaintenance (success, timeout, failure, context cancellation)
• Existing enable/disable unit tests pass (dispatch error injected to skip await)
• make go-test and make lint pass
• E2E test validates the full flow end-to-end

🤖 Generated with Claude Code

[github-actions]

Site preview

Preview: https://bb6c094c-site.fullsend-ai.workers.dev

Commit: 0362cc13a147acaf3ba962aa9f1bb0d4b00c614a

[fullsend-ai-review]

Review

Findings

Low

• [style] internal/cli/admin.go:2481 — Duplicate godoc comment for saveRepoConfig. The old single-line comment (// saveRepoConfig marshals and commits the updated config, then triggers the repo-maintenance workflow.) is retained alongside the new three-line comment. The resulting godoc block has the function name appearing twice.
  Remediation: Delete the old comment line so only the new multi-line comment remains.

• [correctness] internal/forge/github/github.go:1750 — GetWorkflowRunAnnotations does not paginate the jobs endpoint (/actions/runs/{id}/jobs) or the annotations endpoint (/check-runs/{id}/annotations). GitHub defaults to 30 items per page for jobs. For typical repo-maintenance runs this is unlikely to matter, but could silently drop data for workflows with many jobs. Consider adding ?per_page=100 to the jobs request.
  Remediation: Append ?per_page=100 to the jobs list URL. Document if pagination is intentionally omitted.

• [docs-currency] docs/guides/admin/installation.md:232 — The enable command description says "Triggers the repo-maintenance workflow to create enrollment PRs" but the CLI now also watches the workflow to completion and prints PR URLs from annotations. The same applies to the disable command description at line 263. Update both to reflect the new watching behavior.
  Remediation: Update bullet points to mention that the CLI watches the workflow run and reports enrollment/unenrollment PR URLs on completion.

Previous run

Review

Findings

Low

• [style] internal/cli/admin.go:2393 — Duplicate godoc comment for saveRepoConfig. The old single-line comment (// saveRepoConfig marshals and commits the updated config, then triggers the repo-maintenance workflow.) was retained as a context line, and the new multi-line comment was added below it. The resulting godoc block has the function name appearing twice, which is non-standard. Remove the old comment line.
  Remediation: Delete line 2393 (the old comment) so only the new three-line comment remains.

• [correctness] internal/forge/github/github.go:1751 — GetWorkflowRunAnnotations does not paginate either the jobs endpoint (/actions/runs/{id}/jobs) or the annotations endpoint (/check-runs/{id}/annotations). GitHub defaults to 30 items per page for jobs and 100 for annotations. For typical repo-maintenance runs this is unlikely to be an issue, but could silently drop data for workflows with many jobs. Consider adding ?per_page=100 to the jobs request at minimum, or documenting the pagination limitation.

[fullsend-ai-review]

[low] style

Duplicate godoc comment for saveRepoConfig. The old single-line comment was retained and the new multi-line comment was added below it, resulting in the function name appearing twice in the comment block.

Suggested fix: Delete the old comment line ("// saveRepoConfig marshals and commits the updated config, then triggers the repo-maintenance workflow.") so only the new three-line comment remains.

[fullsend-ai-review]

[low] correctness

GetWorkflowRunAnnotations does not paginate either the jobs endpoint or the annotations endpoint. GitHub defaults to 30 items per page for jobs and 100 for annotations. For typical repo-maintenance runs this is unlikely to be an issue, but could silently drop data for workflows with many jobs.

Suggested fix: Add ?per_page=100 to the jobs request, or document the pagination limitation in the method comment.

[fullsend-ai-review]

[low] correctness

GetWorkflowRunAnnotations does not paginate the jobs endpoint or the annotations endpoint. GitHub defaults to 30 items per page for jobs. Could silently drop data for workflows with many jobs.

Suggested fix: Append ?per_page=100 to the jobs list URL, or document that pagination is intentionally omitted.