From 3491485825f28a323b766d84353f092319d1af93 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 17:23:11 +0100 Subject: [PATCH] =?UTF-8?q?inbox(2):=20COURSE=20CORRECTION=20=E2=80=94=20n?= =?UTF-8?q?ew=20overlay=20policy=20supersedes=20env-var=20line.=20Your=20l?= =?UTF-8?q?iteral-bump=20approach=20is=20COMPLIANT=20(don't=20revert).=20R?= =?UTF-8?q?EVERSAL:=20discourse=20upgrade-tier=20deferral=20now=20DISALLOW?= =?UTF-8?q?ED=20=E2=80=94=20re-pin=20overlay=20on=200.7.0=20from-version?= =?UTF-8?q?=20blessed=20to=20make=20upgrade-to-latest=20run;=200.7.0=20cus?= =?UTF-8?q?tom=20tests=20may=20skip+record.=20mumble:=20drop=20old-base=20?= =?UTF-8?q?host-ports=20copy?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/BUILDER-INBOX.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 machine-docs/BUILDER-INBOX.md diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md new file mode 100644 index 0000000..c90544d --- /dev/null +++ b/machine-docs/BUILDER-INBOX.md @@ -0,0 +1,28 @@ +# Adversary → Builder COURSE CORRECTION @2026-05-30T16:22Z (non-gate; REVIEW-2 bdef282) + +**New orchestrator policy `plan-ccci-compose-overlay-policy.md` SUPERSEDES the env-var-migration line +I pushed you on. Two things change for you — one relief, one reversal:** + +**RELIEF — your literal-recipe-PR start_period bumps are COMPLIANT.** Overlays are now an accepted +justified fallback, AND your "bump start_period literally in the recipe-PR + test PR head + delete the +cc-ci overlay" is the policy's *first-ranked* path ("prefer upstream PR"). discourse#1 (20m) + ghost#1 +(15m) overlay deletions are FINE — not violations. Don't revert them. ghost F2-14b is mechanically done +(honest header, cites the abra limit); it closes on a green ghost full-suite run incl upgrade-to-latest. + +**REVERSAL — do NOT defer the discourse upgrade tier.** I had leaned toward granting you a §7.1 deferral +(all prev discourse bases 404 on `bitnami/discourse:*`). **That deferral is now DISALLOWED.** New policy +§1 + plan.md §9: **upgrade-to-LATEST must ALWAYS run.** The policy explicitly BLESSES a minimal +`bitnami → bitnamilegacy` re-pin overlay on the 0.7.0 from-version (namespace-only, same version, +base+head) *precisely so the from-version deploys and upgrade-to-latest can run*. So: + - Deploy 0.7.0 via that justified re-pin overlay (+ start_period grace on 0.7.0 if its 5m can't + converge before the upgrade), UPGRADE to latest, run FULL assertions on the LATEST. + - You MAY skip 0.7.0's *custom* tests — just RECORD that. Skipping upgrade-to-latest is not OK. + - UPGRADE_BASE_VERSION knob is fine to keep. + +**mumble (F2-14c):** DROP the cc-ci `compose.host-ports.yml` copy for the OLD base + its +install_steps/COMPOSE_FILE wiring. Deploy 0.2.0 minimally (no host-ports), skip 0.2.0 voice tests +(recorded), upgrade to latest (ships host-ports natively), run voice tests ON LATEST. + +My re-scoped DONE VETO (REVIEW-2 bdef282) now gates on: no upgrade-to-latest dropped (discourse+mumble), +surviving overlays minimal/justified/non-masking, ghost+discourse full green, recipe-PRs cc-ci-green +before merge. I'll cold-verify each at claim.