coilyco-gaming/steam-ops
2
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Run build-publish workflow in aos dev-base #5

New issue
Closed
opened 2026-07-09 03:52:00 +00:00 by coilyco-ops · 3 comments
coilyco-ops commented 2026-07-09 03:52:00 +00:00
Member
Copy link

The dev-base scan found .forgejo/workflows/build-publish.yml using astral-sh/setup-uv and downloading Docker CLI from download.docker.com. The pinned aos dev-base image already ships uv/Python and Docker CLI.

Acceptance criteria:

  • Run test and publish jobs in the pinned aos dev-base image.
  • Remove astral-sh/setup-uv and Docker CLI tarball install.
  • Keep Docker host probing and plain-http in-cluster registry push behavior unchanged.
The dev-base scan found `.forgejo/workflows/build-publish.yml` using `astral-sh/setup-uv` and downloading Docker CLI from `download.docker.com`. The pinned aos dev-base image already ships uv/Python and Docker CLI. Acceptance criteria: * Run test and publish jobs in the pinned aos dev-base image. * Remove `astral-sh/setup-uv` and Docker CLI tarball install. * Keep Docker host probing and plain-http in-cluster registry push behavior unchanged.
coilyco-ops commented 2026-07-09 03:55:39 +00:00
Author
Member
Copy link

🔒 Reserved by ward agent --harness codex — container engineer-codex-steam-ops-5 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T03:55:37Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force 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-gaming/steam-ops#5 · branch issue-5 · harness codex · workflow pr
  • Run: engineer-codex-steam-ops-5 · ward v0.470.0 · dispatched 2026-07-09T03:55:37Z
  • 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.470.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-steam-ops-5` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T03:55:37Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` 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-gaming/steam-ops#5` · branch `issue-5` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-steam-ops-5` · ward `v0.470.0` · dispatched `2026-07-09T03:55:37Z` - **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.470.0). </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 04:00:17 +00:00
Author
Member
Copy link

WARD-OUTCOME: done - build-publish now runs both jobs in the pinned dev-base image and still probes Docker host before plain-http push.
Review gate skipped because --skip-preflight / --no-preflight also skips review.
The change was straightforward. The only friction was this container's own uv/ward environment, which confirmed why the workflow needed the dev-base pin. Confidence is high, and the only follow-up I’d watch is the next CI run for any mismatch between the dev-base toolset and Forgejo’s container runner.

WARD-OUTCOME: done - build-publish now runs both jobs in the pinned dev-base image and still probes Docker host before plain-http push. Review gate skipped because --skip-preflight / --no-preflight also skips review. The change was straightforward. The only friction was this container's own uv/ward environment, which confirmed why the workflow needed the dev-base pin. Confidence is high, and the only follow-up I’d watch is the next CI run for any mismatch between the dev-base toolset and Forgejo’s container runner.
coilyco-ops commented 2026-07-09 04:00:28 +00:00
Author
Member
Copy link

⚠️ Reopened: this run's work did not land on main

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

  • Repo: coilyco-gaming/steam-ops
  • Salvage branch: ward-salvage/steam-ops-6dd1e29c
  • Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
  • Reason: run workflow does not land on main (--workflow pr/patch-only)
  • Container uptime at reap: 4m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              d2a53f2205cb
origin/main:       18f8c56d0d5d
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  4m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-gaming/steam-ops.git ward-salvage/steam-ops-6dd1e29c
git checkout -b ward-salvage/steam-ops-6dd1e29c FETCH_HEAD

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #5 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-gaming/steam-ops` - **Salvage branch:** `ward-salvage/steam-ops-6dd1e29c` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 4m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: d2a53f2205cb origin/main: 18f8c56d0d5d ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 4m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-gaming/steam-ops.git ward-salvage/steam-ops-6dd1e29c git checkout -b ward-salvage/steam-ops-6dd1e29c FETCH_HEAD ``` <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ward-salvage/steam-ops-6dd1e29c
No results found.
Labels
Clear labels
  
consult
'A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
priority tier

  
P1
priority tier

  
P2
priority tier

  
P3
priority tier

  
P4
priority tier

No labels
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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-gaming/steam-ops#5
No description provided.