Recover release setup after GitHub action fetch timeout

coilyco-ops commented

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

Member

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

headless

P1

labels

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

coilyco-ops commented

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

Author

Member

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 commented

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

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1443 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T13:14:38Z). 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#1443 · branch issue-1443 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1443 · ward v0.710.0 · dispatched 2026-07-15T13:14:31Z
Comment thread: 1 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T13:08:30Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1443` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T13:14:38Z). 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#1443` · branch `issue-1443` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1443` · ward `v0.710.0` · dispatched `2026-07-15T13:14:31Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T13:08:30Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0). </details> </details>  — Codex, via `ward agent`

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

Member

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

Member

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

Member

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

Member

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

Member

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

Member

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

Member

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

Member

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.

Rows
Columns

Recover release setup after GitHub action fetch timeout #1443

Problem

Acceptance