sweep: route hardcoded GitHub mentions for Kai's repos through Forgejo #84

New issue

Open

opened 2026-05-26 03:05:11 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-26 03:05:11 +00:00

Owner

Problem

coily was built when Kai's tracker was GitHub. Her work now routes through Forgejo (forgejo.coilysiren.me). Pieces of coily still assume GitHub: dispatch resolves issues via gh api only, in-code messages and AGENTS.md prose link to github.com/coilysiren/<repo>/issues/N, recovery hints reference GitHub URLs, doc cross-refs land on GitHub even when the canonical issue is on Forgejo. 10 of the 25 cleanup-issue repos in the agentic-os v0.2.8 fan-out were undispatchable for this reason.

Goal

Sweep coily for everywhere "GitHub" is hardcoded against a coilysiren/* tracker, and route through Forgejo (or both, where the GitHub flow is intentionally still in scope - Actions / CI status / external-contrib docs).

Scope of the sweep

cmd/coily/dispatch.go: wire a forgejo-first IssueFetcher via the new cli-guard hook (cli-guard#12). Falls back to gh on 404. Updates seedPrompt and dispatchFooter to reference whichever tracker resolved the ref.
Cross-reference URLs in checked-in prose. README.md, AGENTS.md, doc files, code comments referencing https://github.com/coilysiren/<personal-repo>/issues/N should point at Forgejo when the canonical tracker is Forgejo. Externally-facing tools (agent-guard, cli-*) stay on GitHub.
User-visible messages and denial reasons that suggest gh issue view ... / https://github.com/.../issues/N for Kai's personal repos. Route to coily ops forgejo (or the Forgejo URL) instead.
coily ops gh itself stays unchanged - it's a GitHub passthrough by definition. Don't touch.

Keep as-is (intentionally GitHub)

All gh_actions_* / ci / passthroughs / playwright Actions surface.
coily ops gh wrapper and its helptext.
Private vulnerability reporting in SECURITY.md (GitHub-specific feature).
External-contributor pointers in CONTRIBUTING.md to agent-guard / GitHub.
Go import paths under github.com/coilysiren/... (those are go-module paths, not trackers).
Release pipeline, brew tap install instructions, scoop-bucket URLs.

Trigger

Surfaced during agentic-os v0.2.8 cleanup fan-out (forgejo issues filed against agentic-os-kai, coilysiren, factorio-mods, infrastructure, luca, message-ops, personal-dashboard, sirens-discord-ops, website weren't dispatchable).

Depends on

cli-guard#12 (Forgejo-aware IssueFetcher hook).

**Problem** coily was built when Kai's tracker was GitHub. Her work now routes through Forgejo (`forgejo.coilysiren.me`). Pieces of coily still assume GitHub: dispatch resolves issues via `gh api` only, in-code messages and AGENTS.md prose link to `github.com/coilysiren/<repo>/issues/N`, recovery hints reference GitHub URLs, doc cross-refs land on GitHub even when the canonical issue is on Forgejo. 10 of the 25 cleanup-issue repos in the agentic-os v0.2.8 fan-out were undispatchable for this reason. **Goal** Sweep coily for everywhere "GitHub" is hardcoded against a coilysiren/* tracker, and route through Forgejo (or both, where the GitHub flow is intentionally still in scope - Actions / CI status / external-contrib docs). **Scope of the sweep** 1. `cmd/coily/dispatch.go`: wire a forgejo-first `IssueFetcher` via the new cli-guard hook (cli-guard#12). Falls back to gh on 404. Updates `seedPrompt` and `dispatchFooter` to reference whichever tracker resolved the ref. 2. Cross-reference URLs in checked-in prose. `README.md`, `AGENTS.md`, doc files, code comments referencing `https://github.com/coilysiren/<personal-repo>/issues/N` should point at Forgejo when the canonical tracker is Forgejo. Externally-facing tools (agent-guard, cli-*) stay on GitHub. 3. User-visible messages and denial reasons that suggest `gh issue view ...` / `https://github.com/.../issues/N` for *Kai's* personal repos. Route to `coily ops forgejo` (or the Forgejo URL) instead. 4. `coily ops gh` itself stays unchanged - it's a GitHub passthrough by definition. Don't touch. **Keep as-is (intentionally GitHub)** - All `gh_actions_*` / `ci` / passthroughs / playwright Actions surface. - `coily ops gh` wrapper and its helptext. - Private vulnerability reporting in SECURITY.md (GitHub-specific feature). - External-contributor pointers in CONTRIBUTING.md to agent-guard / GitHub. - Go import paths under `github.com/coilysiren/...` (those are go-module paths, not trackers). - Release pipeline, brew tap install instructions, scoop-bucket URLs. **Trigger** Surfaced during agentic-os v0.2.8 cleanup fan-out (forgejo issues filed against `agentic-os-kai`, `coilysiren`, `factorio-mods`, `infrastructure`, `luca`, `message-ops`, `personal-dashboard`, `sirens-discord-ops`, `website` weren't dispatchable). **Depends on** cli-guard#12 (Forgejo-aware IssueFetcher hook).

coilysiren changed title from ~~dispatch: wire forgejo-first IssueFetcher (cli-guard default stays gh)~~ to sweep: route hardcoded GitHub mentions for Kai's repos through Forgejo

2026-05-26 03:06:16 +00:00

coilysiren added the

label

2026-05-31 01:52:41 +00:00

coilysiren added

and removed

labels

2026-05-31 06:59:45 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-bridge/coily#84

No description provided.

Rows
Columns