Make Scoop release digest helper return raw sidecar body

coilyco-ops commented

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

Member

Problem

QA on closed #1412 after PR #1416 found that release.yml still fails in bump-scoop-manifest for the same release-Scoop acceptance chain.

Run evidence:

run 8524 (#2248) failure release.yml push release "Fix release Scoop helper availability (#1416)"
job bump-scoop-manifest
::error::sidecar digest '{"id":4253,"name":"ward-windows-amd64.exe.sha256","size":286,"download_count":0,"created_at":"2026-07-15T12:02:03Z","uuid":"ded189bb-a00f-4440-bd0d-e282f1499604","browser_download_url":"https://forgejo.coilysiren.me/attachments/ded189bb-a00f-4440-bd0d-e282f1499604","type":"attachment"}' is not a 64-hex sha256; refusing to write manifest

PR #1416 made scripts/forgejo-release-asset.sh available to the job, so the previous No such file or directory error is gone. The remaining blocker is that the helper/API path is still returning release asset metadata JSON where the Scoop manifest job expects the raw .sha256 asset body.

This is a missed acceptance follow-up for #1412. #1412 required preserving the #1410 behavior: read the raw .sha256 asset body, not release asset metadata JSON, and confirm release.yml succeeds for the current release branch SHA including bump-scoop-manifest.

Acceptance

Make bump-scoop-manifest read the raw 64-hex .sha256 asset body for both Windows assets in release.yml after the #1416 checkout fix.
Preserve the best-effort behavior from #1414 for missing Scoop token / bucket push side effects.
Add or update workflow/contract coverage so returning release asset metadata JSON for a sidecar digest is caught before merge.
Confirm release.yml succeeds for the current release branch SHA including bump-scoop-manifest, or leave exact blocker evidence.

Related: #1412, #1416, run 8524 / #2248.

## Problem QA on closed #1412 after PR #1416 found that release.yml still fails in bump-scoop-manifest for the same release-Scoop acceptance chain. Run evidence: ```text run 8524 (#2248) failure release.yml push release "Fix release Scoop helper availability (#1416)" job bump-scoop-manifest ::error::sidecar digest '{"id":4253,"name":"ward-windows-amd64.exe.sha256","size":286,"download_count":0,"created_at":"2026-07-15T12:02:03Z","uuid":"ded189bb-a00f-4440-bd0d-e282f1499604","browser_download_url":"https://forgejo.coilysiren.me/attachments/ded189bb-a00f-4440-bd0d-e282f1499604","type":"attachment"}' is not a 64-hex sha256; refusing to write manifest ``` PR #1416 made `scripts/forgejo-release-asset.sh` available to the job, so the previous `No such file or directory` error is gone. The remaining blocker is that the helper/API path is still returning release asset metadata JSON where the Scoop manifest job expects the raw `.sha256` asset body. This is a missed acceptance follow-up for #1412. #1412 required preserving the #1410 behavior: read the raw `.sha256` asset body, not release asset metadata JSON, and confirm release.yml succeeds for the current release branch SHA including bump-scoop-manifest. ## Acceptance - Make `bump-scoop-manifest` read the raw 64-hex `.sha256` asset body for both Windows assets in release.yml after the #1416 checkout fix. - Preserve the best-effort behavior from #1414 for missing Scoop token / bucket push side effects. - Add or update workflow/contract coverage so returning release asset metadata JSON for a sidecar digest is caught before merge. - Confirm release.yml succeeds for the current release branch SHA including bump-scoop-manifest, or leave exact blocker evidence. Related: #1412, #1416, run 8524 / #2248.

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

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

coilyco-ops added the

headless

P2

labels

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

coilyco-ops referenced this issue

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

Make release Scoop asset helper available to bump-scoop job #1412

coilyco-ops commented

2026-07-15 12:04:11 +00:00

Author

Member

DISPATCH-DEFERRED: capacity blocked. Attempted warded engineer coilyco-flight-deck/ward#1420 --harness codex --workflow pull-request-and-merge at 2026-07-15T12:03Z from the director surface. Ward rejected the launch because coilyco-flight-deck/ward already has 3 active engineers at the repo limit. Broker evidence: repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3). Dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T120355Z-director-codex-jp85-coilyco-flight-deck-ward-1420.log. Retry this release blocker as soon as a slot opens.

coilyco-ops commented

2026-07-15 12:04:39 +00:00

Author

Member

DISPATCH-DEFERRED: capacity blocked. Attempted warded engineer coilyco-flight-deck/ward#1420 --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 concrete release digest repair as soon as a slot opens; #1419 is the umbrella recovery for the same failed run.

coilyco-ops referenced this issue

2026-07-15 12:04:53 +00:00

Repair failed release run after PR #1416 #1419

coilyco-ops commented

2026-07-15 12:23:11 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T12:23:10Z). 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#1420 · branch issue-1420 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1420 · ward v0.710.0 · dispatched 2026-07-15T12:23:02Z
Comment thread: 2 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T12:04:11Z), @coilyco-ops (2026-07-15T12:04:39Z)

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-1420` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T12:23:10Z). 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#1420` · branch `issue-1420` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1420` · ward `v0.710.0` · dispatched `2026-07-15T12:23:02Z` - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T12:04:11Z), @coilyco-ops (2026-07-15T12:04:39Z) 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 pull request that will close it,

2026-07-15 12:29:32 +00:00

Make Scoop release digest helper return raw sidecar body #1429

coilyco-ops closed this issue

2026-07-15 12:30:47 +00:00

coilyco-ops commented

2026-07-15 12:30:48 +00:00

Author

Member

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T12:30:47Z is newer than the latest ward acknowledgement at 2026-07-15T12:23:11Z

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-15T12:30:47Z is newer than the latest ward acknowledgement at 2026-07-15T12:23:11Z This action is blocked until the feedback is visibly acknowledged. </details>  — Codex, via `ward agent`

coilyco-ops commented

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

Author

Member

WARDED_WORKFLOW: #1429

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped (temporary ward default pending brokered QA)
felt: straightforward implementation; the merge gate was the only surprise
confidence: high
follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1429 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped (temporary ward default pending brokered QA) felt: straightforward implementation; the merge gate was the only surprise confidence: high follow-ups: none </details>

coilyco-ops referenced this issue

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

Repair failed release run after PR #1429 #1430

coilyco-ops commented

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

Author

Member

QA FAIL post-merge check on 2026-07-15: PR #1429 merged as 652959ff8dd17cc40ca1cf5f666a7d6c4fcb74c6, and promote passed, but release run 8547 / repository run #2266 still failed in bump-scoop-manifest.

Exact failure from job bump-scoop-manifest:

::error::sidecar digest '{"id":4316,"name":"ward-windows-amd64.exe.sha256","size":65,"download_count":0,"created_at":"2026-07-15T12:32:23Z","uuid":"c2a3d796-517a-44be-86b7-cfdfeacb2061","browser_download_url":"https://forgejo.coilysiren.me/attachments/c2a3d796-517a-44be-86b7-cfdfeacb2061","type":"attachment"}' is not a 64-hex sha256; refusing to write manifest
Job bump-scoop-manifest failed

This misses the acceptance requirement to make bump-scoop-manifest read raw 64-hex .sha256 bodies and confirm release.yml succeeds. I am filing a new same-label follow-up for the remaining release blocker.

QA FAIL post-merge check on 2026-07-15: PR #1429 merged as `652959ff8dd17cc40ca1cf5f666a7d6c4fcb74c6`, and promote passed, but release run 8547 / repository run #2266 still failed in `bump-scoop-manifest`. Exact failure from job `bump-scoop-manifest`: ```text ::error::sidecar digest '{"id":4316,"name":"ward-windows-amd64.exe.sha256","size":65,"download_count":0,"created_at":"2026-07-15T12:32:23Z","uuid":"c2a3d796-517a-44be-86b7-cfdfeacb2061","browser_download_url":"https://forgejo.coilysiren.me/attachments/c2a3d796-517a-44be-86b7-cfdfeacb2061","type":"attachment"}' is not a 64-hex sha256; refusing to write manifest Job bump-scoop-manifest failed ``` This misses the acceptance requirement to make `bump-scoop-manifest` read raw 64-hex `.sha256` bodies and confirm release.yml succeeds. I am filing a new same-label follow-up for the remaining release blocker.

coilyco-ops referenced this issue

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

Make Scoop digest helper fetch raw attachment bodies #1431

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:35:30 +00:00

Download raw Scoop sidecar content from Forgejo attachment URL #1433