Recover release setup after GitHub action fetch timeout

coilyco-ops commented

2026-07-15 13:08:07 +00:00

Owner

Problem

Post-merge release run 8575 / repository run #2288 failed after PR #1441, but no Ward release logic executed. The runner failed during job setup while fetching the shared Agentic OS actions repository:

Set up job: failure after 5m6s
could not fetch remote origin: fatal: unable to access https://github.com/coilysiren/agentic-os/: Connection timed out after 300009 milliseconds
checkout, tag-bump, create-release: cancelled

This is currently a transient external GitHub fetch timeout, not evidence of a defect in #1441. It still needs a recovery trail so the closed resource-warning issue is not left with a red release.

Acceptance

Retrigger the supported release path on current main, using the next eligible main push if Forgejo cannot rerun the completed Actions run directly.
Confirm release.yml passes through setup, tag bump, release creation, and downstream release jobs.
If the GitHub fetch timeout recurs, harden the shared-action acquisition path with a focused retry, bounded timeout, or canonical mirror rather than broad workflow churn.
Leave the green run evidence or the exact remaining external blocker.

Related: #1307, #1441, run 8575 / #2288.

## Problem Post-merge release run 8575 / repository run #2288 failed after PR #1441, but no Ward release logic executed. The runner failed during job setup while fetching the shared Agentic OS actions repository: ```text Set up job: failure after 5m6s could not fetch remote origin: fatal: unable to access https://github.com/coilysiren/agentic-os/: Connection timed out after 300009 milliseconds checkout, tag-bump, create-release: cancelled ``` This is currently a transient external GitHub fetch timeout, not evidence of a defect in #1441. It still needs a recovery trail so the closed resource-warning issue is not left with a red release. ## Acceptance * Retrigger the supported release path on current main, using the next eligible main push if Forgejo cannot rerun the completed Actions run directly. * Confirm `release.yml` passes through setup, tag bump, release creation, and downstream release jobs. * If the GitHub fetch timeout recurs, harden the shared-action acquisition path with a focused retry, bounded timeout, or canonical mirror rather than broad workflow churn. * Leave the green run evidence or the exact remaining external blocker. Related: #1307, #1441, run 8575 / #2288.

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 13:08:07 +00:00

coilyco-ops added the

labels

2026-07-15 13:08:07 +00:00

coilyco-ops commented

2026-07-15 13:08:30 +00:00

Author

Owner

DISPATCH-DEFERRED: capacity blocked. Attempted warded engineer coilyco-flight-deck/ward#1443 --harness codex --workflow pull-request-and-merge from the director surface. Ward rejected the launch because the repository already has 3 active engineers at its limit of 3. No override was used. Retry this transient release recovery when a slot opens, or close it with the next green release.yml run on current main.

coilyco-ops referenced this issue from a commit

2026-07-15 13:32:00 +00:00

fix(release): remove shared action fetch from setup

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

2026-07-15 13:33:33 +00:00

Recover release setup after GitHub action fetch timeout #1452

coilyco-ops commented

2026-07-15 13:36:24 +00:00

Author

Owner

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T13:33:33Z is newer than the latest ward acknowledgement at 2026-07-15T13:14:38Z

This action is blocked until the feedback is visibly acknowledged.

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T13:33:33Z is newer than the latest ward acknowledgement at 2026-07-15T13:14:38Z This action is blocked until the feedback is visibly acknowledged. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 13:37:10 +00:00

Author

Owner

WARDED_WORKFLOW: #1452

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

felt: mechanical once the helper contract was clear.

confidence: high

surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot.

follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1452 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA felt: mechanical once the helper contract was clear. confidence: high surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot. follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained. </details>

coilyco-ops referenced this issue

2026-07-15 13:38:59 +00:00

Recover PR #1452 merge 405 after green checks #1453

coilyco-ops referenced this issue

2026-07-15 13:39:43 +00:00

Recover PR #1452 merge 405 after green checks #1453

coilyco-ops referenced this issue

2026-07-15 13:39:45 +00:00

Recover PR #1452 merge 405 after green checks #1453

coilyco-ops commented

2026-07-15 13:40:07 +00:00

Author

Owner

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T13:39:45Z is newer than the latest ward acknowledgement at 2026-07-15T13:37:10Z

This action is blocked until the feedback is visibly acknowledged.

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T13:39:45Z is newer than the latest ward acknowledgement at 2026-07-15T13:37:10Z This action is blocked until the feedback is visibly acknowledged. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 13:40:38 +00:00

Author

Owner

WARDED_WORKFLOW: #1452

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

felt: mechanical once the helper contract was clear.

confidence: high

surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot.

follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1452 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA felt: mechanical once the helper contract was clear. confidence: high surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot. follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained. </details>

coilyco-ops commented

2026-07-15 13:40:57 +00:00

Author

Owner

WARDED_WORKFLOW: #1452

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

felt: mechanical once the helper contract was clear.

confidence: high

surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot.

follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1452 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA felt: mechanical once the helper contract was clear. confidence: high surprises: the merge gate needs a fresh ward acknowledgement after the PR snapshot. follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained. </details>

coilyco-ops referenced this issue from a commit

2026-07-15 13:47:21 +00:00

fix(release): remove shared action fetch from setup

coilyco-ops commented

