coilyco-flight-deck/ward

Fork 0

Repair failed release run after PR #1429 #1430

New issue

Closed

opened 2026-07-15 12:33:41 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 12:33:41 +00:00

Member

Problem

Post-merge release run 8547 / repository run #2266 failed after PR #1429 merged for #1420. Current run evidence:

run 8547 (#2266) failure release.yml push release "Make Scoop release digest helper return raw sidecar body (#1429)"

PR #1429 fixed the previous Scoop digest helper path enough for PR tests and promote to pass, but the release path is still not green. #1420 is already closed, so this needs its own recovery trail instead of disappearing into the closed issue.

Acceptance

Inspect release run 8547 / repository run #2266 after PR #1429.
If the failure is transient, retrigger the supported release path.
If the failure is real, repair it with a focused change.
Preserve the best-effort behavior for missing Scoop token / bucket push side effects.
Leave final evidence showing release.yml green, or document the exact remaining blocker.

Related: #1420, #1429, run 8547 / #2266.

## Problem Post-merge release run 8547 / repository run #2266 failed after PR #1429 merged for #1420. Current run evidence: ```text run 8547 (#2266) failure release.yml push release "Make Scoop release digest helper return raw sidecar body (#1429)" ``` PR #1429 fixed the previous Scoop digest helper path enough for PR tests and promote to pass, but the release path is still not green. #1420 is already closed, so this needs its own recovery trail instead of disappearing into the closed issue. ## Acceptance - Inspect release run 8547 / repository run #2266 after PR #1429. - If the failure is transient, retrigger the supported release path. - If the failure is real, repair it with a focused change. - Preserve the best-effort behavior for missing Scoop token / bucket push side effects. - Leave final evidence showing release.yml green, or document the exact remaining blocker. Related: #1420, #1429, run 8547 / #2266.

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

2026-07-15 12:33:41 +00:00

coilyco-ops added the

headless

labels

2026-07-15 12:33:41 +00:00

coilyco-ops commented

2026-07-15 12:34:08 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T12:34:07Z). 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#1430 · branch issue-1430 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1430 · ward v0.710.0 · dispatched 2026-07-15T12:33:59Z
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.710.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1430` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T12:34:07Z). 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#1430` · branch `issue-1430` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1430` · ward `v0.710.0` · dispatched `2026-07-15T12:33:59Z` - **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.710.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-15 12:35:26 +00:00

Make Scoop digest helper fetch raw attachment bodies #1431

coilyco-ops referenced this issue

2026-07-15 12:36:08 +00:00

Download raw Scoop sidecar content from Forgejo attachment URL #1433

coilyco-ops referenced this issue from a commit

2026-07-15 12:41:16 +00:00

fix release asset dereference chain

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

2026-07-15 12:41:57 +00:00

Fix release asset digest dereference chain #1436

coilyco-ops closed this issue

2026-07-15 12:43:58 +00:00

coilyco-ops commented

2026-07-15 12:44:03 +00:00

Author

Member

WARDED_WORKFLOW: #1436

details

workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA) felt: the fix was narrow, but the live Forgejo release asset chain took an extra hop to expose the raw digest. confidence: high surprises: the release download URL still wrapped attachment metadata before the raw body. follow-ups: none from this patch.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1436 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA) felt: the fix was narrow, but the live Forgejo release asset chain took an extra hop to expose the raw digest. confidence: high surprises: the release download URL still wrapped attachment metadata before the raw body. follow-ups: none from this patch. </details>