chore(fleet): sync operator memory, hatch menu dialogs, and watchdog alerts

bin/fleet-alert-check.sh

@@ -19,6 +19,9 @@
 #   FLEET_ALERT_DRY_RUN=1        evaluate + print, write no state/outbox, no notify
 #   FLEET_ALERT_INJECT_FAIL=     test hook: comma-separated condition ids to force-fail
 #                                (e.g. FLEET_ALERT_INJECT_FAIL=cdp:pip)
+#   FLEET_BL_RELAY=1             re-enable the bl-side #lobby relay (default 0/off:
+#                                the container-side hook is the live pager; running
+#                                both double-posts every alert — 2026-10-06)
 #
 # State:  ~/.local/share/fleet-alert/state.json   (per-condition consecutive counters)
 # Outbox: ~/.local/share/fleet-alert/outbox.jsonl (ALERT/RECOVERY records for the relay)
@@ -435,7 +438,11 @@ rm -f "$STATE_DIR/.alerts.tmp"
 tail -500 "$LOG" > "$LOG.tmp" 2>/dev/null && mv "$LOG.tmp" "$LOG"
 log "check complete"
 
-# Relay pending outbox records to #lobby with idempotency gates (posted watermark + content hash TTL)
-if [ "$DRY_RUN" -eq 0 ] && [ -x "$BIN/fleet-alert-relay.sh" ]; then
+# Bl-side #lobby relay: DISABLED by default (FLEET_BL_RELAY=1 to re-enable).
+# The container-side hook is the live pager; the bl relay never successfully
+# posted (missing CHAT_KEYFILE) and enabling it now would double-post every
+# alert in a second format. Re-enable only alongside retiring the container
+# hook (and per the relay header, with opm sign-off).
+if [ "${FLEET_BL_RELAY:-0}" = "1" ] && [ "$DRY_RUN" -eq 0 ] && [ -x "$BIN/fleet-alert-relay.sh" ]; then
     "$BIN/fleet-alert-relay.sh" >> "$LOG" 2>&1 || true
 fi