OpenClaw Signals: Resolver Async, Manifest Caching, and Sandbox Tightening

PR

Plugin Resolver Decoupled for Async Manifest Parsing

This PR decouples the plugin resolver from the main executor, letting plugin manifests parse asynchronously while keeping the pipeline responsive under load. For builders running multi-plugin setups, this means fewer blocked threads and cleaner concurrency patterns during cold starts.

Plugin Manifest Caching to Reduce Repeated Parse Overhead

A caching layer for plugin manifests means you only pay the parse cost once per version, not every execution cycle. This is a quick win for anyone dealing with startup latency spikes when loading multiple plugins concurrently.

Sandbox Mount Hardening Restricts Plugin File Access

The sandbox now tightly controls which directories and files a plugin can actually touch during execution, limiting the blast radius of a misbehaving or compromised extension. If you're shipping plugins to customers, this is the kind of defense-in-depth that matters for trust and security.

Issue

OOM Under High Concurrency: Community Debugging Continues

An ongoing investigation into out-of-memory events happening during concurrent plugin execution, with detailed heap dumps and reproduction steps being shared by community contributors. This is critical for everyone running OpenClaw at scale, since uncontrolled memory pressure can cascade into full instance failures.