coilyco-flight-deck/ward

Watch

Remove all refs to coilyco-bridge #1479

New issue

Closed

opened 2026-07-18 03:46:00 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-07-18 03:46:00 +00:00

Owner

No description provided.

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-28 08:47:27 +00:00

coilyco-ops referenced this issue from a commit

2026-07-28 09:51:26 +00:00

Remove coilyco-bridge references

coilyco-ops closed this issue

2026-07-28 09:51:26 +00:00

coilyco-ops commented

2026-07-28 09:54:17 +00:00

Member

WARD-WORKFLOW: done ✅

details

review summary: skipped: the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA.
workflow: merge-remote-main; review summary: skipped: the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA.
implementation felt: straightforward reference removal with a small amount of fixture cleanup to keep existing coverage meaningful.
confidence: high.
surprises: ward exec test still hit the existing async broker tempdir cleanup race in cmd/ward; the affected tests and script tests passed, and that broker test passed when rerun directly. The post-push Forgejo Actions check could not authenticate because aosguard tried SSM/IMDS inside this container.
follow-ups: inspect the release run from an authenticated host if the post-push check is required.

WARD-WORKFLOW: done ✅ <details><summary>details</summary> review summary: skipped: the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA. workflow: merge-remote-main; review summary: skipped: the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA. implementation felt: straightforward reference removal with a small amount of fixture cleanup to keep existing coverage meaningful. confidence: high. surprises: `ward exec test` still hit the existing async broker tempdir cleanup race in `cmd/ward`; the affected tests and script tests passed, and that broker test passed when rerun directly. The post-push Forgejo Actions check could not authenticate because `aosguard` tried SSM/IMDS inside this container. follow-ups: inspect the release run from an authenticated host if the post-push check is required. </details>

coilyco-ops reopened this issue

2026-07-28 09:54:25 +00:00

coilyco-ops commented

2026-07-28 09:54:25 +00:00

Member

WARD-WORKFLOW: blocked 🛑

salvage details

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #1479 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/ward
Salvage branch: ward-salvage/ward-b7b26d1d
Pull request: not opened - salvage branch has no diff against main
Reason: merge conflict integrating onto main
Container uptime at reap: 10m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Cleanup diagnostics

--- reap diagnostics ---
ward version:      v0.823.0
version source:    pinned via WARD_VERSION/--ward-version (v0.823.0)
HEAD:              0cb0054c1590
origin/main:       0cb0054c1590
ancestry:          HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature)
decision gate:     provenance missing or unreadable on already-landed merge-remote-main run
reason:            merge conflict integrating onto main
provenance:        missing or unreadable
run-owned landed:  no
working tree:      clean
container uptime:  10m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-b7b26d1d
git checkout -b ward-salvage/ward-b7b26d1d FETCH_HEAD

— Codex, via ward agent

WARD-WORKFLOW: blocked 🛑 <details><summary>salvage details</summary> An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #1479 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/ward` - **Salvage branch:** `ward-salvage/ward-b7b26d1d` - **Pull request:** not opened - salvage branch has no diff against main - **Reason:** merge conflict integrating onto main - **Container uptime at reap:** 10m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Cleanup diagnostics ``` --- reap diagnostics --- ward version: v0.823.0 version source: pinned via WARD_VERSION/--ward-version (v0.823.0) HEAD: 0cb0054c1590 origin/main: 0cb0054c1590 ancestry: HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature) decision gate: provenance missing or unreadable on already-landed merge-remote-main run reason: merge conflict integrating onto main provenance: missing or unreadable run-owned landed: no working tree: clean container uptime: 10m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-b7b26d1d git checkout -b ward-salvage/ward-b7b26d1d FETCH_HEAD ``` </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-28 09:54:26 +00:00

Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-ward-1479 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: blocked 🛑`. `ward container reap` released container `engineer-codex-ward-1479` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-28 10:15:04 +00:00

Member

Director cleanup: closing this manually because the run completed despite the later false salvage notice. Proof from the archived run: posted WARD-WORKFLOW: done; landed and pushed main at 0cb0054c; reaper diagnostics say HEAD is ALREADY on origin/main and salvage has no diff. The false-salvage bug is captured as coilyco-flight-deck/ward#1606.

Director cleanup: closing this manually because the run completed despite the later false salvage notice. Proof from the archived run: posted WARD-WORKFLOW: done; landed and pushed main at 0cb0054c; reaper diagnostics say HEAD is ALREADY on origin/main and salvage has no diff. The false-salvage bug is captured as coilyco-flight-deck/ward#1606.

coilyco-ops closed this issue

2026-07-28 10:15:09 +00:00

No milestone

No project

No assignees

2 participants

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

No description provided.

Rows
Columns