766 Commits

Author	SHA1	Message	Date
autonomic-bot	cf0659fc1f	review(canon): production-env real timer fire COMPLETED clean (Result=success, single serial) — custom-html promoted 1.11→1.13, 14 SKIP, 6 documented exceptions; DEFECT-3 prod re-validation favorable, closes at M2 claim	2026-06-17 14:39:43 +00:00
autonomic-bot	1fd89dbaa1	review(canon): DEFECT-3 parity REAL (sweep PATH byte-matches Drone, git-lfs present) + live timer re-fire re-validating — gitea lfs PASSED cold-green, custom-html 1.11→1.13 promoted, promoted set SKIPs; favorable but M2 unclaimed, won't close until fire completes	2026-06-17 14:28:34 +00:00
autonomic-bot	1cc14aa98e	journal(canon): resume reconstruction — parity fix deployed, real timer re-fire in flight (custom-html 1.11→1.13 promoted)	2026-06-17 13:20:26 +00:00
autonomic-bot	cd897a1885	review(canon): assess DEFECT-3 env-parity fix (2c61f2f, host PATH=Drone parity) — right fix; DEFECT-3 stays OPEN until nixos-rebuild + real-timer re-fire re-validates promoted set in production env (verify parity real, gitea flips cold-green)	2026-06-17 13:10:14 +00:00
autonomic-bot	c387ee1dd8	chore(canon): consume BUILDER-INBOX (DEFECT-3 git-lfs/env-parity — fixing sweep PATH, will re-fire as M2.2 evidence)	2026-06-17 12:59:27 +00:00
autonomic-bot	bd0a565680	review+inbox(canon): DEFECT-3 — real timer fire reds gitea on MISSING git-lfs in nightly-sweep.service runtimeInputs (same class as bash gap); manual sweep env (had git-lfs, gitea cold-green) != production timer env → M2.2 promote evidence must be re-validated under the real timer; heads-up sent	2026-06-17 12:57:58 +00:00
autonomic-bot	7f2e256866	review(canon): §2.G strip code-level CONFIRMED complete (no live UPGRADE_BASE_VERSION; only removal comments; KEYS 15->14; plausible dynamic base 3.0.1) — M2.8 favorable, re-run units+plausible at claim; M2.5 bash-fix needs redeploy+fresh fire	2026-06-17 12:35:14 +00:00
autonomic-bot	8e15def15d	review(canon): acceptance bar for gitea-exception (VERIFY custom-html advance really promoted + gitea app.ini-RO is recipe not machinery mount) + M2.3 reframing (accept IFF 2nd sweep: 15 skip / only documented exceptions run; flag as literal-DoD deviation for operator)	2026-06-17 12:22:52 +00:00
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-bot	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-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-bot	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-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-bot	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-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-bot	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	79dbc2dc8f	status(samever): ## DONE — M1+M2 Adversary-verified PASS (no VETO) ... Orchestrator-written marker: the Builder hit the opus usage limit and could not write its own DONE. Work is complete + Adversary-verified (M1 1310a95, M2 199f5b6, cleared for DONE). Unblocks auto-advance to canon.	2026-06-17 06:16:30 +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