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

Closed
opened 2026-07-09 03:51:59 +00:00 by coilyco-ops · 3 comments
Member

The dev-base scan found .forgejo/workflows/build-publish.yml using astral-sh/setup-uv, azure/setup-helm, and a runtime Docker CLI tarball install. The pinned aos dev-base image already ships uv/Python and Docker CLI.

Acceptance criteria:

  • Run the test and publish jobs in the pinned aos dev-base image.
  • Remove astral-sh/setup-uv and Docker CLI tarball install where dev-base supplies those tools.
  • Keep Helm setup bounded, or remove it only after the central dev-base expansion adds Helm.
  • Preserve chart validation, image tagging, and push behavior.
The dev-base scan found `.forgejo/workflows/build-publish.yml` using `astral-sh/setup-uv`, `azure/setup-helm`, and a runtime Docker CLI tarball install. The pinned aos dev-base image already ships uv/Python and Docker CLI. Acceptance criteria: * Run the test and publish jobs in the pinned aos dev-base image. * Remove `astral-sh/setup-uv` and Docker CLI tarball install where dev-base supplies those tools. * Keep Helm setup bounded, or remove it only after the central dev-base expansion adds Helm. * Preserve chart validation, image tagging, and push behavior.
Author
Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-lunch-money-k8s-25 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T03:54:39Z). 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-flight-deck/lunch-money-k8s#25 · branch issue-25 · harness codex · workflow pr
  • Run: engineer-codex-lunch-money-k8s-25 · ward v0.470.0 · dispatched 2026-07-09T03:54:39Z
  • 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-lunch-money-k8s-25` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T03:54:39Z). 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-flight-deck/lunch-money-k8s#25` · branch `issue-25` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-lunch-money-k8s-25` · ward `v0.470.0` · dispatched `2026-07-09T03:54:39Z` - **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`
Author
Member

WARD-OUTCOME: done - build-publish now runs test and publish in pinned aos dev-base.
Review gate skipped because --skip-preflight / --no-preflight also skips review.
The workflow change was straightforward, but the docs cap forced a second pass to tighten wording. Confidence is good; the only rough edge I’d file is whether Forgejo’s runner keeps container networking stable for the publish job.

WARD-OUTCOME: done - build-publish now runs test and publish in pinned aos dev-base. Review gate skipped because --skip-preflight / --no-preflight also skips review. The workflow change was straightforward, but the docs cap forced a second pass to tighten wording. Confidence is good; the only rough edge I’d file is whether Forgejo’s runner keeps container networking stable for the publish job.
Author
Member

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

  • Repo: coilyco-flight-deck/lunch-money-k8s
  • Salvage branch: ward-salvage/lunch-money-k8s-fa27a0c5
  • 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: 5m (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:              39c26c89879f
origin/main:       1d166a1766ad
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:  5m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-k8s.git ward-salvage/lunch-money-k8s-fa27a0c5
git checkout -b ward-salvage/lunch-money-k8s-fa27a0c5 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 #25 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/lunch-money-k8s` - **Salvage branch:** `ward-salvage/lunch-money-k8s-fa27a0c5` - **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:** 5m (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: 39c26c89879f origin/main: 1d166a1766ad 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: 5m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-k8s.git ward-salvage/lunch-money-k8s-fa27a0c5 git checkout -b ward-salvage/lunch-money-k8s-fa27a0c5 FETCH_HEAD ``` <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
No description provided.