fix(ops): close post-reboot recovery guardrails

ops/reboot-recovery/full-stack-cold-start-baseline.yml

@@ -289,9 +289,10 @@ resource_guardrails:
       persist_in: /opt/sentry/docker-compose.override.yml
     sentry_self_hosted_memory_limits:
       taskscheduler_mem_limit: 1g
-      relay_mem_limit: 2g
+      relay_mem_limit: 3g
+      relay_memswap_limit: 4g
       persist_in: /opt/sentry/docker-compose.override.yml
-      note: "taskscheduler/relay 不得回退到 512m/1g 造成長期 >85% memory-limit pressure；110 主機仍以 ClickHouse/Kafka/Snuba CPU caps 防止冷啟動過載。"
+      note: "taskscheduler 不得回退到 512m/1g；relay 不得回退到 2g 或以下造成長期 >85% memory-limit pressure；110 主機仍以 ClickHouse/Kafka/Snuba CPU caps 防止冷啟動過載。"
     actions_runner_systemd:
       cpu_quota: 200%
       memory_max: 2G
@@ -310,6 +311,12 @@ resource_guardrails:
     momo_scheduler:
       cpus: 2.0
       memory: 2G
+    momo_db:
+      cpus: 2.0
+      memory: 4G
+      memswap: 6G
+      restart_policy: unless-stopped
+      note: "2026-07-01 live recovery 將 momo-db 補上 Docker resource guardrail；不得回退到 nanocpus=0 / memory=0 / memswap=0。"
     signoz_clickhouse:
       memory: 24G
       note: do_not_lower_during_merge_backlog