coilyco-flight-deck/ward

Fork 0

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

New issue

Closed

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

coilyco-ops commented

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

Member

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 commented

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

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T22:02:54Z). 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#1087 · branch issue-1087 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-1087 · ward v0.605.0 · dispatched 2026-07-10T22:02:54Z
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-1087` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T22:02:54Z). 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#1087` · branch `issue-1087` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-1087` · ward `v0.605.0` · dispatched `2026-07-10T22:02:54Z` - **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: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

Member

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>

coilyco-ops commented

2026-07-10 23:12:43 +00:00

Author

Member

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /scratch/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer3253908897/001/.ward/agent-logs/dispatch/20260710T231245Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 7 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/scratch/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer3253908897/001/.ward/agent-logs/dispatch/20260710T231245Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 7 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 23:12:44 +00:00

Author

Member

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /scratch/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV2321960717/001/.ward/agent-logs/dispatch/20260710T231246Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 7 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/scratch/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV2321960717/001/.ward/agent-logs/dispatch/20260710T231246Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 7 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

forgejo-actions commented

2026-07-10 23:25:12 +00:00

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /tmp/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer597866969/001/.ward/agent-logs/dispatch/20260710T232512Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 8 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/tmp/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer597866969/001/.ward/agent-logs/dispatch/20260710T232512Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 8 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

forgejo-actions commented

2026-07-10 23:25:13 +00:00

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /tmp/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV3570293171/001/.ward/agent-logs/dispatch/20260710T232512Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 8 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/tmp/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV3570293171/001/.ward/agent-logs/dispatch/20260710T232512Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 8 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 23:28:06 +00:00

Author

Member

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /scratch/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer473759058/001/.ward/agent-logs/dispatch/20260710T232808Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 10 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/scratch/TestStartHostDispatchBrokerRequestWaitsForVisibleEngineer473759058/001/.ward/agent-logs/dispatch/20260710T232808Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 10 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 23:28:07 +00:00

Author

Member

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#1087 --harness codex
Container: engineer-codex-ward-1087
Container created: no running engineer was observed.
Host log: /scratch/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV2922969080/001/.ward/agent-logs/dispatch/20260710T232809Z-director-codex-host-coilyco-flight-deck-ward-1087.log
Capacity: ward agent engineer --harness codex: open PR backpressure is engaged: 10 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#1087 --harness codex` Container: `engineer-codex-ward-1087` Container created: no running engineer was observed. Host log: `/scratch/TestStartHostDispatchBrokerRequestFailsWhenEngineerNeverBecomesV2922969080/001/.ward/agent-logs/dispatch/20260710T232809Z-director-codex-host-coilyco-flight-deck-ward-1087.log` Capacity: `ward agent engineer --harness codex: open PR backpressure is engaged: 10 open PR branch(es) (limit 6); continue with --branch on an existing PR or wait for the queue to drain` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`