#19500: Custom rust ultimate rewrite

## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a new Rust-based runtime agent (`rust-agent/`) that provides security guardrails and defender capabilities for OpenClaw. The implementation includes a WebSocket bridge to the gateway, a multi-layered security evaluation engine (prompt injection, command guard, host integrity, VirusTotal integration), and session state management. **Major changes:** - New Rust agent with 5,305+ lines across 27 files implementing security controls - Defender pipeline evaluates actions via risk scoring (allow/review/block thresholds) - Integration with existing gateway protocol via WebSocket - Idempotency cache and session state persistence - Support for tool and channel policies with configurable risk bonuses - Systemd service configuration for Ubuntu 20.04 deployment **Issues found:** - Compilation error: missing `tracing` import in `rust-agent/src/memory.rs:11` - Silent request dropping when queue saturates (no backpressure signaling) - Duplicate audit_only logic in defender engine causing redundant tags - Session state loading failures silently ignored **Missing from PR description:** - All template fields are empty (no problem description, scope, security impact assessment, verification steps, or evidence) - No migration strategy documented for existing deployments - No backward compatibility analysis <h3>Confidence Score: 2/5</h3> - Not safe to merge due to compilation error and incomplete PR description - Score reflects a critical syntax error preventing compilation, plus multiple logical issues (silent failures, dropped requests, duplicate logic). The implementation architecture is solid with good test coverage, but the PR lacks required documentation and verification evidence. - `rust-agent/src/memory.rs` (compilation error), `rust-agent/src/bridge.rs` (backpressure handling), `rust-agent/src/security/mod.rs` (duplicate audit logic), `rust-agent/src/state.rs` (error handling) _{Last reviewed commit: 7a0dc7a} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->