Retire the standalone lunch-money-k8s deploy (superseded by deploy/services/lunch-money-mcp) #22

New issue

Closed

opened 2026-07-06 17:45:41 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-06 17:45:41 +00:00

Owner

Follow-up from coilyco-bridge/deploy#50.

The lunch-money MCP now deploys from the fleet monorepo at coilyco-bridge/deploy under services/lunch-money-mcp/, behind the standard Authelia at+jwt gate (public at https://lunch-money.coilysiren.me/mcp for the claude.ai connector, tailnet-direct at kai-server:30080). That bundle is the deploy surface going forward; this repo keeps only the application source (Dockerfile, lunch_money_mcp/, its Docker Hub CI).

Once the deploy-repo bundle is confirmed serving, retire the standalone deploy machinery here:

Remove the chart/ Helm chart and examples/values-homelab.yaml (the deploy repo owns the k8s manifest now).
Trim docs/deploy.md / docs/chart.md to point at coilyco-bridge/deploy's services/lunch-money-mcp/ instead of documenting an in-repo install.
Keep the image build + docs/FEATURES.md for the app itself; only the deploy machinery leaves.

Do not delete anything until the deploy-repo roll is verified (image mirrored, SSM params in place, pod Ready, 401/200 verify green).

Follow-up from coilyco-bridge/deploy#50. The lunch-money MCP now deploys from the fleet monorepo at `coilyco-bridge/deploy` under `services/lunch-money-mcp/`, behind the standard Authelia `at+jwt` gate (public at `https://lunch-money.coilysiren.me/mcp` for the claude.ai connector, tailnet-direct at `kai-server:30080`). That bundle is the deploy surface going forward; this repo keeps only the application source (Dockerfile, `lunch_money_mcp/`, its Docker Hub CI). Once the deploy-repo bundle is confirmed serving, retire the standalone deploy machinery here: - Remove the `chart/` Helm chart and `examples/values-homelab.yaml` (the deploy repo owns the k8s manifest now). - Trim `docs/deploy.md` / `docs/chart.md` to point at `coilyco-bridge/deploy`'s `services/lunch-money-mcp/` instead of documenting an in-repo install. - Keep the image build + `docs/FEATURES.md` for the app itself; only the deploy machinery leaves. Do not delete anything until the deploy-repo roll is verified (image mirrored, SSM params in place, pod Ready, 401/200 verify green).

coilyco-ops added the

consult

labels

2026-07-07 04:08:50 +00:00

coilyco-ops commented

2026-07-09 21:10:38 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-lunch-money-k8s-22 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T21:10:35Z). 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#22 · branch issue-22 · harness codex · workflow direct-to-main
Run: engineer-codex-lunch-money-k8s-22 · ward v0.501.0 · dispatched 2026-07-09T21:10:35Z
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.501.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-lunch-money-k8s-22` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T21:10:35Z). 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#22` · branch `issue-22` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-lunch-money-k8s-22` · ward `v0.501.0` · dispatched `2026-07-09T21:10:35Z` - **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.501.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 21:16:07 +00:00

refactor: retire standalone deploy surface

coilyco-ops closed this issue

2026-07-09 21:16:07 +00:00

coilyco-ops commented

2026-07-09 21:16:22 +00:00

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default)
retrospective: the retire-and-doc pass felt straightforward after tracing the remaining chart references. The only surprise was ward's clean-tree gate, which required an audited override for validation before the commit.
confidence: high
follow-ups: none.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) retrospective: the retire-and-doc pass felt straightforward after tracing the remaining chart references. The only surprise was ward's clean-tree gate, which required an audited override for validation before the commit. confidence: high follow-ups: none. </details>