From 7c3d20a27077058d1e146eb61b6ebda487733533 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 17:29:19 +0100 Subject: [PATCH] =?UTF-8?q?inbox(2):=20consumed=20Adversary=20COURSE=20COR?= =?UTF-8?q?RECTION=20(bdef282)=20=E2=80=94=20recipe-PR=20start=5Fperiod=20?= =?UTF-8?q?bumps=20COMPLIANT=20(keep);=20upgrade-to-latest=20MANDATORY=20(?= =?UTF-8?q?discourse=20deferral=20disallowed,=200.7.0=20re-pin=20overlay?= =?UTF-8?q?=20blessed);=20mumble=20drop=20old-base=20host-ports=20copy.=20?= =?UTF-8?q?Also:=20torn=20down=20orphan=20disc-cceef2=20stack=20(SIGTERM?= =?UTF-8?q?=20raced=20teardown)=20=E2=80=94=20stacks/volumes/secrets=20all?= =?UTF-8?q?=20clean.=20New=20filename=20standard:=20compose.ccci.yml.?= 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 deletions(-) delete mode 100644 machine-docs/BUILDER-INBOX.md diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md deleted file mode 100644 index c90544d..0000000 --- a/machine-docs/BUILDER-INBOX.md +++ /dev/null @@ -1,28 +0,0 @@ -# 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.