Commit Graph

  • e45e0eea71 review(2): Q4.3 bluesky-pds PASS — COLD full lifecycle GREEN (my clone, log adv-bluesky-pr0) 5 tiers+4 custom, deploy-count=1, real upgrade crossover 0.1.1+v0.4→0.2.0+v0.4, clean teardown; P4 atproto-account marker non-vacuous via IN-BAND pre_restore delete+assert-gone (no recipe-PR — bluesky volume restore genuinely round-trips, real recipe diff from postgres recipes); 2 distinct P3 functional (account+post §4.3 round-trip + getSession auth-gating 401); no veto notplants 2026-05-30 02:56:26 +01:00
  • 7d69a596a7 status(2): fix Q4.3 bluesky claim text (heredoc had eaten backtick code spans) autonomic-bot 2026-05-30 02:51:48 +01:00
  • 4760f9676a claim(Q4.3): bluesky-pds full lifecycle GREEN — P4 added (atproto account marker survives backup/restore/upgrade; volume restore works, no recipe-PR); 5 tiers + 4 custom pass, deploy-count=1, clean teardown autonomic-botandClaude Opus 4.8 2026-05-30 02:50:53 +01:00
  • ad53a7c6c4 status(2): Q4.3 bluesky-pds P4 overlay (atproto account marker) authored, full-lifecycle run in flight autonomic-bot 2026-05-30 02:49:27 +01:00
  • 74da6dc46b feat(2): bluesky-pds P4 data-integrity overlay — deterministic atproto account marker (recipe-aware; catches running-app-holds-sqlite restore gap) via _p4.py + ops/test_upgrade/backup/restore autonomic-botandClaude Opus 4.8 2026-05-30 02:46:50 +01:00
  • 8e160af997 journal(2): mattermost PASS (3rd this session); next bluesky-pds P4 scoped (account-based marker to catch running-app-sqlite-hold restore gap) autonomic-bot 2026-05-30 02:39:05 +01:00
  • 32050885a8 status(2): Q4.5 mattermost-lts Adversary PASS — DONE (3rd PASS this session; 2 recipe-PRs fixing real backup/restore bugs) autonomic-bot 2026-05-30 02:36:54 +01:00
  • 2b4087712d review(2): Q4.5 mattermost-lts PASS — COLD full lifecycle GREEN (my clone, log adv-mattermost-pr1) 5 tiers+4 custom, deploy-count=1, real upgrade crossover 10.11.15→10.11.18, clean teardown; P4 restore proven NON-VACUOUS via negative control (PR=0 published recipe → test_restore_returns_state FAILED 'relation ci_marker does not exist', fail-loud) — recipe-PR #1 is a genuine fix; 2 distinct P3 functional tests (self round-trip + cross-user delivery w/ user_b own token); clean teardown after FAILED run too; no veto notplants 2026-05-30 02:35:50 +01:00
  • 1ca7b2328b claim(Q4.5): mattermost-lts full lifecycle GREEN — P4 restore fixed via recipe-PR recipe-maintainers/mattermost-lts#1 (published restore was a no-op); 5 tiers + 4 custom pass, deploy-count=1, clean teardown autonomic-botandClaude Opus 4.8 2026-05-30 02:11:52 +01:00
  • e9d1e894b2 fix(2): mattermost functional tests share a deterministic admin bootstrap (_mm.bootstrap_admin) — only ONE unauthenticated first-user creation is allowed, so the multi-user test no longer collides with create_message autonomic-botandClaude Opus 4.8 2026-05-30 01:58:32 +01:00
  • 7672f110f6 feat(2): mattermost-lts P3 2nd characteristic test (multi-user message visibility) + PARITY/DECISIONS for the postgres-restore recipe-PR autonomic-botandClaude Opus 4.8 2026-05-30 01:48:08 +01:00
  • 342c3b078f status(2): Q4.5 mattermost recipe-PR #1 opened (pg_backup.sh restore fix), validation run in flight autonomic-bot 2026-05-30 01:41:37 +01:00
  • 11d6d82aad status/journal(2): Q4.5 mattermost P4 overlay caught a real recipe restore defect (no backupbot.restore.post-hook → DB not reimported); recipe-PR queued (immich pattern); node clean autonomic-botandClaude Opus 4.8 2026-05-30 01:30:19 +01:00
  • 012a477540 fix(2): mattermost-lts P4 overlay — postgres service is named 'postgres' not 'db' (exec_in_app container discovery) autonomic-botandClaude Opus 4.8 2026-05-30 01:18:57 +01:00
  • 21e0b16ac4 status(2): Q4.5 mattermost-lts P4 overlay authored, full-lifecycle run in flight autonomic-bot 2026-05-30 01:13:55 +01:00
  • 80ad0a9ed1 feat(2): mattermost-lts P4 data-integrity overlay (ops.py postgres ci_marker seed + test_install/upgrade/backup/restore) — verifying recipe's PGDATA-dir restore brings the marker back autonomic-botandClaude Opus 4.8 2026-05-30 01:11:10 +01:00
  • 0599477440 status(2): Q4.1 matrix-synapse Adversary PASS — DONE autonomic-bot 2026-05-30 01:08:55 +01:00
  • c503f7d51c review(2): Q4.1 matrix-synapse PASS — COLD first-hand full lifecycle GREEN (my clone, log adv-matrix-cold); 5 tiers + 3 custom, deploy-count=1, real upgrade crossover 7.1.0→7.1.1, P4 restore ci_marker survives; §4.3 register retry verified NON-VACUOUS + reproduced the real post-restore transient (500 attempt1/2 → succeeded attempt3, full register→room→send→readback chain intact, 4xx fail-fast, timeout RAISEs); clean teardown; no veto notplants 2026-05-30 01:07:53 +01:00
  • b73018c9ab journal(2): Q4.1 matrix register-500 root cause (restore DROP DATABASE FORCE closes synapse DB pool) + readiness-retry fix autonomic-botandClaude Opus 4.8 2026-05-30 01:01:09 +01:00
  • 9a8850affa claim(Q4.1): matrix-synapse full lifecycle GREEN — §4.3 register transient post-restore 500 root-caused (synapse DB pool closed by restore DROP DATABASE FORCE) + fixed with bounded readiness-retry (not weakened); 5 tiers + 3 functional pass, P4 ci_marker survives, deploy-count=1, clean teardown autonomic-botandClaude Opus 4.8 2026-05-30 01:00:38 +01:00
  • db124d5107 fix(2): matrix register test — bounded readiness-retry on transient post-restore 5xx (synapse re-establishing DB pool after restore-tier DROP DATABASE); assertion unchanged, RAISEs on persistent failure autonomic-botandClaude Opus 4.8 2026-05-30 00:52:18 +01:00
  • cf54fe36a8 status(2): Q4.1 matrix — 4 tiers green; §4.3 register test 500 M_UNKNOWN, diagnosing with synapse log capture (not weakening) autonomic-botandClaude Opus 4.8 2026-05-30 00:45:31 +01:00
  • f39bae71ea status(2): Q3.5 immich Adversary PASS (P4-restore CLOSED); Q4.1 matrix-synapse full-lifecycle run in flight autonomic-botandClaude Opus 4.8 2026-05-30 00:39:57 +01:00
  • 11c5498bfa review(2): Q3.5 immich PASS — COLD first-hand full lifecycle GREEN (my clone, log adv-immich-cold); 5 tiers + 3 custom, deploy-count=1, P4 restore test_restore_returns_state PASSED (ci_marker survives recipe-PR pg_dump backup→restore; non-vacuous: pre_restore DROPs+asserts), negative control 7eb3937 lacks DB backupbot labels (bug confirmed), real upgrade crossover 1.5.1+v2.6.3→1.6.0+v2.7.5, 2 distinct P3 functional, clean teardown; P4-restore RED CLOSED; no veto notplants 2026-05-30 00:36:17 +01:00
  • 191a647dcf journal(2): immich claimed; remaining-recipe scope + backup-capability survey (ghost/bluesky/uptime-kuma/mattermost all backup-capable → P4 overlays required) autonomic-botandClaude Opus 4.8 2026-05-30 00:22:12 +01:00
  • 0487631bac claim(Q3.5): immich full lifecycle GREEN — P4 fixed via recipe-PR recipe-maintainers/immich#1 (recipe backed up NO database); 5 tiers + 3 custom pass, deploy-count=1, clean teardown autonomic-botandClaude Opus 4.8 2026-05-30 00:20:48 +01:00
  • ecd770b9ca feat(2): immich P3 2nd functional test (asset-processing: metadata extraction + library statistics) + PARITY/DECISIONS for immich postgres-backup recipe-PR autonomic-botandClaude Opus 4.8 2026-05-30 00:08:10 +01:00
  • 4f0eeb54bd status(2): immich P4 — mechanism validated, recipe-PR recipe-maintainers/immich#1 opened, full-lifecycle run in flight autonomic-botandClaude Opus 4.8 2026-05-29 23:59:39 +01:00
  • 6241e735ca review(2): drone leftover CLOSED (Builder removed stack+vol, node clean); immich Q3.5 P4 recipe-PR deploy in flight (immi-074f69); no gate pending; drone still operator-blocked (/etc/timezone absent) notplants 2026-05-29 23:49:51 +01:00
  • a4a2e60b87 status(2): immich Q3.5 P4 in-flight — recipe-PR for postgres backup (recipe backs up no DB); inbox consumed, node clean autonomic-botandClaude Opus 4.8 2026-05-29 23:45:08 +01:00
  • 7e2a5bc09c journal(2): immich Q3.5 P4 decision — recipe-PR to add postgres backup (recipe backs up NO DB as published); validate vchord dump/restore empirically first autonomic-botandClaude Opus 4.8 2026-05-29 23:44:47 +01:00
  • 9b2ce09a67 inbox(2): consume adversary heads-up — removed forgotten drone smoke stack+volume (NOT pre-staging; drone integration awaits operator /etc/timezone host-deploy). Node clean: only infra stacks (traefik/bridge/dashboard/backups/warm-keycloak). autonomic-botandClaude Opus 4.8 2026-05-29 23:39:23 +01:00
  • dd45e9555e revert(2): drop adversary scratch probe scripts accidentally staged by git add -A (runner/adv_*.py are local-only adversary scratch, not Builder code) notplants 2026-05-29 23:37:48 +01:00
  • af94708de4 review(2): resume checkpoint — no gate pending; drone block genuine (/etc/timezone still absent on host); leftover drone smoke stack flagged (housekeeping); immich P4-restore still OPEN, unsigned notplants 2026-05-29 23:37:17 +01:00
  • 18577336f0 docs(2): Q5.1 — enroll-recipe.md §2.4 non-HTTP/multi-service/host-dependent recipes + mumble/mailu examples autonomic-botandClaude Opus 4.8 2026-05-29 22:33:43 +01:00
  • 1d99f91b44 status/backlog(2): Q4.10 drone BLOCKED on operator host /etc/timezone deploy (3bde76f); surfaced autonomic-botandClaude Opus 4.8 2026-05-29 22:20:35 +01:00
  • 03b0a3b44d deferred(2): Q4.10 drone blocked on host /etc/timezone deploy (gitea SCM dep); integration scoped autonomic-botandClaude Opus 4.8 2026-05-29 22:19:55 +01:00
  • 3bde76f239 fix(2): cc-ci host — declare /etc/timezone (gitea + Debian-image recipes bind it) autonomic-botandClaude Opus 4.8 2026-05-29 22:16:24 +01:00
  • f86a58addf journal(2): drone+gitea integration fully scoped (gitea dep config + admin/token/OAuth-app + install_steps wiring; §4.3 build-creation deferred) autonomic-botandClaude Opus 4.8 2026-05-29 21:59:07 +01:00
  • 25ae2935b9 status(2): Q4.9 mailu Adversary PASS (REVIEW-2 2958eb6, P4-N/A signed off) — DONE; next drone Q4.10 autonomic-botandClaude Opus 4.8 2026-05-29 21:51:57 +01:00
  • 2958eb6c97 review(2): Q4.9 mailu PASS — COLD first-hand full lifecycle GREEN ×2 (my clone @6a216ed); deploy-count=1, real upgrade crossover 3.0.0→3.0.1 (head_ref==chaos-version), 2 non-vacuous P3 (unique-mailbox round-trip + unique-marker postfix→dovecot delivery), wait_healthy real gate, clean teardown; P4-N/A §7.1 sign-off GRANTED (no backupbot label, independently confirmed); P5/P6 N/A justified; no veto notplantsandClaude Opus 4.8 2026-05-29 21:51:06 +01:00
  • 3c79e3de32 journal(2): drone Q4.10 analysis — needs gitea SCM dep + OAuth + build-trigger pipeline (heaviest §4.3) autonomic-botandClaude Opus 4.8 2026-05-29 21:46:06 +01:00
  • 6a216ed73b claim(2): Q4.9 mailu full lifecycle GREEN (P4 N/A) — awaiting Adversary autonomic-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplants 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 2026-05-29 20:38:25 +01:00
  • e36656f688 status(2): Q4.2 mumble Adversary PASS (REVIEW-2 1daa1ea) — DONE; advancing to discourse autonomic-botandClaude Opus 4.8 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) notplants 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-botandClaude Opus 4.8 2026-05-29 20:33:03 +01:00
  • 1ba56139fb claim(2): Q4.2 mumble full lifecycle GREEN — awaiting Adversary autonomic-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplants 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-botandClaude Opus 4.8 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 notplants 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-botandClaude Opus 4.8 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 notplantsandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplantsandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplantsandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplants 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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 notplants 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-botandClaude Opus 4.8 2026-05-29 15:13:11 +01:00
  • b44d75b89c fix(2): F2-13 cryptpad roundtrip read-back robustness — poll all frames for marker autonomic-botandClaude Opus 4.8 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) notplants 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) notplants 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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) notplants 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 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-botandClaude Opus 4.8 2026-05-29 14:05:26 +01:00