memory: commit session notes (drone P0, weekly-upgrade-queued, mailu/index updates)

Per AGENTS.md 'Agent memory lives in memory/ (in this repo)' — memory notes
must be committed + pushed like any repo change, not left only in the local
~/.claude symlink target.

memory/plausible-upgrade-base-trap.md

@@ -18,10 +18,12 @@ immutable history.
 **Why:** the PR adds 3.1.0 above the newest published tag — the harness-documented case
 where `[-2]` is the wrong base and `[-1]` (3.0.1) is correct.
 
-**How to apply:** the fix is one line in the cc-ci repo (gated by --with-tests / operator):
-`tests/plausible/recipe_meta.py: UPGRADE_BASE_VERSION = "3.0.1+v2.0.0"`. The recipe-side
-hardening (verified cached binary on the persistent volume, Altinity URL, retries+timeout,
-loud hard-fail, depends_on fix) is on PR #3 (commit 9f8bcbc). Diagnosis + ask posted at
-https://git.autonomic.zone/recipe-maintainers/plausible/pulls/3#issuecomment-14261.
-Before burning a !testme on an upgrade-stage recipe, check what base version the harness
-will pick and whether that base can actually converge. See [[abra-chaos-deploy-checkout-gotcha]].
+**How to apply:** RESOLVED 2026-06-09 — `UPGRADE_BASE_VERSION = "3.0.1+v2.0.0"` is merged to
+cc-ci main, and PR #3 went GREEN level 4 (build 247). Full debrief:
+/srv/cc-ci/.cc-ci-logs/upgrades/plausible-upgrade-2026-06-09.md. Lasting lessons: before
+burning a !testme on an upgrade-stage recipe, check what base version the harness picks
+(`recipe_versions[-2]`) and whether that base can converge; backup-bot-two 2.4.0 ignores v1
+`backupbot.backup.path` labels (use `backupbot.backup.volumes.<vol>.path`, dump INTO a
+volume); clickhouse-backup cannot FREEZE TinyLog tables (ecto's schema_migrations — TSV
+roundtrip needed); BEAM apps exit 0 on supervision escalation, so swarm `restart_policy`
+must be `any`, not `on-failure`. See [[abra-chaos-deploy-checkout-gotcha]].