Add coily ops forgejo REST wrapper for issue + comment creation #14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Default TODO destination per AGENTS.md is a Forgejo issue on
coilysiren/agentic-os-kai, but nocoilywrapper exists for filing one. Agents that need to file an issue today fall back to rawcurlagainstforgejo.coilysiren.me/api/v1/..., manually shaped json bodies, and a hand-fetched/forgejo/api-tokenfrom SSM. Every agent reinvents the same curl. Friction taxes the "file the follow-up, then proceed" discipline in AGENTS.md.Today's session is a concrete instance: filed coilysiren/agentic-os-kai#260 with a curl one-liner after first failing to find the token because I searched only under
/coilysiren/and missed the top-level/forgejo/api-token.Proposal
Add a
coily ops forgejoumbrella as a REST wrapper, same shape as the existingcoily ops trello,coily ops discord,coily ops sentry,coily ops modioumbrellas. Auto-resolves the token from/forgejo/api-tokenin SSM, signs the request, passes argv through to the issue/PR endpoints, audit-logs each call.Minimum useful verbs:
coily ops forgejo issue create --repo <owner/repo> --title <t> --body-file <path>-> POST/repos/{owner}/{repo}/issuescoily ops forgejo issue comment --repo <owner/repo> --number <N> --body-file <path>-> POST/repos/{owner}/{repo}/issues/{N}/commentscoily ops forgejo issue list --repo <owner/repo> [--state open|closed|all]-> GET/repos/{owner}/{repo}/issuescoily ops forgejo issue close --repo <owner/repo> --number <N>-> PATCH/repos/{owner}/{repo}/issues/{N}{state: closed}Larger surface (pulls, releases, repos) can land later via the same openapi-to-coily generator if Forgejo publishes a usable spec.
Routing
This issue lives in
coilysiren/agent-guardbecause the new top-levelcoily ops forgejoverb needs an entry incoilyRoutes. The implementation of the REST wrapper itself lives in thecoilysiren/coilyrepo. Per AGENTS.md, the framing in any user-facing recovery hint stays "coily" not "agent-guard."Out of scope
coily forgejo adminandcoily forgejo doctor; this issue is about the REST wrapper, not extending the CLI passthrough.coilysiren/*per AGENTS.md.Merged into #13 in the 2026-05-29 backlog burn-down. exact duplicate of forgejo REST wrapper issue 13 Reopen if it should stand alone.