review(MEM-20260819-C255FF): gen

data/generated/site_state.json

@@ -1,10 +1,10 @@
 {
   "version": 2,
-  "generated_at": "2026-08-20T07:05:46Z",
-  "source_sha256": "d86b72c1246db9a0e1be3bba18038b23d95fe9d406c873a34dcde198af698baf",
+  "generated_at": "2026-08-24T18:25:00Z",
+  "source_sha256": "73d66ea39e4def01d7ccf1993b29bbfd832e893c7926a96dc842bc02d70f6044",
   "stats": {
     "active_admins": 1,
-    "pending_reviews": 5,
+    "pending_reviews": 4,
     "open_tasks": 1,
     "active_projects": 1
   },
@@ -109,31 +109,6 @@
       ],
       "required_count": 1,
       "reviewed_count": 0
-    },
-    {
-      "entry_id": "MEM-20260819-C255FF",
-      "title": "Desplegar Uptime Kuma como monitoreo central (health.mcps-epcm.org)",
-      "description": "Contenedor Uptime Kuma en mcps-hpc-01 con 22 monitores en 3 grupos; gotcha de systemd Type=notify que causaba reinicio en loop.",
-      "date": "2026-08-19T18:55:56Z",
-      "author_id": "gen",
-      "risk": "low",
-      "tags": [
-        "monitoreo",
-        "systemd",
-        "uptime-kuma"
-      ],
-      "systems": [
-        "mcps-hpc-01",
-        "uptime-kuma"
-      ],
-      "permalink": "/memorias/mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org/",
-      "content_sha256": "a74e4f1493843970c55c3197fb2e5266c8b04cf631e7fd187890051a0f076686",
-      "reviewed_by": [],
-      "missing_reviewers": [
-        "gen"
-      ],
-      "required_count": 1,
-      "reviewed_count": 0
     }
   ],
   "recent_memories": [