2026-07-15 13:48:59 +00:00

Author

Owner

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T13:47:21Z is newer than the latest ward acknowledgement at 2026-07-15T13:40:57Z

This action is blocked until the feedback is visibly acknowledged.

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T13:47:21Z is newer than the latest ward acknowledgement at 2026-07-15T13:40:57Z This action is blocked until the feedback is visibly acknowledged. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 13:49:21 +00:00

Author

Owner

WARDED_WORKFLOW: #1452

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

felt: mechanical once the helper contract was clear.

confidence: high

surprises: the merge gate keeps needing a fresh ward acknowledgement after each PR snapshot update.

follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1452 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA felt: mechanical once the helper contract was clear. confidence: high surprises: the merge gate keeps needing a fresh ward acknowledgement after each PR snapshot update. follow-ups: keep watching for shared-action fetch regressions; the new local helpers should keep setup self-contained. </details>

coilyco-ops referenced this issue

2026-07-15 13:56:41 +00:00

Repair release-tag helper on internal Forgejo origin URL #1460

coilyco-ops commented

2026-07-15 13:59:18 +00:00

Author

Owner

Director note: leaving #1443 open as the parent release-recovery acceptance issue, but the active blockers are now split into dispatched repairs #1459 (daemon-independent ward:release alias publish) and #1460 (internal Forgejo release-tag origin URL). Stopping the older #1443 engineer run so it does not keep cycling on superseded PR #1452 while those focused repairs run.

coilyco-ops closed this issue

2026-07-25 06:24:38 +00:00

coilyco-ops referenced this issue from a commit

2026-07-25 06:24:38 +00:00

merge: recover release setup after GitHub action fetch timeout

coilyco-ops commented

2026-07-25 06:25:02 +00:00

Author

Owner

WARD-WORKFLOW: done ✅

details

workflow: merge-remote-main; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

felt: mechanical; the release setup was already in main, so this was mostly history repair.

confidence: high

surprises: origin/main moved while I was landing the merge, so I replayed it on the fresh tip.

follow-ups: green release.yml run 11181 on release.

WARD-WORKFLOW: done ✅ <details><summary>details</summary> workflow: merge-remote-main; review summary: review gate intentionally skipped because temporary ward default pending brokered QA felt: mechanical; the release setup was already in main, so this was mostly history repair. confidence: high surprises: origin/main moved while I was landing the merge, so I replayed it on the fresh tip. follow-ups: green release.yml run 11181 on `release`. </details>

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

2026-07-25 06:25:08 +00:00

ward salvage: ward-salvage/ward-3800c2d1 #1560

coilyco-ops reopened this issue

2026-07-25 06:25:08 +00:00

coilyco-ops commented

2026-07-25 06:25:09 +00:00

Author

Owner

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 #1443 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/ward
Salvage branch: ward-salvage/ward-3800c2d1
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: merge conflict integrating onto main
Container uptime at reap: 7m (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.805.0
version source:    pinned via WARD_VERSION/--ward-version (v0.805.0)
HEAD:              cb539f9b82da
origin/main:       cb539f9b82da
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:  7m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-3800c2d1
git checkout -b ward-salvage/ward-3800c2d1 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 #1443 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/ward` - **Salvage branch:** `ward-salvage/ward-3800c2d1` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** merge conflict integrating onto main - **Container uptime at reap:** 7m (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.805.0 version source: pinned via WARD_VERSION/--ward-version (v0.805.0) HEAD: cb539f9b82da origin/main: cb539f9b82da 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: 7m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-3800c2d1 git checkout -b ward-salvage/ward-3800c2d1 FETCH_HEAD ``` </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-25 06:25:09 +00:00

Author

Owner

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-ward-1443 (--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-1443` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-28 02:25:02 +00:00

Stabilize Ward for safe autonomous burndown and verified releases #1574

coilyco-ops commented

2026-07-28 02:43:22 +00:00

Author

Owner

Tracker reconciliation for #1574:

cb539f9 and 5e93f34 landed the release-setup recovery on main.
This issue already records WARD-WORKFLOW: done with a green release run.
The later blocked record identifies itself as a false salvage after the work was already on origin/main.
The current v0.823.0 promote and release runs are green. The separate stable-asset byte defect is tracked at #1575.

The agent is closing this completed issue as tracker reconciliation. No new implementation is being claimed here.

Codex, via advisor surface

Tracker reconciliation for https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1574: * https://forgejo.coilysiren.me/coilyco-flight-deck/ward/commit/cb539f9 and https://forgejo.coilysiren.me/coilyco-flight-deck/ward/commit/5e93f34 landed the release-setup recovery on `main`. * This issue already records `WARD-WORKFLOW: done` with a green release run. * The later blocked record identifies itself as a false salvage after the work was already on `origin/main`. * The current v0.823.0 promote and release runs are green. The separate stable-asset byte defect is tracked at https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1575. The agent is closing this completed issue as tracker reconciliation. No new implementation is being claimed here.  Codex, via advisor surface

coilyco-ops closed this issue

2026-07-28 02:43:26 +00:00

coilyco-ops referenced this issue

2026-07-28 02:45:16 +00:00

Exclude closed completed issues from active dispatch-health failures #1576

coilyco-ops referenced this issue

2026-07-28 02:47:45 +00:00

Stabilize Ward for safe autonomous burndown and verified releases #1574