feat(blueprints): launch 3 system blueprints, 12 topology layers & in-article mounting

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

@@ -3,6 +3,8 @@ title: "Docker Reported Exit 0. The Kernel Had Already OOM-Killed It."
 description: "A container on my NAS kept stopping unexpectedly while Docker reported exit 0 and OOMKilled=false. The honest evidence was in dmesg: six cgroup OOM kills."
 pubDate: 2026-10-16
 category: devops
+blueprint: self-hosted-infrastructure
+blueprintLayer: L2-edge-proxy-runtime
 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