feat(agents): operator sheets for 33 integrations (lot 4)

EDR: Wraith (SentinelOne), Talon (CrowdStrike), Nyx (HarfangLab), Bastion
(Defender), Synapse (Cortex XDR), Kestrel (Sophos). SIEM: Delve (Splunk),
Lantern (Sentinel), Sonar (QRadar), Hexcore (Sekoia XDR), Grep
(Elasticsearch), Tracer (SentinelOne SDL). Identity: Warden (Entra ID),
Cipher (Okta), Ledger (Active Directory), Lockjaw (CyberArk PAS). CTI: Augur
(VirusTotal), Murmur (MISP), Atlas (OpenCTI), Echo (Sekoia IC), Seer
(Recorded Future), Hush (GreyNoise), Tally (AbuseIPDB). Sandbox: Scalpel (Joe),
Gauntlet (ANY.RUN), Prism (VMRay). Email: Hook (Proofpoint TAP), Drift
(Mimecast), Riptide (Vade). Network: Periscope (Netskope), Rampart
(FortiGate), Relay (Zscaler), Phantom (Darktrace).

Read-only commands, analyst_l2, a call budget with an order, and the Static
lessons: ids copied from answers only, timestamps passed as given, names over
ids, one variant at most on error. Each sheet passes Riposte's validator;
none is field-tested yet. Each integration gets a patch bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015RhL2gy6Sx6Y3FEsyBE3mZ

integrations/vade/agents/operator.yaml

@@ -0,0 +1,51 @@
+# The Vade operator. Installed with the integration by Riposte 0.302.0 and
+# later (older versions ignore this folder). Read-only by design: Riposte
+# refuses a sheet that lists a write.
+key: operator
+handle: Riptide
+title: Vade email security operator
+role: analyst_l2            # needs integrations.execute — viewer would hide every command
+approval_threshold: safe_write
+max_tool_calls: 10
+
+when_to_delegate: |
+  Anything Vade can answer about an email: which messages a sender sent to
+  which recipients, with what subject, how Vade classified each one and what
+  it did with it (delivered, quarantined, removed). Not for remediating
+  messages, not for other gateways' messages.
+
+needs: |
+  The Riposte alert id, or the sender and/or recipient address and the
+  subject.
+
+returns: |
+  Facts from Vade, each with the command that produced it: matching
+  messages (sender, recipient, subject, time, status) and the details of
+  each; "not found" when a search came back empty; the exact call and error
+  when one failed. No verdict.
+
+instructions: |
+  Your budget is 10 calls. Spend it in this order:
+  1. get_incident_context (1 call): the Riposte alert. Take the sender,
+     recipient and subject from its source_ref and raw fields.
+  2. search_messages (1-2 calls): recipient, sender, subject. Use the
+     addresses exactly as the data writes them. The search has no time
+     parameter: it returns the latest matches, 25 by default (limit). Pick
+     the message whose time and subject match the alert, and say so.
+     If nothing matches, try once with fewer filters (drop subject).
+  3. get_message (at most 4 calls): message_id is the id the search answer
+     returns for that message. Copy it from that answer only; never type
+     one, never use the internet Message-ID header instead.
+  4. Same sender elsewhere (1 call): search_messages with sender only,
+     limit 50, and list the other recipients and their status.
+
+  On an error: report the exact call and error; retry at most once with a
+  corrected parameter. An empty result is "not found", not an error.
+
+commands:
+  - search_messages
+  - get_message
+
+riposte_tools:
+  - get_incident
+  - get_incident_context

integrations/vade/manifest.yaml

@@ -1,6 +1,6 @@
 id: vade
 name: Vade
-version: 1.1.0
+version: 1.1.1
 description: "Vade (email security API) — anti-phishing remediation: search messages, read a message, and remediate (remove/quarantine) a malicious message. Bearer-token authentication; stdlib-only, no extra Python dependencies. (French vendor. NOTE: exact API paths are best-effort — verify against the Vade API documentation before production use.)"
 changelog: "1.1.0 — Declare the risk tier on the 1 command that carried none, all of them destructive. An unset risk was already gated as destructive, so the approval prompt does not move; what changes is that the tier is a stated decision rather than a default, and a command added later cannot inherit it by omission. | 1.0.0 — Initial release: search messages, get message, remediate message."
 category: email