100 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
autonomic-bot	bdc2ec4773	decisions(canon): gitea 3.6.0 warm-advance exception (app.ini read-only, recipe issue; 3.5.3 valid) + M2.3 determinism framing	2026-06-17 12:19:04 +00:00
autonomic-bot	9ffbba57e3	review(canon): authoritative sweep DONE rc=0 @12:00:03Z (single serial, 11:25:57->12:00:03); determinism preview visible (promoted recipes SKIP); awaiting gitea fix + M2.3/5/6/7/8 proofs before claim	2026-06-17 12:10:44 +00:00
autonomic-bot	930335972a	chore(canon): consume BUILDER-INBOX (gitea 3.6.0 advance — fixing; drone promoted clean)	2026-06-17 12:00:53 +00:00
autonomic-bot	a6c506844a	review+inbox(canon): final-sweep crux — drone PROMOTED CLEAN (residue fix works, DEFECT-2 closing) but gitea 3.6.0 advance FAILED AGAIN (GREEN-BUT-PROMOTE-FAILED, canon kept 3.5.3) → CLAIM-BLOCKER for M2.6 (advance undemonstrated) + M2.3 (green recipe re-runs, not a red); heads-up sent	2026-06-17 11:59:14 +00:00
autonomic-bot	35d629452b	decisions(canon): record 4 recipe RED exceptions (discourse upstream-compose / mattermost+mumble test-red / bluesky warm-routing) — genuine, tests unmodified, left intact	2026-06-17 11:37:33 +00:00
autonomic-bot	31fbed13b6	review(canon): CONFIRMED final authoritative sweep @12acf94 contains both ca89d44+d072d7e (recency criterion MET); list red-diagnosis verifications (discourse/mattermost-lts/mumble/bluesky) — verify genuine+not-weakened+DECISIONS-recorded at claim	2026-06-17 11:35:51 +00:00
autonomic-bot	2ce31b4035	status(canon): FINAL authoritative M2.2 sweep launched (post-fix /etc/cc-ci@12acf94, enrolled=20, serial); red diagnoses recorded	2026-06-17 11:26:19 +00:00
autonomic-bot	12acf94b91	review(canon): pre-fix sweep DONE (15 canonicals); NEW red mumble rc=1 (must fix-or-document); plausible promoted 3.1.0+v2.0.0 not 3.0.1 → §2.8 retirement must re-derive dynamic base vs actual canonical	2026-06-17 11:23:53 +00:00
autonomic-bot	32c9703ffe	review(canon): VERIFIED fresh-seed-teardown × live-keycloak footgun MITIGATED — keycloak de-enrolled (enrolled=20, not in set), live warm-keycloak 200 + 1/1 unharmed by pre-fix sweep; carry: check no other recipe domain collides with a live service	2026-06-17 11:12:25 +00:00
autonomic-bot	618ac1ef6f	status(canon): M2 snapshot — 10 clean promotes incl. lasuite-* (warm dep works); plan for authoritative post-fix sweep	2026-06-17 11:03:00 +00:00
autonomic-bot	3bcc11f7b5	review(canon): note residue fix (ca89d44, likely drone root cause) + keycloak de-enroll (d072d7e, §2.B exception, enrolled=20); set M2-evidence recency criterion — accepted sweep must postdate both fixes, single serial, drone promotes-or-exception	2026-06-17 11:00:24 +00:00
autonomic-botandClaude Opus 4.8	d072d7e2c2	fix(canon): de-enroll keycloak (live-warm OIDC provider) — §2.B exception ... keycloak is the always-on shared OIDC dep provider at warm-keycloak.ci..., the SAME stable domain a data-warm canonical would use → the sweep's promote would collide with the live provider that lasuite-*/drone depend on. keycloak is kept current by roll_warm_infra (WC1.1) instead. WARM_CANONICAL=False; exception recorded in DECISIONS. Enrolled set now 20. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 10:54:14 +00:00
autonomic-botandClaude Opus 4.8	ca89d44c05	fix(canon): promote clears stale warm-stack on a fresh seed (failed-promote secret residue) ... A once-failed promote left swarm secrets (e.g. drone's gitea client_secret_v1) behind; the retry's install_steps 'abra app secret insert' then FATAd 'already exists', so a recipe could never recover its canonical. promote_canonical now teardown_app()s the warm domain when there is NO existing canonical (fresh seed) — clearing leftover secrets/.env/partial volumes — while a re-promote (canonical exists) still reattaches its retained known-good volume untouched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 10:51:01 +00:00
autonomic-bot	d32940d3e1	review(canon): clean-serial sweep obs — drone STILL promote-fails clean (lock fix cured hang, not promote; M2 risk); gitea new-tag 3.5.3->3.6.0 advance = live M2.6 evidence	2026-06-17 10:48:12 +00:00
autonomic-bot	d4a053dfcc	chore(canon): consume ADVERSARY-INBOX (concurrent sweeps killed, drone tainted-canonical discarded, ONE clean serial sweep relaunched pid1741209); carry to claim — verify 7 kept canonicals' ts outside concurrency window	2026-06-17 10:25:01 +00:00
autonomic-bot	1f4aa25a2b	inbox+status(canon): killed concurrent sweeps, cleaned residue, cleared concurrency-tainted drone canonical; ONE clean serial sweep relaunched	2026-06-17 10:24:06 +00:00
autonomic-bot	fb2fe307dc	chore(canon): consume BUILDER-INBOX (concurrent-sweep alert — killing wedged old sweep, will re-run clean serial)	2026-06-17 10:21:42 +00:00
autonomic-bot	4d5b03b485	inbox+review(canon): TWO concurrent sweeps — wedged old sweep (PID1712141, drone deadlock child ~46m) still alive alongside new re-run (PID1736506); violates §4 serial + breaks release_app_locks precondition; M2 evidence from overlapping run not acceptable	2026-06-17 10:20:49 +00:00
autonomic-bot	88293702b2	status(canon): mirror-sync master-detection + cold-dep lock-release fixes deployed; validating drone	2026-06-17 10:05:13 +00:00
autonomic-botandClaude Opus 4.8	655a9998be	fix(canon): release cold-run app/dep locks before promote (cold-dep self-deadlock) ... drone (DEPS=[gitea], a COLD dep) deadlocked in promote: the cold test holds the gitea dep's app-lock for the whole process lifetime, and promote's _provision_deps re-acquires the same lock in the same process → blocks forever. By promote time the cold test + its deps are torn down (dep teardown runs in the run finally, before promote), so the locks are stale. New lifecycle.release_app_locks() frees them at promote start; the serial sweep guarantees no concurrent run relies on them. lasuite-* (warm keycloak dep) were unaffected (no cold deploy). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 10:04:14 +00:00
autonomic-botandClaude Opus 4.8	24579383f4	fix(canon): mirror-sync detects upstream default branch (master vs main) ... Adversary-flagged: drone/gitea mirror-sync hit rc=128 ('couldn't find remote ref main') — coopcloud/coop-cloud/{drone,gitea} use `master`, not `main`. The script hardcoded `git fetch upstream main` → sync skipped (non-fatal) so the mirror wasn't reconciled (the trigger still used correct upstream tags from the local abra-fetch clone, so the version tested was right; only the mirror push was missed). Now resolves the upstream HEAD symref and fetches that branch, force-pushing it to the mirror's `main`. Consumes BUILDER-INBOX. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 09:37:24 +00:00
autonomic-bot	d9987a0fbf	inbox(canon): heads-up to Builder before M2 claim — (1) drone mirror-sync rc=128 swallowed (clarify §2.C); (2) determinism run-twice-skip-all vs red/promote-failed recipes (reconcile in claim evidence)	2026-06-17 09:35:35 +00:00
autonomic-bot	4accd22d50	review(canon): pre-claim observations — DEFECT-1 label fix live/honest; NEW mirror-sync drone rc=128 swallowed (scrutinise §2.C); determinism M2.3 run-twice-skip-all at risk for red/promote-failed recipes	2026-06-17 09:35:11 +00:00
autonomic-bot	df26041307	chore(canon): consume ADVERSARY-INBOX (fix f94de22 validated, M2 re-run in flight); pre-claim note — scrutinise bluesky 'documented RED' as possible warm-domain routing machinery defect at claim	2026-06-17 09:12:01 +00:00
autonomic-bot	0eca8b5089	status+inbox(canon): promote fix validated (custom-html-tiny+ghost promote); bluesky warm-routing red; full re-run in flight	2026-06-17 09:11:07 +00:00
autonomic-bot	3393dba11e	review(M2.2): file DEFECT-1 (untrustworthy PASS label) + DEFECT-2 (promote path failing broadly) as OPEN adversary findings; close only after re-verify of fix f94de22	2026-06-17 08:55:31 +00:00
autonomic-bot	2126747e2e	status(canon): M2.2 run-1 surfaced+fixed promote bug; validating faithful-install fix	2026-06-17 08:51:49 +00:00
autonomic-botandClaude Opus 4.8	f94de22234	fix(canon): promote does a FAITHFUL warm install (clean tree + deps + install_steps) ... M2 finding (Adversary-flagged): promote_canonical did a bare `abra app deploy` that lacked the cold install's wiring, so recipes that passed the cold test still failed to promote: - ghost: `abra app new` FATA 'locally unstaged changes' — the CCCI_SKIP_FETCH per-run tree was left dirty by the tier suite. Fix: force re-checkout the tag + `git clean -fd` before deploy. - bluesky-pds: missing pds_plc_rotation_key (install_steps inserts it, #generate=false). - custom-html-tiny: 404 (install_steps seeds index.html). Fix: run install_steps_hook in promote. - OIDC recipes would miss their realm. Fix: provision DEPS in promote like the cold install. promote_canonical now: clean tree → provision deps → deploy_app with install_steps_hook + overlay + ready-probes, then snapshot. Also: sweep result label now derives from whether the canonical was actually written (promote is non-fatal; rc==0 did not imply promoted) — fixes the misleading 'PASS (promoted)'. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 08:50:59 +00:00
autonomic-bot	4cf1b32f4c	chore(canon): consume BUILDER-INBOX (promote failing ~4/5 + misleading PASS label — diagnosing)	2026-06-17 08:41:28 +00:00
autonomic-bot	d933585e92	note(canon): pre-claim finding — sweep PASS-label vs actual promote failures (4/5), determinism risk; evidence captured for M2 verification	2026-06-17 08:40:41 +00:00
autonomic-bot	ba28a8897a	inbox(canon): heads-up — sweep logs PASS(promoted) but 4/5 promotes FAILED (only cryptpad wrote a canonical); label derives from rc not record; determinism M2.3 at risk	2026-06-17 08:40:16 +00:00
autonomic-bot	0f2f57b5ca	chore(canon): consume BUILDER-INBOX (discourse wedge heads-up; will time out → RED → sweep continues)	2026-06-17 08:17:27 +00:00
autonomic-bot	7ca77f95ca	inbox(canon): heads-up — M2.2 sweep stuck on discourse ~51m (abra deploy hung, 0 containers, ~08:24Z timeout); canonical count 2	2026-06-17 08:15:59 +00:00
autonomic-bot	38f9c8a30a	note(canon): pre-claim — M2.1 deploy verified live read-only (/etc/cc-ci pulled to 3bdd5d1, weekly timer deployed, sweep runs non-hollow path); M2 not yet claimed	2026-06-17 07:20:47 +00:00
autonomic-bot	7a08f05d59	chore(canon): consume ADVERSARY-INBOX (M1 PASS ack'd; Builder starting M2.2 long sweep)	2026-06-17 07:20:07 +00:00
autonomic-bot	b619e8168f	inbox(canon): heads-up — M2.1 deployed; starting long M2.2 full sweep	2026-06-17 07:19:20 +00:00
autonomic-bot	3bdd5d143b	review(M1): PASS — tagged-gate + trigger + mirror-sync + all-21-enrolled + weekly timer cold-verified; live canonical records tag commit df2e273; 295 unit pass from fresh clone. No VETO	2026-06-17 07:11:34 +00:00
autonomic-bot	8a52c16abb	journal(canon): M2-prep recon — 20 recipes will seed, runtime/disk risks noted	2026-06-17 07:08:50 +00:00
autonomic-botandClaude Opus 4.8	626badd333	claim(M1): canonical sweep machinery built + live-proven on custom-html ... M1 (machinery works locally, each piece proven) — code HEAD d4cc9e4, unit suite 295 passed: - M1.1 tagged-promote gate + promote-tested-version: live proof-A wrote a fresh canonical (commit df2e273 = the tag commit, correcting samever's main-HEAD 2b82eba); live proof-C green-untagged → 0 promotes, canonical byte-identical (tagged-gate blocks untagged). - M1.2 sweep_decision (version-keyed trigger) + vendored faithful recipe-mirror-sync.sh (smoke-tested: faithful no-op main/tags push, closed merged-upstream PR #2, left PR #5); nightly_sweep rewritten (mirror_sync -> trigger -> run_on_tag). Live SKIP demo on custom-html. - M1.3 all 21 used-recipes enrolled. M1.4 hollow-sweep fix (CCCI_REPO=/etc/cc-ci). M1.5 weekly timer. - M1(A) reattach: live proof-B --quick reused the retained volume green; known-good unchanged. Evidence + verify recipes in STATUS-canon.md; reasoning in JOURNAL-canon.md; DECISIONS appended. Gate: M1 CLAIMED, awaiting Adversary. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 07:07:44 +00:00
autonomic-bot	69f59fdcc5	status(canon): M1 code complete + unit-tested; live M1(A) proofs in flight	2026-06-17 06:49:53 +00:00
autonomic-botandClaude Opus 4.8	d4cc9e4530	fix(canon): promote the TESTED release version, not a re-derived latest tag ... Closes the head_version-vs-latest_version divergence: should_promote gates on head_version (code under test) but promote_canonical recorded latest_version(recipe_tags). In a manual RECIPE=<r> run whose main checkout sits on a tag OLDER than the newest published tag, the gate would pass on the older tag yet promote the newer (never-tested) one. promote_canonical now takes the tested `version` (head_version, guaranteed a release tag by the tagged-gate) and records exactly that. Sweep path unaffected (head==tag by construction). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:47:33 +00:00
autonomic-botandClaude Opus 4.8	a20890a363	feat(canon): M1.2 release-tag trigger + faithful mirror-sync in the weekly sweep (§2.C/§2.D) ... - warm_reconcile.sweep_decision(latest_tag, canon_version): pure new-release-tag trigger keyed on version_key (NOT commit) — new tag>canon → run; ==/older → skip no-new-version (even with untagged main commits); no tag → skip never-released. Unit-tested. - scripts/recipe-mirror-sync.sh: faithful mirror sync (adapted from open-recipe-pr.sh --reconcile-only) — explicit coopcloud `upstream` remote (robust to inconsistent clone remotes), syncs main+TAGS, closes merged-upstream PRs, leaves unrelated PRs, bot-token auth. - nightly_sweep rewritten: per enrolled recipe → mirror_sync → fetch → sweep_decision → run_on_tag (checkout the release tag + CCCI_SKIP_FETCH=1 so head IS the tag → tagged-promote gate passes, REF empty → promote allowed). Skips logged; run-twice → skip-all determinism. - smoke-tested recipe-mirror-sync.sh live on custom-html: faithful no-op main/tags push, closed merged-upstream PR #2, left pending PR #5. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:45:43 +00:00
autonomic-bot	f089c30040	chore(canon): pre-claim code-read notes (M1.1/1.3/1.4/1.5 landed; M1.2 outstanding; probe list)	2026-06-17 06:42:08 +00:00
autonomic-botandClaude Opus 4.8	f8c0e53521	feat(canon): M1.4 hollow-sweep fix + M1.5 weekly timer ... M1.4: run the sweep from the deployed checkout (CCCI_REPO=/etc/cc-ci, cd there, exec $CCCI_REPO/runner/nightly_sweep.py) instead of a nix-store runner copy. The store copy had no tests/, so enrolled_recipes() resolved TESTS_DIR to a missing dir and returned [] — the root cause of the hollow no-op sweep. /etc/cc-ci has runner/ AND tests/ and is the same checkout run_recipe_ci already runs from. M1.5: timer OnCalendar daily -> weekly (Sun 03:00 UTC), Persistent kept. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:37:39 +00:00
autonomic-botandClaude Opus 4.8	136100f610	feat(canon): M1.3 enroll all 21 used-recipes as data-warm canonicals (§2.B) ... WARM_CANONICAL=True added to every recipe in cc-ci-plan/used-recipes.md (20 weekly + uptime-kuma external). enrolled_recipes() now returns all 21. Test fixtures (custom-html-*-bad, concurrency, regression) intentionally left unenrolled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:35:30 +00:00
autonomic-botandClaude Opus 4.8	27e06289f8	feat(canon): M1.1 tagged-promote gate — canonical only advances to a published release tag ... - should_promote_canonical gains a `tagged` requirement (canon §2.A): a green cold latest run promotes only when the tested head version is a published release tag; an untagged main commit never becomes a canonical. - warm_reconcile.is_released_version(recipe, version): release-tag membership (exact or by version_key). Caller computes `tagged` so the gate stays pure. - unit tests: untagged -> no promote; is_released_version cases. - drive-by (pre-existing reds, unrelated to canon, now green): test_warm_reconcile traefik assertion was stale vs the phase-pxgate spec (probes /api/version, no health_domain); meta.py UPGRADE_BASE_VERSION KEYS help synced to the prevb doc text. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:34:09 +00:00
autonomic-botandClaude Opus 4.8	23c02c59b6	status(canon): bootstrap phase canon — state files, hollow-sweep root cause, M1/M2 backlog ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 06:28:35 +00:00
autonomic-bot	cfb341e244	chore(canon): Adversary online + cold baseline of starting state (1 enrolled, 1 canonical from samever, daily timer)	2026-06-17 06:19:45 +00:00
autonomic-bot	199f5b6cb8	review(samever): M2 PASS — headline step-back reproduced from own clone; version-bump + discourse #4 unaffected; teeth hold; clean teardown. No VETO; cleared for DONE	2026-06-17 05:04:42 +00:00
autonomic-bot	96c4ad9ef3	claim(M2): samever proven in real CI — step-back base<head, version-bump unaffected, discourse #4 + hedgedoc spot-check ... 5 real cc-ci runs (samever-deploy @ cc-ci main): Run B nightly steady-state step-back custom-html 1.11.0+1.29.0→1.13.0+1.31.1 (base<head real delta, 5 tiers green); Run C version-bump UNAFFECTED (last-green path); Run D PR-form step-back (ref set); discourse #4 kind=ref main-tip unaffected (migration 0.8.1→1.0.0 green); hedgedoc spot-check step-back 3.0.9→3.0.10 green. WHAT/HOW/EXPECTED/WHERE in STATUS-samever.md; logs /root/samever-*.log, artifacts /var/lib/cc-ci-runs/samever-*/ on cc-ci.	2026-06-17 04:58:48 +00:00
autonomic-bot	8e8985b96f	journal(samever): M2 evidence — step-back (B), version-bump-unaffected (C), discourse kind=ref unaffected	2026-06-17 04:47:53 +00:00
autonomic-bot	7902fb327d	chore(samever): consume ADVERSARY-INBOX (M2 heads-up read)	2026-06-17 04:33:32 +00:00
autonomic-bot	aff7b14299	inbox(samever): heads-up — starting M2 e2e (custom-html two-run) on cc-ci	2026-06-17 04:32:52 +00:00
autonomic-bot	398f559168	status(samever): M1 PASS recorded; M2 in progress (custom-html two-run on cc-ci)	2026-06-17 04:32:51 +00:00
autonomic-bot	1310a95ac2	review(samever): M1 PASS — resolver step-back cold-verified; teeth hold (base<head), version-bump path untouched, 13/13 + own probes	2026-06-17 04:28:22 +00:00
autonomic-bot	61c7739285	journal(samever): M2 prep notes while parked at M1 gate	2026-06-17 04:26:27 +00:00
autonomic-bot	c5a0d204c1	claim(M1): samever resolver step-back implemented + unit-tested (13 pass) ... WHAT/HOW/EXPECTED/WHERE in STATUS-samever.md. Adversary: cold pytest tests/unit/test_upgrade_base.py → 13 passed; canonical==head steps back to a strictly-older base, canonical!=head unchanged, no-older→declared skip.	2026-06-17 04:25:16 +00:00
autonomic-bot	b29bb3f804	feat(samever): step back to older base when last-green canonical == head version ... resolve_upgrade_base now reads the head's published version (abra.head_compose_version, the coop-cloud.<stack>.version label) and, when the last-green warm-canonical version equals it, steps back to the newest published version strictly older than head instead of deploying a same-version no-op. warm_reconcile gains version_key + newest_older_version (single coop-cloud ordering source; sort_versions refactored onto version_key, no behavior change). Skip only when no older published predecessor exists. Step-back returns kind=version so it inherits F1d-2 pinned-tag checkout. Extends tests/unit/test_upgrade_base.py (13 pass).	2026-06-17 04:24:14 +00:00
autonomic-bot	279d84d229	fix(STATUS-regall): bare ## DONE marker so watchdog detects phase complete	2026-06-17 04:14:14 +00:00
autonomic-bot	f97ed0299a	review(samever): Adversary orientation — samever phase started; awaiting M1 claim	2026-06-17 04:11:09 +00:00
autonomic-botandClaude Sonnet 4.6	eff8b1a93f	review(regall): M1 PASS + M2 PASS — full sweep 21/21 GREEN, no prevb regressions, no VETO ... M1: All 21 recipes cold-verified from results.json. Classification table accurate. Zero prevb regressions. A-regall-2 (plausible) = recipe bug in 3.0.1+v2.0.0, not prevb. BPs 1-5 complete. No flake misclassifications found. M2: Trivially satisfied — no prevb-caused regressions, no cc-ci code fixes needed. Both M1+M2 PASS. regall phase DONE. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 03:04:38 +00:00
autonomic-botandClaude Sonnet 4.6	3403309136	status(regall): ## DONE — M1+M2 Adversary-verified PASS (no VETO); all 21 GREEN ... 21/21 recipes GREEN post-prevb. 0 prevb regressions. A-regall-2 closed (plausible backup_restore=fail was recipe bug in 3.0.1+v2.0.0, NOT prevb; run 758 / PR#3 / 3.1.0+v2.0.0 confirms L5 pass with fixed backup mechanism). All batches 1-6 complete. M1+M2 both claimed 2026-06-17T04:45Z. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 03:03:06 +00:00
autonomic-botandClaude Sonnet 4.6	848e0c6b1e	review(regall): A-regall-2 CLOSED — plausible L5 via PR#3 (run 758); recipe bug NOT prevb ... Builder diagnosis (a3d115d) accepted: - backupbot.backup.path in 3.0.1+v2.0.0 places dump in writable layer (not restic volume) - PR#4 (trivial regall trigger at 3.0.1+v2.0.0) exposes the bug; PR#3 (3.1.0+v2.0.0) fixes it - Baseline run 658 used PR#3 (d77adba4698b) — same passing ref as run 758 Cold-verified: run 758 (PR#3, d77adba4698b) → level=5, backup_restore=pass ✓ Plausible regall result = L5 GREEN. Sweep now 21/21 complete. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 03:01:55 +00:00
autonomic-botandClaude Sonnet 4.6	a3d115d6e3	diagnose(regall): A-regall-2 root cause — recipe bug in 3.0.1+v2.0.0, NOT prevb ... backupbot.backup.path: "/postgres.dump.gz" places dump in container writable layer (not a volume), so restic never captures it. Restore post-hook fails with "No such file or directory". PR#3 (3.1.0+v2.0.0) fixes this with backupbot.backup.volumes.db-data.path. Baseline run 658 tested PR#3 (working mechanism), not 3.0.1+v2.0.0 (broken). Re-opened PR#3 + !testme triggered (comment 14651) to demonstrate backup_restore=pass. BUILDER-INBOX consumed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:58:06 +00:00
autonomic-botandClaude Sonnet 4.6	3edd0713d2	review(regall): A-regall-2 CONFIRMED — plausible backup_restore=fail 2/2 (genuine regression) ... Runs 750 and 754 both fail: ci_marker absent after restore. No-op upgrade (3.0.1+v2.0.0→3.0.1+v2.0.0) via UPGRADE_BASE_VERSION path is prevb-specific. Baseline run 658 had genuine git-ref upgrade and passed L5. Builder-INBOX written. M1 blocked pending plausible fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:34:04 +00:00
autonomic-botandClaude Sonnet 4.6	a7317a54fb	review(regall): batches 5-6 verified; A-regall-2 filed for plausible backup_restore=fail ... Batch 5 results: - uptime-kuma (748): L5 all pass ✓ - lasuite-drive (749): L5 all pass ✓ - plausible (750): L2, backup_restore=FAIL — regression from baseline L5 - ci_marker not found after restore; no-op upgrade (3.0.1+v2.0.0→3.0.1+v2.0.0) - Builder re-running as Drone 754 Batch 6 results: - custom-html-tiny (752): L5, upgrade=pass, backup_restore=skip (expected) ✓ - bluesky-pds (753): L5, upgrade=skip (expected/EXPECTED_NA), backup_restore=pass ✓ A-regall-2: plausible backup_restore=fail — prevb regression or flake TBD. Run 750 shows no-op upgrade (prevb UPGRADE_BASE_VERSION path) vs baseline run 658 genuine upgrade (git ref). Same failure seen in m2r/m2rr-plausible during prevb development. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:32:26 +00:00
autonomic-bot	ec1dc5978d	status(regall): batch 5 partial (lasuite-drive/uptime-kuma L5; plausible restore=fail LIKELY FLAKY, re-triggered); batch 6 IN FLIGHT	2026-06-17 02:28:31 +00:00
autonomic-bot	b2198dc7e5	status(regall): batch 4 DONE (ghost/immich/lasuite-docs L5); batch 5 IN FLIGHT (lasuite-drive/plausible/uptime-kuma)	2026-06-17 02:20:13 +00:00
autonomic-botandClaude Sonnet 4.6	c42a65d315	review(regall): batch 4 all L5 (lasuite-docs/ghost/immich); 16/21 recipes GREEN ... Cold-verified from results.json: - lasuite-docs (743): L5 all pass - ghost (744): L5 all pass - immich (745): L5 all pass No regressions. Remaining: lasuite-drive, plausible, uptime-kuma, custom-html-tiny, bluesky-pds. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:18:46 +00:00
autonomic-bot	2c4fdddd33	status(regall): batch 3 DONE (custom-html/mailu/mattermost-lts L5); batch 4 IN FLIGHT (ghost/immich/lasuite-docs trivial PRs created + !testme)	2026-06-17 02:14:09 +00:00
autonomic-botandClaude Sonnet 4.6	2db9c8bb00	review(regall): batch 3 all L5 (custom-html/mailu/mattermost-lts); BP-5 previous/ overlay scoping correct ... Cold-verified from results.json + Drone logs: - custom-html (737): L5 all pass - mailu (738): L5 upgrade=pass (A-regall-1 risk clear), backup_restore=skip (expected) - mattermost-lts (739): L5 all pass BP-5: custom-html build 737 log confirms kind=ref main-tip, no previous/ overlay applied. prevb previous/ mechanism correctly scoped to UPGRADE_BASE_VERSION recipes only. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:13:07 +00:00
autonomic-botandClaude Sonnet 4.6	dc086ecb70	review(regall): batch 2 closed all L5; batch 3 partial (custom-html L5, mailu L5 upgrade=pass, mattermost-lts running) ... Cold-verified from results.json: - mumble (732): L5 all pass - custom-html (737): L5 all pass - mailu (738): L5 upgrade=pass (A-regall-1 corrected baseline — regression risk clear), backup_restore=skip (expected) - mattermost-lts (739): still running Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 02:11:40 +00:00
autonomic-bot	12741fceee	status(regall): batch 2 DONE (lasuite-meet/n8n/mumble L5); batch 3 IN FLIGHT (custom-html/mattermost-lts/mailu)	2026-06-17 02:08:52 +00:00
autonomic-bot	bc4eeaa6b5	review(regall): A-regall-1 CLOSED; BP-3 !testmexyz rejected; BP-4 dashboard clean; batch-2 partial (lasuite-meet/n8n L5)	2026-06-17 02:07:36 +00:00
autonomic-bot	7c6134a773	fix(regall): correct mailu baseline upgrade=pass (A-regall-1); consume Adversary inbox; batch 2 in flight	2026-06-17 02:05:42 +00:00
autonomic-bot	4ad3c9d907	review(regall): BP-1 baseline verified (A-regall-1: mailu upgrade=pass not skip); BP-2 upgrade-base=main-tip confirmed; batch-1 all L5	2026-06-17 02:04:48 +00:00
autonomic-bot	d809167c84	status(regall): batch 1 DONE (drone/gitea/matrix-synapse L5); batch 2 IN FLIGHT (mumble/lasuite-meet/n8n)	2026-06-17 02:03:21 +00:00
autonomic-bot	fc3ed2834b	review(regall): Adversary live; orientation + batch-1 partial results recorded (drone/matrix-synapse L5✓, gitea running)	2026-06-17 02:01:26 +00:00
autonomic-bot	a54a27837e	status(regall): batch 1 IN FLIGHT — drone/gitea/matrix-synapse !testme triggered	2026-06-17 01:58:20 +00:00
autonomic-bot	4d54123d03	chore(regall): bootstrap phase state (STATUS/BACKLOG/REVIEW/JOURNAL-regall)	2026-06-17 01:56:27 +00:00
autonomic-bot	b6f526a22d	status(prevb): ## DONE — M1+M2 Adversary-verified PASS (no VETO); dynamic base + previous/ + discourse PR#4 real-CI GREEN (official 3.5.3 migration tested)	2026-06-17 01:51:04 +00:00
autonomic-bot	1c3ba71b04	review(prevb): M2 PASS — discourse #4 !testme GREEN in real CI (Drone 717, live-image teeth=official 3.5.3, lint non-gating); 3 spot-checks + own cryptpad re-run confirm dynamic base; public surface secret-clean; nothing merged. Both M1+M2 PASS, no VETO → Builder may DONE	2026-06-17 01:50:01 +00:00
autonomic-bot	e8a0037d85	defer(prevb): file F-prevb-C (mint_admin ApiKey in access-controlled RAW log; pre-existing, low-sev, out of scope)	2026-06-17 01:49:56 +00:00
autonomic-bot	19c9c3edcf	review(prevb): M2 cold-verify IN FLIGHT — discourse #4 !testme GREEN confirmed via gitea API (Drone 717, real live-image teeth, lint=non-gating rung); 3 spot-checks dynamic-base confirmed; my own cryptpad re-run in flight	2026-06-17 01:48:41 +00:00
autonomic-bot	71399f65d1	claim(prevb): M2 — discourse PR#4 !testme GREEN in real CI (Drone 717, all 5 tiers, head=official 3.5.3); 3 spot-checks green under dynamic base	2026-06-17 01:40:19 +00:00
autonomic-bot	a0de5b196d	status(prevb): B7 DONE — discourse PR#4 !testme GREEN in real CI (Drone 717, all 5 tiers); launching hedgedoc spot-check	2026-06-17 01:36:44 +00:00
autonomic-bot	59338e9fc4	journal(prevb): all 5 discourse tiers green locally (custom mint_admin fixed); posting !testme for B7	2026-06-17 01:26:53 +00:00
autonomic-bot	b66abc4978	fix(prevb): discourse custom mint_admin image-agnostic (official /var/www/discourse + DB-password re-export; bitnami fallback) ... The custom tier runs on the PR head — now genuinely the official discourse/discourse image (prevb stopped the overlay reverting it to bitnamilegacy). mint_admin hardcoded /opt/bitnami/discourse (404 on official) → create-topic roundtrip failed. Detect /var/www/discourse, re-export DISCOURSE_DB_PASSWORD from /run/secrets (entrypoint exports it only for boot), run bin/rails; keep bitnami fallback.	2026-06-17 01:20:41 +00:00
autonomic-bot	55d638026f	status(prevb): M1 PASS recorded; starting M2 (full local discourse run → !testme)	2026-06-17 01:06:32 +00:00
autonomic-bot	dbc7a3b6ea	review(prevb): M1 PASS — dynamic base (main-tip fallback live), previous/ base-only, overlay separated, head=official 3.5.3; TEETH: broken head → upgrade RED; clean teardown; no test weakened	2026-06-17 01:03:45 +00:00
autonomic-bot	ad8d9f4713	review(prevb): M1 e2e GREEN confirmed cold (head=official 3.5.3, sidekiq dropped, clean teardown); break-it re-launched after SIGTERM	2026-06-17 01:00:44 +00:00
autonomic-bot	8c286bff60	docs(prevb): update recipe-customization/testing/runbook for dynamic base + previous/ (drop stale recipe_versions[-2] model)	2026-06-17 00:46:03 +00:00
autonomic-bot	0cf70b67b9	journal(prevb): 3 green spot-checks under dynamic base (cryptpad/keycloak incl master-fallback); parking at M1 gate	2026-06-17 00:43:17 +00:00
autonomic-bot	22f597c0fa	recon(prevb): M1 cold acceptance in flight — base=main-tip ref confirmed; concurrent keycloak run isolated	2026-06-17 00:42:34 +00:00
autonomic-bot	bb79e9140e	claim(prevb): M1 — dynamic base + previous/ + discourse migration; discourse upgrade GREEN locally (head=official 3.5.3, sidekiq pruned)	2026-06-17 00:37:23 +00:00
autonomic-bot	e1b32ea650	fix(prevb): prune orphan services on upgrade redeploy (head's dropped services); re-add EXPECTED_NA-other-rung test; consume Adversary inbox ... docker stack deploy doesn't prune services the head compose dropped (discourse PR#4 drops sidekiq), leaving them orphaned on the base image. perform_upgrade now reconciles the live stack to the head compose service set (lifecycle.prune_orphan_services). Makes the deployed stack faithfully reflect the head — no test weakened. No-op when service sets match / compose unresolvable.	2026-06-17 00:29:00 +00:00
autonomic-bot	7f3e7c26f6	recon(prevb): M1 code pre-review (sound; 63 prevb unit tests pass cold) + builder heads-up (pre-existing red test)	2026-06-17 00:27:06 +00:00
autonomic-bot	37cacf0f09	journal(prevb): M1 code green (unit+lint); discourse main-tip e2e in flight	2026-06-17 00:20:39 +00:00
autonomic-bot	bb2e3c6b2c	feat(prevb): dynamic upgrade base (last-green→main→skip) + per-recipe previous/ overlay; migrate discourse off static base + leaky overlay ... - resolve_upgrade_base: BasePlan(kind=version|ref|skip); last-green (warm canonical) primary, main-tip fallback, declared skip else. UPGRADE_BASE_VERSION retained as optional override. - deploy_app: base_ref path (chaos-deploy a main-tip/last-green commit) + apply_previous wiring. - lifecycle: previous/ surface (has_previous, previous_target_version, previous_status decision, provide/remove overlay, compose_file add/remove, recipe_branch_commit, stack_service_names). - generic.perform_upgrade: strip previous/ overlay + COMPOSE_FILE entry before head redeploy. - discourse: compose.ccci.yml now environmental-only (order: stop-first); removed bitnamilegacy pins + sidekiq + UPGRADE_BASE_VERSION; test_upgrade.py asserts head image == official 3.5.3 + no sidekiq. - unit tests: resolve_upgrade_base matrix + previous/ apply/skip/stale + COMPOSE_FILE layering.	2026-06-17 00:15:06 +00:00
autonomic-bot	1090abb97a	recon(prevb): independently cold-verified discourse PR#4 head/main image facts (confirmed)	2026-06-17 00:10:57 +00:00