Add a Forgejo API surface to ward (port coily ops forgejo, with pagination) #117

New issue

Closed

opened 2026-06-17 21:24:22 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-17 21:24:22 +00:00

Owner

Why

coily is being retired, so coily ops forgejo (the current Forgejo API surface) needs a home on ward. The goose-triage tooling in agentic-os depends on it today (coily ops forgejo issue list / issue view), and so does ad-hoc issue filing.

Asked-for surface

Port the Forgejo API verbs onto ward as an audited passthrough (sibling to ward git / ward pkg), NOT repo-verb-gated:

ward forgejo issue list|view|create|edit|comment|label|close|reopen
ward forgejo label create (+ CRUD)
ward forgejo repo topics list, ward forgejo pr list

Fix the 50-cap while porting

coily ops forgejo issue list hard-caps --limit at 50 with no --page flag, so any repo with >50 open issues can only be triaged partially (the goose-triage percentile math is dishonest over a partial backlog). The ward port should support pagination and expose the authoritative open count (the per-repo /issues X-Total-Count header) so callers can page to exhaustion.

Context: goose-triage (agentic-os#237) and the coily-retirement doc update in agentic-os-kai/AGENTS.md.

## Why `coily` is being retired, so `coily ops forgejo` (the current Forgejo API surface) needs a home on ward. The goose-triage tooling in agentic-os depends on it today (`coily ops forgejo issue list` / `issue view`), and so does ad-hoc issue filing. ## Asked-for surface Port the Forgejo API verbs onto ward as an audited passthrough (sibling to `ward git` / `ward pkg`), NOT repo-verb-gated: - `ward forgejo issue list|view|create|edit|comment|label|close|reopen` - `ward forgejo label create` (+ CRUD) - `ward forgejo repo topics list`, `ward forgejo pr list` ## Fix the 50-cap while porting `coily ops forgejo issue list` hard-caps `--limit` at 50 with no `--page` flag, so any repo with >50 open issues can only be triaged partially (the goose-triage percentile math is dishonest over a partial backlog). The ward port should support pagination and expose the authoritative open count (the per-repo `/issues` `X-Total-Count` header) so callers can page to exhaustion. Context: goose-triage (agentic-os#237) and the coily-retirement doc update in agentic-os-kai/AGENTS.md.

coilysiren referenced this issue from a commit

2026-06-17 21:26:13 +00:00

docs(agents): cloud passthroughs migrate off coily ops onto ward

coilysiren referenced this issue from coilyco-flight-deck/agentic-os

2026-06-17 21:27:48 +00:00

Swap goose-triage fully onto ward (drop bare goose / coily / git) #239

coilysiren added the

headless

labels

2026-06-18 06:18:54 +00:00