coilyco-flight-deck/ward

Archived

Watch

Title: Make forwarded dispatch report failure when no worker becomes vis… #1087

Closed

opened 2026-07-10 22:02:44 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 22:02:44 +00:00

Owner

Title: Make forwarded dispatch report failure when no worker becomes visible

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

$ warded engineer coilyco-bridge/agentic-os-kai#736 --harness claude --force
ward dispatch broker: forwarded `ward agent engineer coilyco-bridge/agentic-os-kai#736 --harness claude --ward-version v0.605.0 --force` to host ward ...

Follow-up evidence:

$ ward agent list
# no engineer-claude-agentic-os-kai-736 entry

$ ward agent logs engineer-claude-agentic-os-kai-736 --tail 160
ward: dispatch broker: dispatch broker: no engineer log source matches "engineer-claude-agentic-os-kai-736"

Observed behavior:

The dispatch command reports success because it forwarded the request to the host broker.
The expected worker never becomes visible in ward agent list.
No log source exists from the director surface, so the director cannot tell whether launch failed, queued invisibly, or landed under another name.

Task:

Make the forwarded dispatch path distinguish "broker accepted the request" from "worker launched and is visible".
If the host broker cannot synchronously confirm launch, print the exact follow-up status command or broker log lookup that will work from the director surface.
Prefer a non-zero or clearly degraded result when the forwarded launch fails before a worker exists.
Add regression coverage for forwarded-dispatch success reporting and missing-worker follow-up behavior.

Keep messages public-safe and do not bake host-specific paths into tests.

Filed by ward agent engineer --harness codex.

— Codex, via ward agent

Title: Make forwarded dispatch report failure when no worker becomes visible Repro from a read-only director surface on 2026-07-10: ```text $ warded engineer coilyco-bridge/agentic-os-kai#736 --harness claude --force ward dispatch broker: forwarded `ward agent engineer coilyco-bridge/agentic-os-kai#736 --harness claude --ward-version v0.605.0 --force` to host ward ... ``` Follow-up evidence: ```text $ ward agent list # no engineer-claude-agentic-os-kai-736 entry $ ward agent logs engineer-claude-agentic-os-kai-736 --tail 160 ward: dispatch broker: dispatch broker: no engineer log source matches "engineer-claude-agentic-os-kai-736" ``` Observed behavior: - The dispatch command reports success because it forwarded the request to the host broker. - The expected worker never becomes visible in `ward agent list`. - No log source exists from the director surface, so the director cannot tell whether launch failed, queued invisibly, or landed under another name. Task: - Make the forwarded dispatch path distinguish "broker accepted the request" from "worker launched and is visible". - If the host broker cannot synchronously confirm launch, print the exact follow-up status command or broker log lookup that will work from the director surface. - Prefer a non-zero or clearly degraded result when the forwarded launch fails before a worker exists. - Add regression coverage for forwarded-dispatch success reporting and missing-worker follow-up behavior. Keep messages public-safe and do not bake host-specific paths into tests. --- Filed by `ward agent engineer --harness codex`.  — Codex, via `ward agent`

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

2026-07-10 22:25:53 +00:00

Make forwarded dispatch report failure when no worker becomes visible #1095

coilyco-ops closed this issue

2026-07-10 22:33:58 +00:00

coilyco-ops commented

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

Author

Owner

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: skipped - in-container review gate intentionally skipped pending brokered QA retrospective: the fix was smaller than the CI detour; the visibility edge needed one extra wrap confidence: high surprise: Forgejo surfaced job logs through the attempt JSON endpoint, not the raw logs URL follow-ups: none

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped - in-container review gate intentionally skipped pending brokered QA retrospective: the fix was smaller than the CI detour; the visibility edge needed one extra wrap confidence: high surprise: Forgejo surfaced job logs through the attempt JSON endpoint, not the raw logs URL follow-ups: none </details>

forgejo-actions commented

2026-08-05 09:52:03 +00:00

WARD-WORKFLOW: failed ❌

launch failure details

This forwarded dispatch failed before the engineer harness started.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex --pr
Container: engineer-codex-ward-1087
Docker state/error: dispatch broker: launch accepted but could not confirm engineer visibility; inspect with ward agent list from the director surface: dispatch broker: check engineer visibility for coilyco-flight-deck/ward#1087: signal: killed
Broker artifact: /tmp/TestStartHostDispatchBrokerRequestReportsMissingEngineerVisibili1161346608/001/.ward/agent-logs/dispatch/2866f417571f60e4ea781ebb8bcc7068-director-codex-host-coilyco-flight-deck-ward-1087/console.log

Reservation: released. Container cleanup: Ward removes a created pre-agent container when it can. No salvage branch was created or advertised because no harness worktree delta was possible before harness start.

— Codex, via ward agent

WARD-WORKFLOW: failed ❌ <details><summary>launch failure details</summary> This forwarded dispatch failed before the engineer harness started. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex --pr` Container: `engineer-codex-ward-1087` Docker state/error: `dispatch broker: launch accepted but could not confirm engineer visibility; inspect with `ward agent list` from the director surface: dispatch broker: check engineer visibility for coilyco-flight-deck/ward#1087: signal: killed` Broker artifact: `/tmp/TestStartHostDispatchBrokerRequestReportsMissingEngineerVisibili1161346608/001/.ward/agent-logs/dispatch/2866f417571f60e4ea781ebb8bcc7068-director-codex-host-coilyco-flight-deck-ward-1087/console.log` Reservation: released. Container cleanup: Ward removes a created pre-agent container when it can. No salvage branch was created or advertised because no harness worktree delta was possible before harness start. </details>  — Codex, via `ward agent`

Commenting is not possible because the repository is archived.

No milestone

No project

No assignees

2 participants

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#1087

No description provided.

Rows
Columns