coilyco-flight-deck/cli-guard
2
0
Fork 0
Code Issues 8 Pull requests Projects Releases 96 Packages Wiki Activity Actions

Remove cli-guard mcporter integration from release scope #204

New issue
Closed
opened 2026-07-09 02:25:14 +00:00 by coilyco-ops · 7 comments
coilyco-ops commented 2026-07-09 02:25:14 +00:00
Member
Copy link

Remove cli-guard's mcporter integration from the release surface:

  • Remove mcp/mcporter and its tests.
  • Remove passthrough pre-exec mcporter resolver wiring.
  • Remove docs/examples that advertise mcporter support.
  • Keep ordinary passthrough and core guard behavior intact.

Rationale: mcporter is optional local integration glue, not core cli-guard release behavior.

Remove cli-guard's mcporter integration from the release surface: * Remove `mcp/mcporter` and its tests. * Remove passthrough pre-exec mcporter resolver wiring. * Remove docs/examples that advertise mcporter support. * Keep ordinary passthrough and core guard behavior intact. Rationale: mcporter is optional local integration glue, not core cli-guard release behavior.
coilyco-ops commented 2026-07-09 02:27:46 +00:00
Author
Member
Copy link

🔒 Reserved by ward agent --harness codex — container engineer-codex-cli-guard-204 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T02:27:44Z). 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#204 · branch issue-204 · harness codex · workflow pr
  • Run: engineer-codex-cli-guard-204 · ward v0.470.0 · dispatched 2026-07-09T02:27:44Z
  • 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

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-cli-guard-204` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T02:27:44Z). 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#204` · branch `issue-204` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-cli-guard-204` · ward `v0.470.0` · dispatched `2026-07-09T02:27:44Z` - **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> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 02:32:31 +00:00
Author
Member
Copy link

WARD-OUTCOME: done - removed the mcporter package and passthrough secret-resolver wiring from release surface
Review gate skipped because --skip-preflight / --no-preflight also skips review.
The change was mostly mechanical, but the stale GoDoc snapshot was the only piece that fought back. Confidence is high after the repo tests and pre-commit gate both passed.

WARD-OUTCOME: done - removed the mcporter package and passthrough secret-resolver wiring from release surface Review gate skipped because --skip-preflight / --no-preflight also skips review. The change was mostly mechanical, but the stale GoDoc snapshot was the only piece that fought back. Confidence is high after the repo tests and pre-commit gate both passed.
coilyco-ops commented 2026-07-09 02:32:41 +00:00
Author
Member
Copy link

⚠️ 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 #204 never reached main). Recover from the salvage branch below.

  • Repo: coilyco-flight-deck/cli-guard
  • Salvage branch: ward-salvage/cli-guard-9b23a268
  • 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: 4m (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:              18b20c23fd52
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:  4m (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-9b23a268
git checkout -b ward-salvage/cli-guard-9b23a268 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 #204 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/cli-guard` - **Salvage branch:** `ward-salvage/cli-guard-9b23a268` - **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:** 4m (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: 18b20c23fd52 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: 4m (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-9b23a268 git checkout -b ward-salvage/cli-guard-9b23a268 FETCH_HEAD ``` <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-10 16:47:36 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T16:47:35Z). 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#204 · branch issue-204 · harness codex · workflow pull-requests-and-merge
  • Run: engineer-codex-cli-guard-204 · ward v0.584.0 · dispatched 2026-07-10T16:47:35Z
  • Comment thread: 2 included in the pre-flight read, 1 stripped (ward's own automated comments).

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

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-cli-guard-204` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T16:47:35Z). 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#204` · branch `issue-204` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-cli-guard-204` · ward `v0.584.0` · dispatched `2026-07-10T16:47:35Z` - **Comment thread:** 2 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T02:32:31Z), @coilyco-ops (2026-07-09T02:32:41Z) - stripped: @coilyco-ops (2026-07-09T02:27:46Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-10 16:49:53 +00:00
Author
Member
Copy link

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: review gate skipped because review gate skipped by ~/.ward/config.yaml default

The mcporter release-surface removal stayed intact. The work felt mechanical after the existing patch, and the only surprise was the PR body metadata needing the workflow marker. Confidence is high. Follow-up: merge PR #205.

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped because review gate skipped by ~/.ward/config.yaml default The mcporter release-surface removal stayed intact. The work felt mechanical after the existing patch, and the only surprise was the PR body metadata needing the workflow marker. Confidence is high. Follow-up: merge PR #205. </details>
coilyco-ops commented 2026-07-10 22:32:03 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-cli-guard-204 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-10T22:32:03Z). 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#204 · branch issue-204 · harness codex · workflow pull-requests-and-merge
  • Run: engineer-codex-cli-guard-204 · ward v0.605.0 · dispatched 2026-07-10T22:32:03Z
  • Comment thread: 3 included in the pre-flight read, 2 stripped (ward's own automated comments).

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

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-cli-guard-204` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T22:32:03Z). 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#204` · branch `issue-204` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-cli-guard-204` · ward `v0.605.0` · dispatched `2026-07-10T22:32:03Z` - **Comment thread:** 3 included in the pre-flight read, 2 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T02:32:31Z), @coilyco-ops (2026-07-09T02:32:41Z), @coilyco-ops (2026-07-10T16:49:53Z) - stripped: @coilyco-ops (2026-07-09T02:27:46Z), @coilyco-ops (2026-07-10T16:47:36Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-10 22:38:25 +00:00
Author
Member
Copy link

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

The mcporter release-surface cleanup stayed mechanical once the branch was refreshed. The only surprise was the base-branch drift, and that was handled by merging main into issue-204 before the final push. Confidence is high. Follow-up: none.

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA The mcporter release-surface cleanup stayed mechanical once the branch was refreshed. The only surprise was the base-branch drift, and that was handled by merging `main` into `issue-204` before the final push. Confidence is high. Follow-up: none. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release
issue-229
issue-185-sandbox-leakfree
issue-214
issue-225
fix/refusal-names-the-actual-gate
issue-204
issue-219
issue-216
issue-203
issue-217
ward-salvage/cli-guard-a8e13cf8
ward-salvage/cli-guard-7f69a8f5
ward-salvage/cli-guard-9b23a268
issue-124
ward-salvage/cli-guard-e8175b16
v0.101.0
draft-16b0b2affc80b689710f3a470137449f4d898a6b
v0.100.0
v0.99.0
v0.98.0
v0.97.0
v0.96.0
v0.95.0
v0.94.0
v0.93.0
v0.92.0
v0.91.0
v0.90.0
v0.89.0
v0.88.0
v0.87.0
v0.86.0
v0.85.0
v0.84.0
v0.83.0
v0.82.0
v0.81.0
v0.80.0
v0.79.0
v0.78.0
v0.77.0
v0.76.0
v0.75.0
v0.74.0
v0.73.0
v0.72.0
v0.71.0
v0.70.0
v0.69.0
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.0
v0.61.0
v0.60.0
v0.59.0
v0.58.0
v0.57.0
v0.56.0
v0.55.0
v0.54.0
v0.53.0
v0.52.0
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.0
v0.38.0
v0.37.0
v0.36.0
v0.35.0
v0.34.0
v0.33.0
v0.32.0
v0.31.0
v0.30.0
v0.29.0
v0.28.0
v0.27.0
v0.26.0
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.0
v0.18.0
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.4.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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-flight-deck/cli-guard#204
No description provided.