Collapse the `ward agent` dispatch fork onto cli-guard dispatch.Dispatcher #267

New issue

Closed

opened 2026-06-24 07:46:08 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-06-24 07:46:08 +00:00

Member

agent*.go (agent.go, agent_route.go, agent_reply.go, agent_tab.go, agent_ask.go, agent_reserve.go) is a container-shaped fork of cli-guard's dispatch.Dispatcher, which already abstracts headless/interactive/detached spawn, issue resolve, owner-trust, and reap. Reusable pieces ward re-implemented: pre-flight verdict parsing, detached-spawn health-window, the two-sided reservation lock, salvage-reap, the owner-trust gate, and an issue-ref parser that duplicates dispatch.ParseIssueRef (ward's own comment flags it).

Drive dispatch.Dispatcher with container seams instead of re-hosting it; keep only the seeded-prompt prose, harness selection, and Forgejo comment bodies in ward.
Depends on the cli-guard issue to make dispatch.Dispatcher pluggable (container backend + pre-flight verdict stage), landed + released first.
High risk: this IS the live dispatch path.

From the 2026-06-24 ward/cli-guard boundary audit. See ward docs/architecture.md (the 3-layer model: cli-guard engine / ward-kdl generator / ward product). Related: ward#194, ward#200, cli-guard#139.

`agent*.go` (`agent.go`, `agent_route.go`, `agent_reply.go`, `agent_tab.go`, `agent_ask.go`, `agent_reserve.go`) is a container-shaped **fork** of cli-guard's `dispatch.Dispatcher`, which already abstracts headless/interactive/detached spawn, issue resolve, owner-trust, and reap. Reusable pieces ward re-implemented: pre-flight verdict parsing, detached-spawn health-window, the two-sided reservation lock, salvage-reap, the owner-trust gate, and an issue-ref parser that **duplicates** `dispatch.ParseIssueRef` (ward's own comment flags it). - Drive `dispatch.Dispatcher` with container seams instead of re-hosting it; keep only the seeded-prompt prose, harness selection, and Forgejo comment bodies in ward. - **Depends on** the cli-guard issue to make `dispatch.Dispatcher` pluggable (container backend + pre-flight verdict stage), landed + released first. - High risk: this IS the live dispatch path. From the 2026-06-24 ward/cli-guard boundary audit. See ward docs/architecture.md (the 3-layer model: cli-guard engine / ward-kdl generator / ward product). Related: ward#194, ward#200, cli-guard#139.

coilyco-ops added the

interactive

labels

2026-06-24 07:46:08 +00:00

coilyco-ops referenced this issue

2026-06-24 07:46:36 +00:00

[tracking] Slim ward to the product layer (migrate engine/policy code to cli-guard) #265

coilyco-ops commented

2026-06-24 17:30:24 +00:00

Author

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P2 - Collapse the dispatch fork onto cli-guard, committed migration, depends on a cli-guard change.
interactive - High-risk live dispatch path with a cli-guard dependency, agent works it then pauses at the verify.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P2** - Collapse the dispatch fork onto cli-guard, committed migration, depends on a cli-guard change. - **interactive** - High-risk live dispatch path with a cli-guard dependency, agent works it then pauses at the verify.