OpenClaw Signals: Deletion Guardrails, Probe Coverage, and the OOM Grind Continues

Tools

Safe Recursive Deletion Utility Merged

This PR adds guardrails around recursive file deletion so a bad path or symlink loop cant nuke more than intended. Small change but it closes a real footgun that shows up once you let agents touch the filesystem unsupervised.

System Probe Coverage Expanded

New probes check resource limits and process health before handing off tasks, which should catch failure modes earlier instead of letting them cascade into the OOM mess. Good defensive engineering, not flashy but it matters at scale.

Plugin Resolver Gets Async Treatment Again

Another pass at making the plugin resolver non-blocking, this time focused on manifest parsing under concurrent load. Feels like theyre circling the real bottleneck but havent fully landed it yet.

Sandbox Mount Hardening Follow-Up

Tightens which paths plugins can mount into their sandbox, closing off a class of escape routes. Necessary if youre letting third party plugins run near anything sensitive.

Retry Backoff Jitter Tuning Continues

The jitter algorithm keeps getting refined to avoid thundering herd retries under load. Incremental but it's the kind of thing that actually prevents outages once you're running this at any real volume.

Analysis

OOM Under Concurrency Still Open

This issue keeps getting new theories thrown at it, memory leaks in the manifest cache, unbounded retry queues, plugin instances not getting garbage collected. Anyone running OpenClaw at any real scale should be watching this thread closely before they hit the same wall in production.