Remove legacy cli-guard dispatch subsystem if unused

coilyco-ops commented

2026-07-09 02:25:14 +00:00

Member

Remove the legacy cli-guard dispatch subsystem from the release surface:

Confirm whether any current repo still imports or shells into cli/dispatch.
If unused, remove the dispatch package, examples, docs, tests, and command-tree wiring.
Remove dispatch-only GitHub cache/rate-limit dependencies when no other consumers remain.
Keep cli-guard's core policy, audit, verb, execverb, sandbox, and specverb surfaces intact.

Rationale: ward now owns agent dispatch. cli-guard dispatch appears to be the older issue-runner and should not ship unless a current consumer still depends on it.

Remove the legacy cli-guard dispatch subsystem from the release surface: * Confirm whether any current repo still imports or shells into `cli/dispatch`. * If unused, remove the dispatch package, examples, docs, tests, and command-tree wiring. * Remove dispatch-only GitHub cache/rate-limit dependencies when no other consumers remain. * Keep cli-guard's core policy, audit, verb, execverb, sandbox, and specverb surfaces intact. Rationale: ward now owns agent dispatch. cli-guard dispatch appears to be the older issue-runner and should not ship unless a current consumer still depends on it.

coilyco-ops commented

2026-07-09 02:27:32 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-cli-guard-203 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T02:27:30Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/cli-guard#203 · branch issue-203 · harness codex · workflow pr
Run: engineer-codex-cli-guard-203 · ward v0.470.0 · dispatched 2026-07-09T02:27:30Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-cli-guard-203` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T02:27:30Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/cli-guard#203` · branch `issue-203` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-cli-guard-203` · ward `v0.470.0` · dispatched `2026-07-09T02:27:30Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 02:33:08 +00:00

Remove legacy cli-guard dispatch subsystem #207

coilyco-ops commented

2026-07-09 02:33:20 +00:00

Author

Member

WARD-OUTCOME: done - removed the legacy cli-guard dispatch subsystem from the release surface.
Review gate: skipped because --skip-preflight / --no-preflight also skips review.
The cut was straightforward after confirming nothing else imported cli/dispatch. The only friction was the generated godoc snapshot and example treebuilder cleanup, both resolved cleanly. Confidence is high, and I do not see a follow-up beyond watching for any downstream docs that still mention dispatch.

WARD-OUTCOME: done - removed the legacy cli-guard dispatch subsystem from the release surface. Review gate: skipped because --skip-preflight / --no-preflight also skips review. The cut was straightforward after confirming nothing else imported cli/dispatch. The only friction was the generated godoc snapshot and example treebuilder cleanup, both resolved cleanly. Confidence is high, and I do not see a follow-up beyond watching for any downstream docs that still mention dispatch.

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 02:33:30 +00:00

ward salvage: ward-salvage/cli-guard-7f69a8f5 #208

coilyco-ops commented

2026-07-09 02:33:32 +00:00

Author

Member

⚠️ Reopened: this run's work did not land on `main`

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #203 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/cli-guard
Salvage branch: ward-salvage/cli-guard-7f69a8f5
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: run workflow does not land on main (--workflow pr/patch-only)
Container uptime at reap: 5m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              05e8b788468f
origin/main:       a90604c56b17
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  5m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/cli-guard.git ward-salvage/cli-guard-7f69a8f5
git checkout -b ward-salvage/cli-guard-7f69a8f5 FETCH_HEAD

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #203 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/cli-guard` - **Salvage branch:** `ward-salvage/cli-guard-7f69a8f5` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 5m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: 05e8b788468f origin/main: a90604c56b17 ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 5m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/cli-guard.git ward-salvage/cli-guard-7f69a8f5 git checkout -b ward-salvage/cli-guard-7f69a8f5 FETCH_HEAD ```  — Codex, via `ward agent`

coilyco-ops added the

P3

headless

labels

2026-07-10 08:59:46 +00:00

coilyco-ops commented

2026-07-10 16:54:14 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-cli-guard-203 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T16:54:13Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/cli-guard#203 · branch issue-203 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-cli-guard-203 · ward v0.584.0 · dispatched 2026-07-10T16:54:13Z
Comment thread: 2 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T02:33:20Z), @coilyco-ops (2026-07-09T02:33:32Z)
- stripped: @coilyco-ops (2026-07-09T02:27:32Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-cli-guard-203` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T16:54:13Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/cli-guard#203` · branch `issue-203` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-cli-guard-203` · ward `v0.584.0` · dispatched `2026-07-10T16:54:13Z` - **Comment thread:** 2 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T02:33:20Z), @coilyco-ops (2026-07-09T02:33:32Z) - stripped: @coilyco-ops (2026-07-09T02:27:32Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 17:00:13 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: skipped because review gate skipped by ~/.ward/config.yaml default summary: removed the legacy cli/dispatch subsystem and refreshed the branch onto current main felt: straightforward once the stale PR was merged onto current main and the docs snapshot was regenerated confidence: high surprises: main had drifted, but the dispatch removal still held cleanly follow-ups: merge PR #207

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped because review gate skipped by ~/.ward/config.yaml default summary: removed the legacy cli/dispatch subsystem and refreshed the branch onto current main felt: straightforward once the stale PR was merged onto current main and the docs snapshot was regenerated confidence: high surprises: main had drifted, but the dispatch removal still held cleanly follow-ups: merge PR #207  </details>

coilyco-ops closed this issue

2026-07-10 22:12:56 +00:00

Rows
Columns

Remove legacy cli-guard dispatch subsystem if unused #203

⚠️ Reopened: this run's work did not land on main

Reap diagnostics

Recover

⚠️ Reopened: this run's work did not land on `main`