C/C++ Security Review Runs in the main conversation (invoke via ). Orchestrator owns the ledger as bookkeeping for retries; workers and judges have no Task tools. Workers and judges are named plugin subagents ( , , ); tool sets are declared in . Findings are exchanged via markdown-with-YAML files in a shared output directory. When to Use Native C/C++ application security review: memory safety, integer overflow, races, type confusion, Linux/macOS daemons, Windows userspace services. When NOT to Use - Kernel drivers/modules (Linux, Windows, macOS). - Managed languages (Java, C#, Python, Go, Rus…