auto: docs sync 2026-08-15T12:00:04+00:00

Files changed: engine/.embcache.json engine/changelog.md engine/lint-report.md vault/.obsidian/workspace.json vault/docs/hardware/environment.md vault/projects/fleet-storage-memory-upgrade.md vault/projects/navi-recon-separation.md vault/runbooks/corescope-ingest-stall-oom.md vault/runbooks/edge2-access-reference.md vault/runbooks/edge2-boot-recovery.md vault/runbooks/navi-lift-to-media.md vault/runbooks/peertube-sitemap-redis-oom.md

vault/runbooks/corescope-ingest-stall-oom.md

@@ -3,14 +3,13 @@ title: CoreScope Silent Ingest Stall — Diagnosis and Fix
 type: runbook
 tags:
   - mesh
-  - proxmox
 aliases: []
 related:
-  - [[services]]
-  - [[ct-runbook]]
   - [[peertube-sitemap-redis-oom]]
-  - [[environment]]
-  - [[meshcore-transport]]
+  - [[edge2-boot-recovery]]
+  - [[meshtastic-headscale-runbook]]
+  - [[SESSION-HANDOFF-meshai-test]]
+  - [[services]]
 updated: 2026-08-15
 ---
 # CoreScope Silent Ingest Stall — Diagnosis and Fix
@@ -129,7 +128,7 @@ Monitored every three hours for 26 hours after the fix: ingest never stalled, me
 
 ## If it ever recurs
 
-More memory raises the ceiling; it does not cap growth. The next lever is to bound CoreScope itself in `/opt/corescope-data/config.json` — `packetStore.maxMemoryMB` around 320, `retentionHours` 48, and `runtime.maxMemoryMB` around 512 (that last one applies to **both** the server and the ingestor). The config is a **partial override**, so adding keys will not disturb `mqttSources`. Upstream documents this deployment case in issues #836 and #1010.
+More memory raises the ceiling; it does not cap growth. The next lever is to bound CoreScope itself in `/opt/corescope-data/config.json` — `packetStore.maxMemoryMB` around 320, `retentionHours` 48, and `runtime.maxMemoryMB` around 512 (that last one applies to **both** the server and the ingestor). The config is a **partial override**, so adding keys will not disturb `mqttSources`. Upstream documents this [[deployment]] case in issues #836 and #1010.
 
 A flat-`tx_inserted` self-heal watchdog on CT 100 is worth building if the pattern returns, since the container's own watchdog demonstrably stops trying.