75f66550e2
Builder asked me to confirm or refute that the _assert_slot_not_foreign x B-redfix-5 composition reaches the UPGRADE path, not only the rollback path I named. Re-derived cold from source at b5f2b10; confirmed. - snapshot() calls the guard FIRST (warmsnap.py:158, before _assert_undeployed) -> raises before docker. - warm_reconcile.py:511-514 (undeploy -> wait_undeployed -> snapshot) is OUTSIDE the try/except at :520-525, which wraps only deploy_version + wait_healthy. Neither abra.undeploy site (:512, :534) is covered. - No enclosing try in reconcile(); sole caller main():556 does not catch -> SystemExit, no redeploy. The app stays undeployed. - Site (a) is strictly more reachable than site (b): snapshot() runs on EVERY stateful auto-upgrade; restore() only after an unhealthy release. Builder's "no unhealthy release needed" is correct. - Arming condition is real: keycloak has WARM_CANONICAL=True at07fc6d4too, so one pre-fix seed writes domain=warm-canon-keycloak into the bare-recipe slot and arms BOTH sites post-merge. - Blast radius exactly one unit: keycloak is the only WARM_DOMAINS member and the only stateful SPEC. Probe with the reconciler's exact args: site (a) raises SnapshotError before docker (CONFIRMED); an unclaimed slot passes the guard (why it's unreachable on cc-ci today); site (b) dies on docker at _assert_undeployed (:205) upstream of the guard (:209) — independently reproducing the Builder's probe caveat, same class as the e3b0c44298fc1c14 empty-input tell. Accept the correction thatb5f2b10ADDS a raise path rather than only closing one; what makes it unreachable today is node state, not F-redfix-4's closure. Verdict: do not revert the widening. Precondition stands and covers both sites. Merge targetb5f2b10unchanged. M1+M2 PASS stand, DONE stands, no VETO. B-redfix-5 deferred (now correctly scoped); B-redfix-8 unchanged. ADVERSARY-INBOX consumed + deleted. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SoraVF2hkEMExHswFX1g4M
cc-ci — Co-op Cloud recipe CI server
Comment !testme on a PR in an enrolled Co-op Cloud recipe repo and cc-ci deploys the recipe
at that commit onto a real single-node Docker Swarm, runs install / upgrade / backup-restore tests
(Python + Playwright) end-to-end, and reports a live, tail-able run with pass/fail back to the PR.
This repo declares the entire server as a NixOS flake and holds the test harness, the per-recipe test trees, and the docs to enroll a recipe or rebuild the box from scratch.
Status: under active autonomous construction. See
machine-docs/STATUS.mdfor the live phase andplan.md-driven milestones inmachine-docs/BACKLOG.md. Definition of Done is D1–D10 (see the build plan).
Layout
flake.nix NixOS entry point + devshells (`#cc-ci` = live Hetzner host, `#cc-ci-incus` = legacy Incus host)
nix/hosts/cc-ci/ legacy Incus VM host config (fallback / historical)
nix/hosts/cc-ci-hetzner/ live Hetzner host config
nix/modules/ drone, comment-bridge, swarm, dashboard, secrets (Nix modules)
secrets/ sops-encrypted infra secrets (cc-ci-secrets submodule)
bridge/ !testme webhook listener source
runner/ run_recipe_ci.py + shared pytest harness
dashboard/ results overview generator
tests/<recipe>/ per-recipe install/upgrade/backup tests + custom/
docs/ install, enroll-recipe, secrets, architecture, runbook, baseline
All .nix code lives under nix/; flake.nix/flake.lock stay at the repo root. Host targets are:
#cc-ci= canonical live Hetzner server#cc-ci-hetzner= explicit alias for the same live Hetzner server#cc-ci-incus= legacy Incus VM definition only; do not use on Hetzner
Docs
docs/install.md— rebuild the server from scratch (D8)docs/testing.md— test architecture: generic lifecycle suite + layered recipe overlays (override/extend, discovery precedence, custom install-steps hook)docs/enroll-recipe.md— add a recipe under CI (D5)docs/secrets.md— secret model + rotation (D6)docs/architecture.md,docs/runbook.md— design + debugging failed runsdocs/baseline.md— bootstrap snapshot / rollback reference
Linting & formatting
The codebase is kept formatted + lint-clean by a single entrypoint, run from the pinned lint
devshell so local and CI use identical tool versions:
nix develop .#lint --command bash scripts/lint.sh # check-only (what CI runs)
nix develop .#lint --command bash scripts/lint.sh --fix # auto-format + apply fixes
Covers Nix (nixpkgs-fmt · statix · deadnix), Python (ruff lint+format), Shell
(shellcheck · shfmt), and YAML (yamllint). Config lives in ruff.toml / .yamllint.yaml;
tool/strictness choices are in machine-docs/DECISIONS.md. CI enforces it: the lint step in the
.drone.yml push pipeline runs the same command and fails the build on any unclean file, so
keep commits clean (--fix before pushing).
Loop state (autonomous build)
The multi-agent loop state lives under machine-docs/: STATUS.md (phase/blockers),
BACKLOG.md (work + adversary findings), REVIEW.md (independent verification), JOURNAL.md
(build log), DECISIONS.md (architecture choices) — plus the phase-namespaced *-1b.md / *-1c.md
variants. See the build plan for the two-loop Builder/Adversary protocol.