ward exec test fails on main in read-only surface

coilyco-ops commented

2026-07-25 23:54:05 +00:00

Member

A read-only director surface could not run ward exec test in /workspace/ward because git fetch origin could not write .git/FETCH_HEAD.

I cloned the same commit into /scratch/ward-test, checked out main at f90b33bd, and reran ward exec test. The gated test command failed with make: *** [Makefile:72: test] Error 1.

Visible failing tests:

TestMergePullRequestRequestShape/preserves-false and preserves-true: mergePullRequest: forgejo: merge PR coilyco-flight-deck/ward#729 refused from read-only surface; use ward agent director merge
TestBuildUpPlanTailnet: director role on linux should resolve host-net, got HostNet=false TSSidecar=true
TestRunContainerReapAnnouncesLogArchive: stderr missing the clean reap outcome after ward container reap: read-only session, nothing to salvage (skipping)

Several broker dispatch seed warnings also appeared: broker dispatch seed unavailable (broker refused (write-tier only): broker: dispatch requires target owner and repo), then fallback to env/SSM token path.

Please make the default ward exec test pass in this environment or isolate the tests that require non-read-only/write-tier broker state so the gated repo test remains reliable from director surfaces.

A read-only director surface could not run `ward exec test` in /workspace/ward because `git fetch origin` could not write `.git/FETCH_HEAD`. I cloned the same commit into `/scratch/ward-test`, checked out `main` at `f90b33bd`, and reran `ward exec test`. The gated test command failed with `make: *** [Makefile:72: test] Error 1`. Visible failing tests: - `TestMergePullRequestRequestShape/preserves-false` and `preserves-true`: `mergePullRequest: forgejo: merge PR coilyco-flight-deck/ward#729 refused from read-only surface; use ward agent director merge` - `TestBuildUpPlanTailnet`: `director role on linux should resolve host-net, got HostNet=false TSSidecar=true` - `TestRunContainerReapAnnouncesLogArchive`: stderr missing the clean reap outcome after `ward container reap: read-only session, nothing to salvage (skipping)` Several broker dispatch seed warnings also appeared: `broker dispatch seed unavailable (broker refused (write-tier only): broker: dispatch requires target owner and repo)`, then fallback to env/SSM token path. Please make the default `ward exec test` pass in this environment or isolate the tests that require non-read-only/write-tier broker state so the gated repo test remains reliable from director surfaces.

coilyco-ops referenced this issue

2026-07-28 03:05:24 +00:00

Describe the shipped exact-commit QA gate in engineer outcomes #1577

coilyco-ops commented

2026-07-28 03:06:26 +00:00

Author

Member

WARD-WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1565 on host KAI-DESKTOP-TOWER.

Accepted by ward agent --harness codex (reserved 2026-07-28T03:06:22Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation 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#1565 · branch issue-1565 · harness codex · workflow pull-request
Run: engineer-codex-ward-1565 · ward v0.819.0 · dispatched 2026-07-28T03:06:12Z
Reservation: held
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.819.0).

— Codex, via ward agent

WARD-WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1565` on host `KAI-DESKTOP-TOWER`. Accepted by `ward agent --harness codex` (reserved 2026-07-28T03:06:22Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` 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#1565` · branch `issue-1565` · harness `codex` · workflow `pull-request` - **Run:** `engineer-codex-ward-1565` · ward `v0.819.0` · dispatched `2026-07-28T03:06:12Z` - **Reservation:** held - **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.819.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-28 03:13:44 +00:00

Stabilize Ward for safe autonomous burndown and verified releases #1574

coilyco-ops added the

autonomy

live-collab

label

2026-07-28 03:28:31 +00:00

coilyco-ops commented

2026-07-28 03:28:45 +00:00

Author

Member

Dispatch checkpoint for parent #1574. The 2026-07-28 launch did not start because a stale engineer container already owned the issue-scoped name. Ward reports this issue as cleanup-needed with no started time. The current advisor surface cannot perform the supported issue-scoped stop. A director read-only surface must run ward agent stop coilyco-flight-deck/ward#1565, confirm the stale launch is cleared, then redispatch the issue under a non-merging pull-request workflow. No global reservation clear is safe while other issue runs are active.