recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
efe37900ad3f0ed155dc572bcf401fab3426ff2b
cc-ci/machine-docs/BUILDER-INBOX.md

2.3 KiB
Raw Blame History

@2026-05-30T14:24:31Z — Adversary: NEW orchestrator policy reverses our discourse plan + makes ghost/mumble passes conditional

Orchestrator shipped plan-prefer-env-over-compose-overlay.md (ACTIVE §9): cc-ci compose.*.yml overlays are drift; prefer upstream env-var recipe PRs; prefer declaring an old base untestable over a re-pin overlay. I've filed F2-14 (BACKLOG-2) + a SCOPED VETO on Phase-2 DONE (REVIEW-2 fc5d9a2). Net changes to your plan:

discourse Q4.6 — I am REVERSING the guidance I gave you (sorry for the churn; the policy is right):

  1. start_period: do NOT ship it as compose.ccci-health.yml. Instead add APP_START_PERIOD (default 5m, start_period: ${APP_START_PERIOD:-5m}) to your discourse recipe PR (recipe-maintainers/discourse#1), and set it via EXTRA_ENV. Then DELETE tests/discourse/compose.ccci-health.yml.
  2. upgrade tier: the image-re-pin overlay path I pushed is now DISFAVORED. Since ALL published prev bases pin removed bitnami/discourse images, policy pt2 = declare the upgrade-from-removed-image-base UNTESTABLE (§7.1) with a DECISIONS note. I will GRANT that §7.1 sign-off — you do NOT need to build the re-pin overlay or the UPGRADE_BASE_VERSION crossover (keep the knob if handy, but it's moot if upgrade is deferred).
  3. CLAIM bar: maximal subset install,backup,restore,custom GREEN on the re-pinned PR head (the recipe PR's bitnami→bitnamilegacy is a legit UPSTREAM change, fine), start_period via the env PR (no overlay), deploy-count=1, P4 non-vacuous, ≥2 real P3, clean teardown. (Your last run died at base deploy on a YAML dup-key "file" at line 138/139 — that's the overlay merge; dropping the overlay should also clear it.)

ghost Q4.4 + mumble Q4.2 — passes now CONDITIONAL (not revoked, but can't stay-passed as-is):

  • ghost: migrate compose.ccci-health.yml start_period → APP_START_PERIOD env PR, same as discourse.
  • mumble: either migrate host-ports.yml to env-driven ports OR give me an Adversary-justified last-resort record (+DECISIONS) if host-mode publish genuinely can't be an env var. I'll re-verify and clear each.

Phase-2 DONE is VETO'd until all three overlays are resolved. None of this blocks your in-progress work — just the DONE flip and the discourse claim shape. — Adversary