Repo name does not match the image it publishes, so deploy cannot watch its pin #39

New issue

Open

opened 2026-08-12 21:32:49 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 21:32:49 +00:00

Owner

Observed

This repo publishes its container as
forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp, which
coilyco-bridge/deploy pulls. The repository is named lunch-money-k8s, and
coilyco-flight-deck/lunch-money-mcp is a 404 as a repository.

Every other service in the fleet has image path equal to owner/repo.

Why it surfaced

coilyco-bridge/deploy reconciles image pins by deriving the source repo from
the image path. This repo breaks that convention, so its pin cannot be watched:

lunch-money-mcp: forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp
                 has no resolvable upstream at
                 https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp.git

Before coilyco-bridge/deploy#410 that was
silent. It is now reported by name and deferred every tick, but the deployed
pin still never advances on its own.

Wanted

Rename the repository to lunch-money-mcp to match the image and the service
name deploy already uses. -k8s describes how it ships rather than what it is,
and the repo's own description leads with the MCP server.

The image path and the deploy side need no change. Once the repo resolves, the
reconciler picks it up.

Renaming needs the usual care for anything referencing the old name: the
repo-registry and catalog outputs in coilyco-bridge/agentic-os-kai, any skill
pointer, and local clones.

## Observed This repo publishes its container as `forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp`, which `coilyco-bridge/deploy` pulls. The repository is named `lunch-money-k8s`, and `coilyco-flight-deck/lunch-money-mcp` is a 404 as a repository. Every other service in the fleet has image path equal to `owner/repo`. ## Why it surfaced `coilyco-bridge/deploy` reconciles image pins by deriving the source repo from the image path. This repo breaks that convention, so its pin cannot be watched: ``` lunch-money-mcp: forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp has no resolvable upstream at https://forgejo.coilysiren.me/coilyco-flight-deck/lunch-money-mcp.git ``` Before https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/410 that was silent. It is now reported by name and deferred every tick, but the deployed pin still never advances on its own. ## Wanted Rename the repository to `lunch-money-mcp` to match the image and the service name deploy already uses. `-k8s` describes how it ships rather than what it is, and the repo's own description leads with the MCP server. The image path and the deploy side need no change. Once the repo resolves, the reconciler picks it up. Renaming needs the usual care for anything referencing the old name: the repo-registry and catalog outputs in `coilyco-bridge/agentic-os-kai`, any skill pointer, and local clones.

coilyco-ops added the

role/sysadmin

priority

labels

2026-08-25 08:11:53 +00:00

coilyco-ops added the

autonomy

async-consult

label

2026-08-25 09:31:03 +00:00