#489 - warded carries GitHub issues end to end (dispatch, comments, PR) - GitHub as a first-class forge - coilyco-flight-deck/ward

coilyco-ops commented

2026-07-01 23:56:36 +00:00

Member

Why

Launch decision (2026-07-01 triage): GitHub is the public front door and all external copy goes GitHub-only (#461, #438). That is only honest if the core loop - warded owner/repo#N picking up an issue, posting comments, opening the PR - works against GitHub, not just Forgejo. Split out of #414 as its launch-gating slice.

Deliverable

warded accepts a GitHub issue ref/URL: clone + push via a GitHub token, preflight/NO-GO/outcome comments on the GitHub issue, PR opened on GitHub.
Auth via a documented user-suppliable token path (env / keychain), not the compiled-in SSM path (#441 / #453 alignment).
Docs: GitHub token setup + a worked example.

Done condition

A maintainer runs warded <gh-owner>/<repo>#<n> against a GitHub-hosted repo and gets the full loop; docs cover setup end to end.

Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

## Why Launch decision (2026-07-01 triage): GitHub is the public front door and all external copy goes GitHub-only (#461, #438). That is only honest if the core loop - `warded owner/repo#N` picking up an issue, posting comments, opening the PR - works against GitHub, not just Forgejo. Split out of #414 as its launch-gating slice. ## Deliverable - `warded` accepts a GitHub issue ref/URL: clone + push via a GitHub token, preflight/NO-GO/outcome comments on the GitHub issue, PR opened on GitHub. - Auth via a documented user-suppliable token path (env / keychain), not the compiled-in SSM path (#441 / #453 alignment). - Docs: GitHub token setup + a worked example. ## Done condition A maintainer runs `warded <gh-owner>/<repo>#<n>` against a GitHub-hosted repo and gets the full loop; docs cover setup end to end. --- Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilyco-ops added this to the ward launch milestone

2026-07-01 23:56:36 +00:00

coilyco-ops added the

headless

P1

labels

2026-07-01 23:56:36 +00:00

coilyco-ops referenced this issue

2026-07-01 23:57:00 +00:00

add github equivalents for all forgejo integrations / functionality #414

coilyco-ops referenced this issue

2026-07-01 23:58:15 +00:00

README opening buries what ward actually does under four paragraphs of naming lore and unexplained bare issue refs #444

coilyco-ops referenced this issue

2026-07-01 23:58:18 +00:00

README's first sentence conflates dev-verb wrapping (forge-agnostic) with agent-carries-a-Forgejo-issue (Forgejo-only), losing GitHub-only adopters of the half that would actually work for them #461

coilyco-ops referenced this issue

2026-07-02 00:01:42 +00:00

meta: jul 1st evening sprint - launch burndown session 1 #492

coilyco-ops referenced this issue

2026-07-02 00:20:44 +00:00

Unify agent.go issue-ref parser with cli-guard dispatch.parseIssueRef (export it) #124

coilyco-ops referenced this issue

2026-07-02 00:22:37 +00:00

Warded agents aren't meaningfully conservative about github API rate limits #466

coilyco-ops commented

2026-07-02 02:50:09 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-489 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T02:50:07Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-489` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T02:50:07Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 02:52:20 +00:00

docs(readme): tell GitHub-only readers the verb gate needs no forge (closes #461)

coilysiren referenced this issue

2026-07-02 02:52:38 +00:00

README's first sentence conflates dev-verb wrapping (forge-agnostic) with agent-carries-a-Forgejo-issue (Forgejo-only), losing GitHub-only adopters of the half that would actually work for them #461

coilyco-ops commented

2026-07-02 04:30:39 +00:00

Author

Member

🔒 Reserved by ward agent --driver codex — container engineer-codex-ward-489 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T04:30:38Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Codex, via ward agent

🔒 Reserved by `ward agent --driver codex` — container `engineer-codex-ward-489` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T04:30:38Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Codex, via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 04:34:51 +00:00

feat(agent): accept GitHub issue refs

coilysiren closed this issue

2026-07-02 04:34:52 +00:00

coilysiren commented

2026-07-02 04:35:07 +00:00

Owner

WARD-OUTCOME: done - warded now accepts GitHub issue refs and documents the GitHub token path
The ref parsing change was straightforward, but the repo-doc size caps fought harder than the code. I split the auth guidance into two short docs to satisfy the hooks. Confidence is decent on the parser and docs; the remaining gap is that this lands the ref/credential side, not a full GitHub API client.

WARD-OUTCOME: done - warded now accepts GitHub issue refs and documents the GitHub token path The ref parsing change was straightforward, but the repo-doc size caps fought harder than the code. I split the auth guidance into two short docs to satisfy the hooks. Confidence is decent on the parser and docs; the remaining gap is that this lands the ref/credential side, not a full GitHub API client.

coilysiren referenced this issue

2026-07-02 07:10:55 +00:00

meta: jul 1st evening sprint - launch burndown session 1 #492

coilysiren referenced this issue

2026-07-02 07:33:03 +00:00

Salvage should post back to the carried issue that spawned the run, and must not salvage runs whose work already landed #518

coilysiren referenced this issue

2026-07-02 07:38:07 +00:00

Recover the full gh-backed GitHub issue client abandoned on ward-salvage/ward-b4d43076 (the work #489 shipped only partially) #520

coilysiren referenced this issue from a commit

2026-07-02 07:48:52 +00:00

feat(agent): recover the gh-backed GitHub issue-forge client (ward#489 completion)