coilyco-flight-deck/ward-mcp
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Run ward-mcp CI in aos dev-base #13

New issue
Closed
opened 2026-07-09 03:52:01 +00:00 by coilyco-ops · 5 comments
coilyco-ops commented 2026-07-09 03:52:01 +00:00
Member
Copy link

The dev-base scan found .forgejo/workflows/ci.yml using actions/setup-go and downloading Docker CLI from download.docker.com. The pinned aos dev-base image already ships Go and Docker CLI.

Acceptance criteria:

  • Run the gate and publish jobs in the pinned aos dev-base image.
  • Remove actions/setup-go and Docker CLI tarball install when dev-base supplies those tools.
  • Preserve GOPRIVATE behavior for the private cli-guard module.
  • Keep Docker host probing and image push behavior unchanged.
The dev-base scan found `.forgejo/workflows/ci.yml` using `actions/setup-go` and downloading Docker CLI from `download.docker.com`. The pinned aos dev-base image already ships Go and Docker CLI. Acceptance criteria: * Run the gate and publish jobs in the pinned aos dev-base image. * Remove `actions/setup-go` and Docker CLI tarball install when dev-base supplies those tools. * Preserve GOPRIVATE behavior for the private cli-guard module. * Keep Docker host probing and image push behavior unchanged.
coilyco-ops commented 2026-07-09 03:55:58 +00:00
Author
Member
Copy link

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-mcp-13 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T03:55:56Z). 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/ward-mcp#13 · branch issue-13 · harness codex · workflow pr
  • Run: engineer-codex-ward-mcp-13 · ward v0.470.0 · dispatched 2026-07-09T03:55:56Z
  • 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-ward-mcp-13` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T03:55:56Z). 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/ward-mcp#13` · branch `issue-13` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-ward-mcp-13` · ward `v0.470.0` · dispatched `2026-07-09T03:55:56Z` - **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 03:59:45 +00:00
Author
Member
Copy link

WARD-OUTCOME: done - CI now runs gate and publish in the pinned aos dev-base image.
Review gate skipped because --skip-preflight / --no-preflight also skips review.
The edit was straightforward once the container pin was identified, and the Docker host probing stayed intact. Confidence is high. The only rough edge was keeping the docs aligned with the workflow change.

WARD-OUTCOME: done - CI now runs gate and publish in the pinned aos dev-base image. Review gate skipped because --skip-preflight / --no-preflight also skips review. The edit was straightforward once the container pin was identified, and the Docker host probing stayed intact. Confidence is high. The only rough edge was keeping the docs aligned with the workflow change.
coilyco-ops commented 2026-07-09 04:00:04 +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 #13 never reached main). Recover from the salvage branch below.

  • Repo: coilyco-flight-deck/ward-mcp
  • Salvage branch: ward-salvage/ward-mcp-558b4977
  • 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: 3m (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:              5c4d11382dba
origin/main:       c0700f1995ee
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:  3m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp.git ward-salvage/ward-mcp-558b4977
git checkout -b ward-salvage/ward-mcp-558b4977 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 #13 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/ward-mcp` - **Salvage branch:** `ward-salvage/ward-mcp-558b4977` - **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:** 3m (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: 5c4d11382dba origin/main: c0700f1995ee 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: 3m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp.git ward-salvage/ward-mcp-558b4977 git checkout -b ward-salvage/ward-mcp-558b4977 FETCH_HEAD ``` <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 22:40:25 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-mcp-13 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T22:40:23Z). 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/ward-mcp#13 · branch issue-13 · harness codex · workflow direct-main
  • Run: engineer-codex-ward-mcp-13 · ward v0.540.0 · dispatched 2026-07-09T22:40:23Z
  • 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.540.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-mcp-13` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T22:40:23Z). 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/ward-mcp#13` · branch `issue-13` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-ward-mcp-13` · ward `v0.540.0` · dispatched `2026-07-09T22:40:23Z` - **Comment thread:** 2 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T03:59:45Z), @coilyco-ops (2026-07-09T04:00:04Z) - stripped: @coilyco-ops (2026-07-09T03:55:58Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.540.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops referenced this issue from a commit 2026-07-09 22:42:51 +00:00
chore: close issue 13
coilyco-ops commented 2026-07-09 22:43:19 +00:00
Author
Member
Copy link

WARD-OUTCOME: done

details workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default Recovered the prior dev-base workflow change from the salvage branch, kept GOPRIVATE intact, and landed the minimal closure commit on `main`. Confidence: high. Surprise: the salvage branch already contained the intended workflow edit, so the only live fix was closure hygiene. Follow-up: none.
WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default Recovered the prior dev-base workflow change from the salvage branch, kept GOPRIVATE intact, and landed the minimal closure commit on `main`. Confidence: high. Surprise: the salvage branch already contained the intended workflow edit, so the only live fix was closure hygiene. Follow-up: none. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-18
issue-21
issue-20
issue-13
ward-salvage/ward-mcp-558b4977
No results found.
Labels
Clear labels
  
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
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/ward-mcp#13
No description provided.