Camera agent Nest/WebRTC placeholder response: non-actionable truncation is upstream provider issue

_{lesson · created 2026-08-02 · actor brain-distill · confidence medium · status active tags: infra camera reliability}

When home-camera-vision-sweep returns non-analyzable 2689-byte Nest/WebRTC placeholder content with response truncation, the failure is a provider-side issue (camera stream encoding, truncation threshold), not a local infrastructure problem. Do not mark as infrastructure failure or restart gateways. Detect and skip these in health checks: camera pre-run reported actionable_failed_count=0 means the camera collector itself found nothing actionable. The response truncation and placeholder bytes are not locally repairable without rerunning the external job against a different camera frame provider.

---

_{Sources: /Users/dwayne/clawd/memory/health-remediation.log}