Remove the retired Helm chart from the build-publish gate #28

New issue

Closed

opened 2026-07-23 08:22:11 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-23 08:22:11 +00:00

Owner

Failure

Forgejo Actions run 53 failed in the Helm job:

https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-k8s/actions/runs/53/jobs/1/attempt/1

Error unable to check Chart.yaml file in chart: stat chart/Chart.yaml: no such file or directory

This is a stale CI contract, not a missing-file accident. docs/chart.md says the repository no longer ships a standalone Helm chart and points deployment ownership to coilyco-bridge/deploy/services/lunch-money-mcp/. The refactor removed Chart.yaml and values files but left:

the helm job in .forgejo/workflows/build-publish.yml
publish.needs: [test, helm]
orphaned templates under chart/templates/
template commands referring to a missing examples/values-homelab.yaml

The publish job has therefore been blocked since the standalone deploy surface was retired. The Telegram timeout is secondary.

Scope

Remove the retired Helm validation job and its dependency from the image publish DAG.
Remove orphaned chart-only files if they have no remaining source-level purpose.
Keep Kubernetes deployment ownership in the deploy repository.
Update the feature inventory and docs so source-image ownership and deploy ownership are consistent.
Preserve the app test gate before image publication.

Acceptance

The source test job remains required for publish.
No source-repo CI step expects a standalone Helm chart.
Orphaned chart references are removed or deliberately documented.
The build-publish workflow reaches the image publish job and is green.

## Failure Forgejo Actions run 53 failed in the Helm job: https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-k8s/actions/runs/53/jobs/1/attempt/1 ```text Error unable to check Chart.yaml file in chart: stat chart/Chart.yaml: no such file or directory ``` This is a stale CI contract, not a missing-file accident. `docs/chart.md` says the repository no longer ships a standalone Helm chart and points deployment ownership to `coilyco-bridge/deploy/services/lunch-money-mcp/`. The refactor removed `Chart.yaml` and values files but left: - the `helm` job in `.forgejo/workflows/build-publish.yml` - `publish.needs: [test, helm]` - orphaned templates under `chart/templates/` - template commands referring to a missing `examples/values-homelab.yaml` The publish job has therefore been blocked since the standalone deploy surface was retired. The Telegram timeout is secondary. ## Scope - Remove the retired Helm validation job and its dependency from the image publish DAG. - Remove orphaned chart-only files if they have no remaining source-level purpose. - Keep Kubernetes deployment ownership in the deploy repository. - Update the feature inventory and docs so source-image ownership and deploy ownership are consistent. - Preserve the app test gate before image publication. ## Acceptance - The source test job remains required for publish. - No source-repo CI step expects a standalone Helm chart. - Orphaned chart references are removed or deliberately documented. - The build-publish workflow reaches the image publish job and is green.

coilyco-ops commented

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

Author

Owner

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-lunch-money-k8s-28 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-23T08:23:15Z). 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/lunch-money-k8s#28 · branch issue-28 · harness codex · workflow merge-remote-main
Run: engineer-codex-lunch-money-k8s-28 · ward v0.793.0 · dispatched 2026-07-23T08:23:12Z
Reservation: held
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.793.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-lunch-money-k8s-28` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-23T08:23:15Z). 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/lunch-money-k8s#28` · branch `issue-28` · harness `codex` · workflow `merge-remote-main` - **Run:** `engineer-codex-lunch-money-k8s-28` · ward `v0.793.0` · dispatched `2026-07-23T08:23:12Z` - **Reservation:** held - **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.793.0). </details> </details>  — Codex, via `ward agent`