Title: Fix advisor/freeform container launch using wrong dev-base image… #1084

New issue

Closed

opened 2026-07-10 21:54:15 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 21:54:15 +00:00

Member

Title: Fix advisor/freeform container launch using wrong dev-base image or entrypoint

Repro from a read-only director surface on 2026-07-10:

$ warded advisor coilyco-bridge/agentic-os-kai --instructions-file /scratch/cross-org-backlog-scout-brief.md
latest: Pulling from coilyco-flight-deck/agentic-os
Status: Image is up to date for forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest
ward agent advisor --harness codex: answering with codex about coilyco-flight-deck/agentic-os in a fresh container...
docker: Error response from daemon: ... exec: "/opt/ward/entrypoint.sh": stat /opt/ward/entrypoint.sh: no such file or directory
exit status 127

Observed problems:

The advisor/freeform path pulled forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest.
The launched container expected /opt/ward/entrypoint.sh.
The current aos dev-base tests and Dockerfile contract point at /opt/agentic-os/ward-shell-entrypoint.sh, not /opt/ward/entrypoint.sh.
The command also reported it was answering about coilyco-flight-deck/agentic-os even though the requested target was coilyco-bridge/agentic-os-kai.

Task:

Fix the ward advisor/freeform container path so it uses the correct dev-base image and entrypoint contract.
Preserve the explicit target repo when the caller passes owner/repo --instructions-file.
Add regression coverage for advisor/freeform launch planning that asserts the image, entrypoint, and target repo.
Verify the fixed path can launch far enough to run the advisor command or print the resolved plan without the missing-entrypoint failure.

Related context:

agentic-os owns the image and entrypoint contract.
This issue is about ward selecting or launching that contract incorrectly.

Filed by ward agent engineer --harness codex.

— Codex, via ward agent

Title: Fix advisor/freeform container launch using wrong dev-base image or entrypoint Repro from a read-only director surface on 2026-07-10: ```text $ warded advisor coilyco-bridge/agentic-os-kai --instructions-file /scratch/cross-org-backlog-scout-brief.md latest: Pulling from coilyco-flight-deck/agentic-os Status: Image is up to date for forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest ward agent advisor --harness codex: answering with codex about coilyco-flight-deck/agentic-os in a fresh container... docker: Error response from daemon: ... exec: "/opt/ward/entrypoint.sh": stat /opt/ward/entrypoint.sh: no such file or directory exit status 127 ``` Observed problems: - The advisor/freeform path pulled `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest`. - The launched container expected `/opt/ward/entrypoint.sh`. - The current aos dev-base tests and Dockerfile contract point at `/opt/agentic-os/ward-shell-entrypoint.sh`, not `/opt/ward/entrypoint.sh`. - The command also reported it was answering about `coilyco-flight-deck/agentic-os` even though the requested target was `coilyco-bridge/agentic-os-kai`. Task: - Fix the ward advisor/freeform container path so it uses the correct dev-base image and entrypoint contract. - Preserve the explicit target repo when the caller passes `owner/repo --instructions-file`. - Add regression coverage for advisor/freeform launch planning that asserts the image, entrypoint, and target repo. - Verify the fixed path can launch far enough to run the advisor command or print the resolved plan without the missing-entrypoint failure. Related context: - `agentic-os` owns the image and entrypoint contract. - This issue is about ward selecting or launching that contract incorrectly. --- Filed by `ward agent engineer --harness codex`.  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 21:54:25 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1084 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-10T21:54:26Z). 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#1084 · branch issue-1084 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-1084 · ward v0.605.0 · dispatched 2026-07-10T21:54:26Z
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.605.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1084` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T21:54:26Z). 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#1084` · branch `issue-1084` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-1084` · ward `v0.605.0` · dispatched `2026-07-10T21:54:26Z` - **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.605.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 22:22:11 +00:00

Fix advisor/freeform container launch using wrong dev-base image or entrypoint #1093

coilyco-ops closed this issue

2026-07-10 22:23:15 +00:00

coilyco-ops commented

2026-07-10 22:23:52 +00:00

Author

Member

WARD-OUTCOME: submitted

details

review summary: skipped. The in-container review gate was intentionally skipped because the temporary ward default pending brokered QA.
workflow: pull-request-and-merge; review summary: skipped
felt: mostly wiring, then a short test-contract cleanup.
confidence: high.
surprises: the image contract and entrypoint path had drifted together, and the explicit repo target needed a separate freeform path.
follow-ups: director merge when ready.

WARD-OUTCOME: submitted <details><summary>details</summary> review summary: skipped. The in-container review gate was intentionally skipped because the temporary ward default pending brokered QA. workflow: pull-request-and-merge; review summary: skipped felt: mostly wiring, then a short test-contract cleanup. confidence: high. surprises: the image contract and entrypoint path had drifted together, and the explicit repo target needed a separate freeform path. follow-ups: director merge when ready. </details>