docs(linkedin): apply consultant audit feedback, reorder by wave schedule, and sync NocoDB status

docs/linkedin/03-running-production-infrastructure-solo.md

@@ -0,0 +1,58 @@
+# LinkedIn Draft & Consultant Review: Running Production Infrastructure Solo: 162 Containers Across Three Hosts
+
+> **文档性质**：从 `blog.hoelee.com` 改写并在 NocoDB 排期的 LinkedIn 生产级动态。
+> **发布状态**：`已通过外部顾问审阅 / NocoDB 已排期待发布`
+> **排期波次**：Wave 1 (立威期) - 槽位 3 (拟发布日期: 2026-11-05 Thu)
+> **源文章**：https://blog.hoelee.com/posts/running-production-infrastructure-solo/
+> **系统标识**：`running-production-infrastructure-solo` | **分类**：`case-studies`
+> **字数**：2223 chars (严格控制在 3,000 字符内)
+
+---
+
+## 一、 核心背景与铁律约束提示（供复核对照）
+
+1. **求职画像契合（Senior 全栈/DevOps/AI 架构师）**：彻底脱敏“做生意的老板/小公司创始人”倾向；一切商业实战均转换为“生产系统架构、高可用交付与自动化运维”视角。
+2. **纯洁人设与零禁用词**：绝对禁止 `homelab`, `home lab`, `家用`, `小主机`, `玩具`, `折腾`, `玩票` 等词汇。必须使用 `the infrastructure I manage`, `my self-hosted production nodes`, `production host`。
+3. **第一人称单数**：统一使用单数 `I` / `我`，杜绝虚张声势的复数 `we`。
+4. **数据绝对保真**：所有数字、性能比率、吞吐提升、故障现象严禁凭空捏造。
+5. **OPSEC 安全脱敏**：无内部绝对路径（如 `D:/dev`），无真实私有内网 IP，公网 IP 必须转为文档保留地址。
+
+---
+
+## 二、 LinkedIn 拟发布动态文案（已按顾问意见修订）
+
+```text
+I run 162 Docker containers across three self-managed production hosts with 78 compose stacks — serving public client applications, mail infrastructure, workflow automation, and CI/CD pipelines.
+
+Operating at that density without leaning on a sprawling ops team or five-figure managed cloud PaaS bills forces strict architectural discipline.
+
+When you manage an estate of that density solo, you learn quickly that conventional dashboard metrics are dangerous. Two real-world production failures changed how I audit my systems:
+
+1. The silent database dashboard disconnect
+My analytics dashboard (NocoDB) was happily displaying rows and answering HTTP 200. Downstream, the background replication worker had dropped its database socket four hours earlier. The UI was serving cached metadata from memory while live mutations stalled. A green dashboard is not health; transactional read-after-write verification is health.
+
+2. The zero-config daemon lockup
+A credential management container hung on startup after a routine patch. Docker health checks passed because PID 1 stayed alive, but reverse-proxy requests timed out with HTTP 504. The culprit? An empty GPG keyring directory in a newly mounted volume triggered a blocking interactive entropy prompt inside the daemon. Health checks that probe process existence rather than live application handshakes will always deceive you.
+
+My operational rules for running production infrastructure solo:
+• Segregate workloads by isolation boundary: public ingress and edge routing live on a dedicated VPS; core storage and identity live behind private gateways.
+• Telemetry must be completely decoupled from application runtimes.
+• If an alert is based on an arbitrary percentage ratio instead of absolute time-to-exhaustion, delete it.
+
+When you operate both the codebase and the host it runs on, there is no finger-pointing between the developer and the infrastructure provider. You own the transport layer as completely as the application layer.
+
+For those running dense container footprints: what is your primary watchdog test to catch a service that is technically "running" but practically dead?
+
+Write-up: https://blog.hoelee.com/posts/running-production-infrastructure-solo/
+```
+
+---
+
+## 三、 外部顾问审阅评估反馈单与归档记录
+
+- [x] **审阅结论**：通过（已微调）
+- **1. 诊断与修改批注**：按顾问建议微调第 2 段，将无团队/不用 PaaS 转化为高密度单位经济效益与架构严谨度。
+- **2. NocoDB 归档记录**：
+  - Candidate Key: `cand:running-production-infrastructure-solo` (Status: `APPROVED`, Priority: `HIGH`)
+  - Draft Key: `cand:running-production-infrastructure-solo:v1` (Status: `APPROVED`)
+  - 拟定发布节奏：每周 2 篇（周二/周四），平稳推进 5 周。