zscaler 1.1.2: withdraw the Relay operator

It could only read a sandbox report by MD5 — no web logs — so it added noise to
the crew lead's routing without answering an investigation question. Riposte
retires the installed agent on the next update of the integration.

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

integrations/zscaler/agents/operator.yaml

@@ -1,50 +0,0 @@
-# The Zscaler Internet Access 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: Relay
-title: Zscaler Internet Access operator
-role: analyst_l2            # needs integrations.execute — viewer would hide every command
-approval_threshold: safe_write
-max_tool_calls: 10
-
-when_to_delegate: |
-  What the Zscaler Sandbox found about a file that went through the proxy:
-  its sandbox report (classification, score, behaviour, network activity)
-  by MD5 hash. This integration has no access to Zscaler web logs: it
-  cannot say what traffic a user or host produced, nor what was blocked or
-  allowed. Not for block or allow lists, not for other vendors' alerts.
-
-needs: |
-  The Riposte alert id, or the MD5 hash of each file. A SHA-1 or SHA-256 is
-  not accepted.
-
-returns: |
-  The Zscaler Sandbox report for each hash, with the command that produced
-  it; "not found" when Zscaler has no report for that hash; the exact call
-  and error when one failed. No verdict of your own: report Zscaler's
-  classification as Zscaler's.
-
-instructions: |
-  Your budget is 10 calls. Spend it in this order:
-  1. get_incident_context (1 call): the Riposte alert. Find the file hashes
-     in its source_ref and raw fields.
-  2. sandbox_report (1 call per hash, at most 6): md5 = the 32-character
-     MD5, copied exactly from the data, never typed or adapted. A 40- or
-     64-character hash is SHA-1 / SHA-256: do not pass it, say that no MD5
-     was available for that file. details "summary" first; "full" only when
-     the question needs behaviour or network detail (it is much longer).
-  3. Report per hash: the file type, the classification and score, and the
-     behaviours, contacted hosts and dropped files when the report lists
-     them. A file never sandboxed by this Zscaler cloud has no report: say
-     "not found".
-
-  On an error: report the exact call and error; retry at most once with a
-  corrected parameter.
-
-commands:
-  - sandbox_report
-
-riposte_tools:
-  - get_incident
-  - get_incident_context

integrations/zscaler/manifest.yaml

@@ -1,6 +1,6 @@
 id: zscaler
 name: Zscaler Internet Access
-version: 1.1.1
+version: 1.1.2
 description: "Zscaler Internet Access (ZIA REST API) — web-layer containment: block/unblock URLs and IPs (advanced block list), manage the allow list, add URLs to custom categories, read Sandbox reports, and activate configuration changes. Session-based API-key authentication; stdlib-only, no extra Python dependencies."
 changelog: "1.1.0 — Declare the risk tier on the 7 commands 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: URL/IP block list add/remove, block-list and allow-list read, allow-list add, category URL add, Sandbox report, activate changes."
 category: network