feat(content): implement consultant review recommendations (executive summary, dynamic cta, homelab cleanup)

src/content/posts/docker-reported-exit-0-the-oom-killer-disagreed.md

@@ -7,6 +7,22 @@ tags: ["docker", "oom", "traefik", "synology", "crawlers"]
 ogImage: /og/docker-reported-exit-0-the-oom-killer-disagreed.jpg
 banner: /banners/docker-reported-exit-0-the-oom-killer-disagreed.jpg
 draft: false
+summary:
+  audience: "SREs, DevOps Leads & Systems Engineers"
+  painPoint: "A public edge proxy (Traefik) crashed 7 times over 4 days while Docker daemon reported ExitCode=0 and OOMKilled=false, rendering standard monitoring completely blind."
+  impact:
+    - metric: "Exposed Root Cause"
+      detail: "Bypassed Docker's false status via kernel dmesg and cgroup high-water marks, pinning the crash to 25,976 crawler IPs hitting a 512MB limit."
+    - metric: "Zero-Downtime Hotfix"
+      detail: "Hot-scaled proxy container to 2GB with memory swap locked, dropping peak memory to 210MB in 18 minutes with 0 subsequent crashes."
+    - metric: "Anti-Lockout SOP"
+      detail: "Established edge crawler stress-testing and verified probe procedures to prevent diagnostic self-lockout from security filters."
+  stack: ["Docker", "Linux Kernel (dmesg/cgroups)", "Traefik", "Synology DSM", "Security Filtering"]
+  jumpLinks:
+    business: "#the-result"
+    architecture: "#the-kernel-keeps-its-own-record"
+    result: "#what-i-would-do-differently"
+dynamicCta: true
 ---
 
 ## The notification I expected to be a config mistake