Commit Graph

  • 3c79e3de32 journal(2): drone Q4.10 analysis — needs gitea SCM dep + OAuth + build-trigger pipeline (heaviest §4.3) autonomic-bot 2026-05-29 21:46:06 +01:00
  • 6a216ed73b claim(2): Q4.9 mailu full lifecycle GREEN (P4 N/A) — awaiting Adversary autonomic-bot 2026-05-29 21:39:02 +01:00
  • 88449431e1 fix(2): Q4.9 mailu — rewrite mail-flow via in-container sendmail+doveadm; drop network IMAP-auth test autonomic-bot 2026-05-29 21:33:11 +01:00
  • 916bdd8b68 feat(2): Q4.9 mailu — recipe_meta + health + 3 functional (create-mailbox/imap-login/mail-flow); P4 N/A deferred autonomic-bot 2026-05-29 21:13:56 +01:00
  • 3ab04cd07a journal(2): mailu Q4.9 deeper recon — certdumper/ACME TLS friction; start with TLS_FLAVOR=notls autonomic-bot 2026-05-29 20:57:39 +01:00
  • 594f2d3389 review(2): Q4.6 discourse deferral VERIFIED SOUND — bitnami/discourse:3.3.1 + :3.1.2 both GONE, bitnamilegacy present; genuine upstream env-blocker (§8), pre-cleared for DONE; no veto autonomic-bot 2026-05-29 20:56:01 +01:00
  • 7282caef30 journal(2): mailu Q4.9 enrollment plan + discourse Q4.6 block recorded (handoff to next iteration) autonomic-bot 2026-05-29 20:54:21 +01:00
  • bdc05e24c4 status/backlog(2): Q4.6 discourse blocked (bitnami images gone); pivot to Q4.9 mailu (images pullable) autonomic-bot 2026-05-29 20:53:09 +01:00
  • 848cc31fea deferred(2): Q4.6 discourse BLOCKED — upstream bitnami/discourse images removed from Docker Hub (undeployable) autonomic-bot 2026-05-29 20:52:14 +01:00
  • ca7acf3d52 feat(2): Q4.6 discourse — recipe_meta + postgres P4 overlays + health (WIP, §4.3 create-topic next) autonomic-bot 2026-05-29 20:38:25 +01:00
  • e36656f688 status(2): Q4.2 mumble Adversary PASS (REVIEW-2 1daa1ea) — DONE; advancing to discourse autonomic-bot 2026-05-29 20:35:50 +01:00
  • 1daa1ea067 review(2): Q4.2 mumble PASS — COLD first-hand full-lifecycle GREEN (my clone @1ba5613); 5 tiers, deploy-count=1, tcp ready-probe 2x, real upgrade crossover, P3 config round-trips non-vacuous (max_users=42 + welcome marker), P4 sqlite ci_marker survives, clean teardown; no veto. Minor: leftover mumb-smoke volume (housekeeping) autonomic-bot 2026-05-29 20:34:57 +01:00
  • f4e11d4cca journal(2): next-recipe recon — discourse chosen (only remaining recipe with a backup mechanism for real P4) autonomic-bot 2026-05-29 20:33:03 +01:00
  • 1ba56139fb claim(2): Q4.2 mumble full lifecycle GREEN — awaiting Adversary autonomic-bot 2026-05-29 20:25:37 +01:00
  • ec76072489 fix(2): Q4.2 mumble — TCP voice-server READY_PROBE gates backup past upgrade host-port churn autonomic-bot 2026-05-29 20:19:07 +01:00
  • 1890cb58f3 fix(2): recipe_checkout force (-f) — fixes mumble upgrade-tier checkout collision with cc-ci overlay autonomic-bot 2026-05-29 20:03:41 +01:00
  • 191fa774ec review(2): Q4.2 mumble PRE-CLAIM code audit (NOT a verdict) — P7 non-vacuous at code level; cold-verify checklist staged for when claimed autonomic-bot 2026-05-29 19:59:41 +01:00
  • 850c3c4fb9 inbox(2): consume Adversary node-free/mumble-unblocked notice (already acting — mumble run in flight) autonomic-bot 2026-05-29 19:58:57 +01:00
  • 7054e9bcd0 review(2): Q4.7 plausible teardown CLOSED (plau-0c70fd fully clean); cold run done, node FREE; §4.3 first-hand PASS still pending; inbox-notify Builder mumble unblocked autonomic-bot 2026-05-29 19:58:01 +01:00
  • a0fd58b4c5 fix(2): Q4.2 mumble — set sqlite busy timeout via silent .timeout dot-command, not PRAGMA autonomic-bot 2026-05-29 19:54:10 +01:00
  • 27abce678b review(2): Q4.7 plausible CONSOLIDATED verdict — self-corrects 0efcc36+1ecae1c (both had errors); §4.3 green in ONE clean Builder log + non-vacuous; full-lifecycle unproven (upstream clickhouse stall); not cleared, no veto autonomic-bot 2026-05-29 19:45:51 +01:00
  • 3360f1b266 status(2): Q4.2 mumble code complete; full run queued behind Adversary plausible cold run (single node) autonomic-bot 2026-05-29 19:34:22 +01:00
  • 999dd0d564 fix(2): Q4.2 mumble — CHAOS_BASE_DEPLOY meta flag for chaos base deploy (clean-tree gate) autonomic-bot 2026-05-29 19:32:48 +01:00
  • 1b6c77c76a inbox(2): consume Adversary BUILDER-INBOX (Q4.7 plausible evidence) — corrected by review 1ecae1c (§4.3 green substantiated) autonomic-bot 2026-05-29 19:31:21 +01:00
  • 1ecae1ce27 review(2): Q4.7 plausible CORRECTION — retract 'no evidence'; §4.3 event tests ARE green (2 Builder logs, 1 clean) + non-vacuous; my own cold run launched; full-lifecycle still deferred autonomic-bot 2026-05-29 19:30:26 +01:00
  • 38db17af0c status(2): ACK Adversary Q4.7 plausible finding — will provide preserved green-run log post-cooldown autonomic-bot 2026-05-29 19:28:54 +01:00
  • 6bf0425f50 fix(2): Q4.2 mumble — provide host-ports overlay for every version via install_steps autonomic-bot 2026-05-29 19:27:35 +01:00
  • 0efcc36207 review(2): Q4.7 plausible — deferral sound + test content non-vacuous, but '§4.3 proven green' UNVERIFIED (no evidence log on host); Q4.7 not cleared autonomic-bot 2026-05-29 19:26:59 +01:00
  • 6841048aae feat(2): Q4.2 mumble — parity port (health/protocol-handshake/web) + 2 specific + P4 sqlite autonomic-bot 2026-05-29 19:20:56 +01:00
  • 265eae5365 status(2): Q4.2 mumble enrolling — TCP-protocol recipe, mumbleweb+host-ports plan, P2 corpus port autonomic-bot 2026-05-29 19:13:39 +01:00
  • 7851f0450d status(2): Q4.7 plausible — test content green (event tests proven); full-lifecycle blocked on upstream clickhouse boot-download; Q4.7b recipe-PR deferred autonomic-bot 2026-05-29 18:56:11 +01:00
  • 19f1ea6da4 decisions(2): plausible clickhouse-backup boot-download = upstream robustness defect; recipe-PR deferred (Q4.7b) autonomic-bot 2026-05-29 18:55:45 +01:00
  • f9ebb3f610 journal(2): Q4.7 plausible — root cause of clickhouse-backup boot-download crash-loop + decision autonomic-bot 2026-05-29 18:48:56 +01:00
  • b4f39cb51a fix(2): plausible install overlay — assert /api/health subsystems, not / (auth_controller 500s under headless DISABLE_AUTH; / is not a valid readiness probe) autonomic-bot 2026-05-29 18:13:20 +01:00
  • 3943cd80e5 feat(2): Q4.7 plausible — §4.3 event-tracking functional tests + PARITY.md; /api/health readiness probe autonomic-bot 2026-05-29 18:05:16 +01:00
  • baae41fe10 fix(2): plausible HTTP_TIMEOUT 600→1200 + DEPLOY_TIMEOUT 1200 — app 500s until clickhouse/migrations ready autonomic-bot 2026-05-29 16:34:11 +01:00
  • f0f6b6f545 feat(2): Q4.7 plausible — ops + lifecycle overlays (postgres ci_marker; pg_dump backup hook) autonomic-bot 2026-05-29 16:21:15 +01:00
  • 1dd7376ff4 status(2): HQ1 image pre-pull Adversary PASS (0215bd2) autonomic-bot 2026-05-29 16:19:27 +01:00
  • 0215bd2203 review(2): PASS gate HQ1 image pre-pull (claim 475ad5c/code 2bf40d6) — 4 unit pass (non-vacuous, raises on pull-fail); LIVE warm-cache skip (present n8n, zero network); LIVE bad-tag RAISES clear pull error BEFORE deploy (manifest unknown, not converge timeout); abra deploy real+UNCHANGED (prepull before, no service update/scale); honest scope (pull-time not init-time). No VETO autonomic-bot 2026-05-29 16:18:28 +01:00
  • 475ad5c774 claim(2): HQ1 image pre-pull — warm local store before deploy (4 unit tests + warm-cache-skip + bad-tag-clear-error + abra-unchanged) autonomic-bot 2026-05-29 16:14:25 +01:00
  • 2bf40d69d6 feat(2): HQ1 image pre-pull (plan-prepull-images.md) — warm local store before deploy autonomic-bot 2026-05-29 16:02:21 +01:00
  • e6e5436942 backlog(2): Q3.5 immich [~] partial — 4/5 green + §4.3; restore P4 blocked by upstream recipe (pg_dump hook needed, DEFERRED) autonomic-bot 2026-05-29 15:54:10 +01:00
  • 9272c20727 journal/deferred(2): Q3.5 immich PARTIAL — restore P4 blocked by upstream recipe (volume backup, no pg_dump hook); recipe-PR unit filed (drive/meet pg_backup.sh pattern) autonomic-bot 2026-05-29 15:53:22 +01:00
  • 250bed4768 status(2): cryptpad F2-9 + F2-13 Adversary CLOSED (f7ed2d9) — §4.3 create-pad floor demonstrated; DONE-blocker cleared autonomic-bot 2026-05-29 15:38:21 +01:00
  • f7ed2d967c review(2): cryptpad F2-9 + F2-13 CLOSED — re-verify after fix b44d75b (poll-all-frames). create-pad roundtrip test_cryptpad_pad_content_survives_fresh_session PASSED (46s, was 340s timeout), all 5 tiers green, deploy-count=1, clean teardown. Fix non-vacuous (still asserts marker surfaces in fresh context = server-side encrypted persistence). §4.3 create-pad floor demonstrated; conditional sign-off satisfied autonomic-bot 2026-05-29 15:37:12 +01:00
  • 62ac9b59e0 journal/status(2): F2-13 cryptpad read-back robustness FIXED (b44d75b, poll-all-frames) — 3x green vs cold probe; awaiting Adversary re-verify/F2-9 close autonomic-bot 2026-05-29 15:26:25 +01:00
  • 82dc2d733d feat(2): immich §4.3 asset upload→read-back→thumbnail test + PARITY autonomic-bot 2026-05-29 15:13:11 +01:00
  • b44d75b89c fix(2): F2-13 cryptpad roundtrip read-back robustness — poll all frames for marker autonomic-bot 2026-05-29 15:08:52 +01:00
  • 1cbb1ccd73 review(2): cryptpad F2-9 NOT closed — create-pad roundtrip read-back leg FAILED on cold-verify (CKEditor frame never attached on fresh context, line 133; 1 failed in 340s) → test is flaky not 3x-reliable. Filed F2-13: make read-back robust before F2-9 closes. install/upgrade/backup/restore pass, only the §4.3-floor pad-persist test red; teardown clean. NOT a VETO (F2-9 was conditional/open) autonomic-bot 2026-05-29 15:05:22 +01:00
  • 754f508231 review(2): record forward-looking Adversary criteria for pre-pull harness unit (plan-prepull-images.md) — verify warm-cache no-redownload + bad-tag=clear-pull-error-pre-deploy + abra stays real/unchanged + honest scope (pull-time not init-time; F2-12 init races still need healthcheck) autonomic-bot 2026-05-29 14:58:38 +01:00
  • f8af5b2307 backlog(2): HQ1 — image pre-pull harness unit (plan-prepull-images.md), near-term; fixes the first-deploy 'No such image' race autonomic-bot 2026-05-29 14:56:18 +01:00
  • d4eae4ee49 fix(2): set time.timeZone=UTC on cc-ci → create /etc/localtime (immich bind-mount) autonomic-bot 2026-05-29 14:51:33 +01:00
  • b0f1e0b0ad status(2): Q3.3 lasuite-meet Adversary PASS (a46f7d4); immich Q3.5 validating autonomic-bot 2026-05-29 14:44:09 +01:00
  • 98a37d44b5 feat(2): Q3.5 immich enrollment (recipe_meta + ops + lifecycle overlays + health parity) autonomic-bot 2026-05-29 14:40:54 +01:00
  • a46f7d4593 review(2): PASS gate Q3.3 lasuite-meet (claim 5af513e/code 1f7806a) — cold-verify all 5 tiers GREEN, deploy-count=1, real upgrade crossover 0.2.0+v1.15.0->0.3.0+v1.16.0, meeting_flow (room create->read-back->LiveKit video-grant JWT->delete) PASSED, OIDC PASSED not-skipped, ci_marker survives, teardown clean+realm reaped. WebRTC media-relay non-port: ADVERSARY SIGN-OFF (genuine UDP env-blocker, maximal subset=LiveKit token issuance shipped) autonomic-bot 2026-05-29 14:40:15 +01:00
  • 5af513e2c8 claim(2): Q3.3 lasuite-meet — full lifecycle green (meeting_flow §4.3 + OIDC; R014 chaos-base; webrtc env-blocker non-port) autonomic-bot 2026-05-29 14:33:31 +01:00
  • 1f7806a9c4 fix(2): lasuite-meet meeting_flow — tolerant best-effort delete-verify (meet 0.3.0 soft-deletes) autonomic-bot 2026-05-29 14:24:21 +01:00
  • 72719fe0d7 fix(2): R014 — chaos base deploy for recipes with lightweight tags (replaces fragile origin-repoint) autonomic-bot 2026-05-29 14:15:07 +01:00
  • ad06a5dd3f fix(2): R014 normalize — use git clone --mirror (not --bare) so abra's later fetches find refs/heads/main autonomic-bot 2026-05-29 14:05:26 +01:00
  • da44e2ca8a fix(2): R014 normalize — repoint recipe origin to local bare with annotated tag (abra force-fetches tags before lint, reverting in-place re-annotation) autonomic-bot 2026-05-29 13:59:03 +01:00
  • 8c19b1fadc fix(2): normalize lightweight recipe tags to annotated before pinned deploy (R014) autonomic-bot 2026-05-29 13:48:55 +01:00
  • 9c6cb539ee feat(2): Q3.3 lasuite-meet §4.3 meeting_flow test + PARITY.md autonomic-bot 2026-05-29 13:39:32 +01:00
  • 9c9a0059c1 journal(2): record operator clarification — 3x repeat-green is flakiness-specific (lasuite-drive), not the general gate standard (normal = 1 cold-verified green) autonomic-bot 2026-05-29 13:25:46 +01:00
  • c7b36ebb6a review(2): record operator clarification — 3x repeat-green bar is lasuite-drive-recipe-PR ONLY (flakiness proof); normal gates = ONE cold-verified green per §6.1; cryptpad F2-9 needs only 1x autonomic-bot 2026-05-29 13:25:46 +01:00
  • 31bda3995d feat(2): Q3.3 lasuite-meet — install_steps (OIDC-at-install) + lifecycle overlays + health/OIDC parity tests autonomic-bot 2026-05-29 13:22:30 +01:00
  • 32a743f501 feat(2): Q3.3 lasuite-meet recipe_meta — DEPS=keycloak + OIDC_AT_INSTALL + livekit-domain flatten (reuses lasuite-drive machinery) autonomic-bot 2026-05-29 13:14:42 +01:00
  • 3a8c5ca076 journal(2): both Phase-2 blockers cleared (Q3.2 PASS, F2-9 resolved); scout Q3.3 lasuite-meet as next (reuses lasuite-drive OIDC-at-install machinery) autonomic-bot 2026-05-29 13:13:32 +01:00
  • a48543f57b status/journal/deferred(2): cryptpad F2-9 RESOLVED — roundtrip green in full harness custom tier (cold deploy); awaiting Adversary close autonomic-bot 2026-05-29 13:11:35 +01:00
  • 118305b92f status(2): Q3.2 lasuite-drive Adversary PASS (F2-12 closed); cryptpad roundtrip cold-timing fix in validation autonomic-bot 2026-05-29 13:01:15 +01:00
  • 3484d25b5c fix(2): cryptpad roundtrip — more patient pad-creation wait (240s + reload) for cold fresh deploy autonomic-bot 2026-05-29 13:00:39 +01:00
  • af1481f6fc review(2): record forward-looking Adversary criteria for parked lasuite-drive recipe-PR (Q3.2b) — keystone collabora healthcheck must let cc-ci drop -c backstop to abra-native convergence w/o regressing F2-12; repeat-green+cold-verify before operator merge. Does NOT reopen Q3.2 (PASS stands) autonomic-bot 2026-05-29 13:01:01 +01:00
  • 3f5d58a7c2 review(2): PASS gate Q3.2 lasuite-drive (re-claim a13d2ae/code e1147b5+6506c4a) — F2-12 CLOSED. Cold re-run: all 5 tiers GREEN, upgrade tier now passes, deploy-count=1, ready-probe OK(200) twice, OIDC+minio round-trip PASS (not skipped), data-integrity survives, teardown clean. abra -c + owned wait_healthy/READY_PROBE proven non-vacuous (5 P7-negative units + code-read RAISE paths). DECISIONS: record operator READY_PROBE principle autonomic-bot 2026-05-29 12:59:49 +01:00
  • ac241d44c7 backlog(2): park Q3.2b — lasuite-drive recipe-PR (plan-lasuite-drive-recipe-pr.md) behind Q3.2; keystone collabora healthcheck lets cc-ci drop the F2-12 -c backstop later autonomic-bot 2026-05-29 12:59:37 +01:00
  • 7dab4f5cb6 decisions(2): record operator principle — real-abra-only deploys, abra convergence by default, READY_PROBE (strict + negative-tested) only when abra doesn't fit; F2-12 applied autonomic-bot 2026-05-29 12:57:41 +01:00
  • a13d2ae48b claim(2): Q3.2 re-claim — F2-12 fixed (own convergence wait + READY_PROBE; upgrade 3x green; P7-negative unit-proven) autonomic-bot 2026-05-29 12:45:02 +01:00
  • 6506c4ac3a test(2): F2-12 P7-negative unit tests — owned upgrade-convergence wait fails on stuck convergence autonomic-bot 2026-05-29 12:23:34 +01:00
  • f7c5681cd0 review(2): pre-claim recon F2-12 fix e1147b5 — abra -c skips converge monitor BUT harness owns stricter wait_healthy(N/N all svcs)+READY_PROBE(collabora 200, raises on timeout); plausibly not-a-weakening, MUST cold-verify upgrade-GREEN + P7-negative at re-claim; NO verdict yet autonomic-bot 2026-05-29 12:21:30 +01:00
  • cc4af49c99 status(2): Q3.2 F2-12 FAIL acknowledged, fix e1147b5 validating; cryptpad F2-9 test landed 3/3 green autonomic-bot 2026-05-29 11:58:03 +01:00
  • e1147b5fe3 fix(2): F2-12 lasuite-drive upgrade tier — own convergence wait (abra -c) + collabora READY_PROBE autonomic-bot 2026-05-29 11:55:53 +01:00
  • aab77ea0f3 review(2): FAIL gate Q3.2 lasuite-drive (claim 911680f/code 4b38b66) — cold re-run upgrade tier FAILS (abra chaos-deploy FATA: new collabora 25.04.9.4.1 not converged; WOPI pre-gate DID work). install/backup/restore/custom+OIDC pass, deploy-count=1, teardown clean. Filed F2-12 BLOCKING autonomic-bot 2026-05-29 11:47:38 +01:00
  • 05d0dc14eb feat(2): cryptpad create-pad content roundtrip Playwright test — resolves F2-9 (§4.3 create+read-back) autonomic-bot 2026-05-29 11:46:02 +01:00
  • 911680f843 claim(2): Q3.2 lasuite-drive — full lifecycle 3x green via install-time OIDC + collabora-ready upgrade gate autonomic-bot 2026-05-29 11:16:18 +01:00
  • 5e0af07b86 journal(2): Q3.2a fixed-code run 1 FULL SUITE GREEN (collabora-ready gate fixed upgrade tier); launching 3x repeat-green autonomic-bot 2026-05-29 10:52:44 +01:00
  • e0a80124bc inbox(2): consume BUILDER-INBOX (flag rename relay) + finish --extra rename in BACKLOG-2 Adversary-section lines 241/248/292 (Adversary explicitly delegated) autonomic-bot 2026-05-29 10:40:49 +01:00
  • a22ba9c9cc inbox(2): relay orchestrator flag rename --extra-tests -> --extra to Builder (DEFERRED.md 12 occ + BACKLOG-2 4 occ; single-writer files, not editing them myself) autonomic-bot 2026-05-29 10:38:54 +01:00
  • 4b38b66fa5 fix(2): lasuite-drive Q3.2a — gate upgrade redeploy on collabora-ready + plumb DEPLOY_TIMEOUT autonomic-bot 2026-05-29 10:37:55 +01:00
  • 0b558529c9 review(2): pre-claim recon lasuite-drive Q3.2a Part A — minio scale is recipe one-shot (replicas:0) NOT a bypass; install-time OIDC=deploy-once; minio test is real round-trip; NO verdict (gate not claimed) autonomic-bot 2026-05-29 10:33:01 +01:00
  • f89cf9b1b8 status(2): Q3.2a lasuite-drive Part A in validation — install-time OIDC landed, full-suite run in flight autonomic-bot 2026-05-29 10:13:21 +01:00
  • a151489996 feat(2): lasuite-drive Q3.2a Part A — wire OIDC at INSTALL, eliminate flaky redeploy autonomic-bot 2026-05-29 10:10:05 +01:00
  • 4356f0009c review(2): cross-phase probe — 2pc prune-policy did NOT regress 2w warm infra (volumes survived, timers active, canonical idle@1.11.0); no finding, standing obligations stand autonomic-bot 2026-05-29 10:00:38 +01:00
  • d389dd516b status(2pc): ## DONE — Adversary PASS for PC1+PC2+PC3, F2pc-1 closed, no VETO autonomic-bot 2026-05-29 09:53:30 +01:00
  • 486d162663 review(2pc): PASS gate 2pc (re-claim 9e73ebd) — PC1+PC2+PC3 cold-verified; F2pc-1 CLEARED. git==host: docker-prune.nix+swarm.nix byte-identical to /root/cc-ci, committed units now ci-docker-prune = live (enabled+active), old docker-prune.timer not-found. Live re-confirm: no-op prune@<80% images 18->18, cold->warm redis reuse. Pressure-branch keep-cache property structural (image prune w/o --all). PC2 PAT nptest2+retention+no-mirror, PC3 teardown-keeps-images+bogus-tag-fails GREEN from prior pass. autonomic-bot 2026-05-29 09:52:28 +01:00
  • 9e73ebda3d claim(2pc): re-claim — F2pc-1 resolved (git==host==ci-docker-prune via b9bbd25) autonomic-bot 2026-05-29 09:50:39 +01:00
  • 49892be7b0 review(2pc): FAIL gate 2pc (claim de6103d) — PC1/PC2/PC3 behavior cold-verified GREEN on host (surgical gated prune no-op@31%, images 17→17; teardown keeps images; PAT nptest2; cold→teardown→warm reuses local layers; bogus tag still fails), BUT committed code != verified host: git defines docker-prune units, host runs ci-docker-prune from uncommitted /root/cc-ci → not reproducible from git (D8). Filed F2pc-1 BLOCKING. autonomic-bot 2026-05-29 09:47:43 +01:00
  • f6af7edd97 status(2pc): add probe-5 evidence — surgical prune reclaimed 2.34GB (dangling+old only), all tagged images kept, disk bounded without -af autonomic-bot 2026-05-29 09:44:57 +01:00
  • b9bbd253eb fix(2pc): rename unit docker-prune -> ci-docker-prune (NixOS docker module reserves docker-prune) autonomic-bot 2026-05-29 09:43:09 +01:00
  • de6103d41d claim(2pc): PC1 conservative prune deployed+verified; PC2/PC3 local-store cache confirmed autonomic-bot 2026-05-29 09:42:36 +01:00
  • 16d177e73a feat(2pc): PC1 conservative prune — drop autoPrune --all, add gated surgical docker-prune autonomic-bot 2026-05-29 09:29:54 +01:00
  • e42753c17c note(2pc): realign REVIEW-2pc to narrowed scope — registry pull-through cache DROPPED per operator; 2pc is now prune-policy only (PC1 surgical prune + teardown must NOT remove images, PC2 confirm PAT-auth+local-store retention, PC3 deploy/teardown/redeploy reuses local layers). Break-it checklist updated. autonomic-bot 2026-05-29 09:25:55 +01:00
  • 863bbac4de note(2pc): init REVIEW-2pc — AWAITING CLAIM; baseline recon of current prune (swarm.nix --all until=24h) + confirm no pull-through cache exists yet; break-it checklist staged autonomic-bot 2026-05-29 09:22:11 +01:00