Adopt the cli-guard/dispatch package #6

New issue

Closed

opened 2026-05-23 20:53:17 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-23 20:53:17 +00:00

Owner

Originally filed by @coilysiren on 2026-05-21T12:25:27Z - https://github.com/coilysiren/agent-guard/issues/26

Goal - Wire the reusable cli-guard/dispatch package (coilysiren/cli-guard#86, landed) into agent-guard's command tree, so agent-guard consumers get dispatch headless / dispatch interactive / dispatch reap.

Wire - build a dispatch.Config from agent-guard's runner + audit writer and hang dispatch.New(...).Command() off agent-guard's urfave/cli tree, the same way agent-guard wires shell, verb, audit today.

Config.Wrap adapts agent-guard's verb pipeline.
Config.AllowedOwner / RepoPath / WorktreeRoot / LogRoot reflect agent-guard's host policy and workspace layout (these are the host-specific seams the package refuses to hard-code).
Config.BinaryName = "agent-guard".
Config.Notify optional - wire ntfy / a done-banner if desired.

Pin - bump the cli-guard pin to the commit that landed #86.

Surfaced from coilysiren/cli-guard#86 sequencing: cli-guard package first, then coily switches to thin wiring, then agent-guard adopts. Each repo is its own commit closing its own issue.

_Originally filed by @coilysiren on 2026-05-21T12:25:27Z - [https://github.com/coilysiren/agent-guard/issues/26](https://github.com/coilysiren/agent-guard/issues/26)_ **Goal** - Wire the reusable `cli-guard/dispatch` package (coilysiren/cli-guard#86, landed) into agent-guard's command tree, so agent-guard consumers get `dispatch headless` / `dispatch interactive` / `dispatch reap`. **Wire** - build a `dispatch.Config` from agent-guard's runner + audit writer and hang `dispatch.New(...).Command()` off agent-guard's urfave/cli tree, the same way agent-guard wires `shell`, `verb`, `audit` today. - `Config.Wrap` adapts agent-guard's verb pipeline. - `Config.AllowedOwner` / `RepoPath` / `WorktreeRoot` / `LogRoot` reflect agent-guard's host policy and workspace layout (these are the host-specific seams the package refuses to hard-code). - `Config.BinaryName` = `"agent-guard"`. - `Config.Notify` optional - wire ntfy / a done-banner if desired. **Pin** - bump the cli-guard pin to the commit that landed #86. Surfaced from coilysiren/cli-guard#86 sequencing: cli-guard package first, then coily switches to thin wiring, then agent-guard adopts. Each repo is its own commit closing its own issue.

coilysiren added the

label

2026-05-31 01:54:04 +00:00

coilysiren closed this issue

2026-06-03 23:48:12 +00:00

coilysiren referenced this issue

2026-06-15 15:31:56 +00:00

Epic: coily -> ward -> ward-kdl consolidation (umbrella) #91

coilysiren referenced this issue

2026-06-18 07:43:25 +00:00

Re-express agent_upgrade.go Forgejo release check as ward-kdl forgejo guardfile (retire its bespoke HTTP client) #172

coilysiren referenced this issue