Pasture: WordPress pinned with its updates off, Mbin's worker restarting, threads checking our own deliveries

A full sweep found three peers silent. WordPress had updated itself to 7.1.2 from WP-Cron, and the new CA bundle dropped
Caddy's root: it now runs the 7.1.2 image with automatic updates off. Mbin's messenger worker had died when the shared
Postgres restarted under it: it now consumes again whenever it stops. Friendica sat in a quarantine left by the old
breaker. The threads scenario checks that PrivaPub never sends carol's reply to Mastodon, since a relay Mastodon has just
left (the relay scenario's) may still pass it on. With these, every scenario passes but the crawler's, which needs it
switched on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

tools/pasture/peers/mbin.sh

@@ -82,8 +82,7 @@ mbin_up() {
 		podman logs pasture-mbin 2>&1 | grep -q "PHP app ready" && break
 		sleep 2
 	done
-	podman run -d --replace --name pasture-mbin-worker "${common[@]}" "$MBIN_IMAGE" \
-		php bin/console messenger:consume scheduler_default old async outbox deliver inbox resolve receive failed --time-limit=86400 >/dev/null
+	mbin_worker
 	for _ in $(seq 1 60); do
 		site mbin.test -s -o /dev/null -w '%{http_code}' https://mbin.test:6443/api/instance 2>/dev/null | grep -q 200 && break
 		sleep 2
@@ -102,3 +101,11 @@ mbin_settle() {
 	mbin_console mbin:user:verify mbuser >/dev/null 2>&1 || true
 	python3 "$here/peers/mbin_token.py" "$MBIN_PASSWORD" "$here/.state/mbin/client.json" > "$here/.state/mbin.token" 2>"$here/.state/mbin/token.log" || true
 }
+
+# mbin_worker: the messenger worker, consuming again whenever it stops (an hour's time limit, or a lost database: a
+# Postgres restarted once left Mbin sending nothing for a day)
+mbin_worker() {
+	podman run -d --replace --name pasture-mbin-worker "${common[@]}" "$MBIN_IMAGE" sh -c 'while :; do
+		php bin/console messenger:consume scheduler_default old async outbox deliver inbox resolve receive failed --time-limit=3600; sleep 5
+	done' >/dev/null
+}