fix(release): publish roboco-agent-kimi — v0.28.0 shipped without it

The kimi provider (#713) added docker/agent-kimi.Dockerfile and the
agent-kimi-image pull stanza in docker-compose.registry.yml, but never
the entry in release.yml's build/push map — the exact regression class
the map's own history records for the grok sub-images. v0.28.0
published every image except kimi and its pull-smoke job went red on
precisely that pull; the red run went unactioned. The image is
backfilled to both registries manually for :0.28.0/:latest; this entry
covers every future release.

.github/workflows/release.yml

@@ -122,6 +122,12 @@ jobs:
             # (unlike roboco-agent-grok above) it needs no special build-order
             # carve-out and is just another entry here.
             [roboco-agent-gemini]=docker/agent-gemini.Dockerfile
+            # Kimi (Moonshot, official kimi-code CLI) — same shape as gemini/
+            # codex: one-shot delivery roles only, plain FROM agent-base.
+            # Missing from this map on v0.28.0 shipped the release without the
+            # image; pull-smoke went red on exactly that pull. Every new
+            # docker/agent-*.Dockerfile MUST land here in the same PR.
+            [roboco-agent-kimi]=docker/agent-kimi.Dockerfile
           )
           for name in "${!IMAGES[@]}"; do
             echo "::group::build ${name}"