docs: test postmortem with TODO for pipeline E2E

docs/post-mortems/2026-04-14-postmortem-pipeline-test.md

@@ -3,39 +3,21 @@
 | Field | Value |
 |-------|-------|
 | **Date** | 2026-04-14 |
-| **Duration** | N/A (test incident) |
+| **Duration** | N/A |
 | **Severity** | SEV3 |
 | **Affected Services** | None (test) |
 | **Status** | Draft |
 
 ## Summary
 
-This is a test post-mortem to validate the automated TODO implementation pipeline.
+Test post-mortem for pipeline E2E validation.
-
-## Impact
-
-- **User-facing**: None
-- **Duration**: N/A
-- **Data loss**: None
-
-## Timeline (UTC)
-
-| Time | Event |
-|------|-------|
-| **15:55** | Test post-mortem created |
-
-## Root Cause
-
-Test document — no real root cause.
 
 ## Prevention Plan
 
-### P2 — Test auto-implementation
-
 | Priority | Action | Type | Details | Status |
 |----------|--------|------|---------|--------|
-| P2 | Add Uptime Kuma monitor for PVE SSH port 22 | Monitor | TCP check on 192.168.1.127:22 to detect PVE host unreachable | TODO |
+| P2 | Add Uptime Kuma monitor for PVE SSH port 22 | Monitor | TCP check on 192.168.1.127:22 | TODO |
-| P2 | Review NFS export monitoring strategy | Investigation | Evaluate if node_exporter NFS metrics are sufficient | TODO |
+| P2 | Review NFS monitoring strategy | Investigation | Evaluate node_exporter NFS metrics | TODO |
 
 ## Lessons Learned
 
@@ -43,8 +25,5 @@ Test document — no real root cause.
 
 ## Follow-up Implementation
 
-_This section is auto-populated by the postmortem-todo-resolver agent._
-
 | Date | Action | Priority | Type | Commit | Implemented By |
 |------|--------|----------|------|--------|----------------|
-# Tue Apr 14 04:44:11 PM UTC 2026