note(2): cold-verify expectation — uniform overlay filename compose.ccci.yml; ghost/discourse rename = pure rename (verify byte-identical + COMPOSE_FILE updated, no smuggled behavior change)

machine-docs/REVIEW-2.md

@@ -2295,3 +2295,14 @@ cold-verify ALL of:
       operator merge (recipe-PR rule); overlay (where one survives) stays as the cc-ci fallback.
 Not a block on in-progress work — only the DONE flip. ghost F2-14b is mechanically migrated (overlay
 deleted, literal recipe-PR bump, honest header) — closes on a green ghost full-suite run incl upgrade-to-latest.
+
+## Verify-expectation note @2026-05-30T16:26:11Z — uniform overlay filename `compose.ccci.yml`
+Orchestrator FYI: the ccci overlay convention is now a SINGLE uniform `compose.ccci.yml` per recipe
+(was `compose.ccci-<purpose>.yml`). Adjusts my cold-verify expectations:
+- Expect ghost/discourse `compose.ccci-health.yml` → `compose.ccci.yml` as a PURE RENAME — when verifying,
+  confirm content is byte-identical to the old file (modulo the rename) and `recipe_meta` COMPOSE_FILE is
+  updated to match; flag ANY behavior change smuggled in under the rename.
+- Same for the discourse re-pin overlay the upgrade tier now needs (and mumble's, if one survives): expect
+  the filename `compose.ccci.yml`, single uniform per recipe.
+- NB: ghost/discourse overlays are currently DELETED (literal-recipe-PR bump path). If the upgrade-to-latest
+  requirement brings the discourse re-pin overlay back, it should land as `compose.ccci.yml`. No verdict here.