feat(mumble F2-14c): drop cc-ci compose.host-ports.yml fork; deploy 0.2.0 base minimally, add native host-ports on upgrade-to-latest via new UPGRADE_EXTRA_ENV harness hook + COMPOSE_FILE-aware READY_PROBE/install skip

runner/harness/generic.py

@@ -18,7 +18,7 @@ import socket
 import ssl
 import time
 
-from . import lifecycle
+from . import abra, lifecycle
 
 # A recipe is backup-capable iff a compose file carries a truthy backupbot.backup label.
 _BACKUPBOT_RE = re.compile(r"backupbot\.backup\b[^\n]*\btrue\b", re.IGNORECASE)
@@ -244,6 +244,17 @@ def perform_upgrade(
     before = lifecycle.deployed_identity(domain)
     if head_ref:
         lifecycle.recipe_checkout_ref(recipe, head_ref)
+    # UPGRADE_EXTRA_ENV (F2-14c): a recipe may need different app .env for the upgrade-TARGET deploy
+    # than for the base — e.g. mumble's `compose.host-ports.yml` overlay exists ONLY in the newer
+    # (target) version, so the base deploys minimally WITHOUT it and the upgrade adds it to COMPOSE_FILE
+    # here, after the PR-head checkout (which ships the overlay) and before the chaos redeploy that
+    # picks up the new .env. Dict or callable(domain)->dict. No-op for recipes without it.
+    upgrade_env = meta.get("UPGRADE_EXTRA_ENV") or {}
+    if callable(upgrade_env):
+        upgrade_env = upgrade_env(domain) or {}
+    for k, v in upgrade_env.items():
+        print(f"  upgrade-env: {k}={v}", flush=True)
+        abra.env_set(domain, k, v)
     # HQ1: warm the NEW-version image set before the chaos redeploy (the head_ref checkout's pinned
     # tags) so a pull failure is a clear pre-deploy error and convergence isn't pull-bound.
     lifecycle.prepull_images(recipe, domain)