From 651350b2dea5bd070d32082c76cce0f4bfca0de4 Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Mon, 5 Oct 2026 23:34:15 -0700
Subject: [PATCH] chore(plugin-catalog): bento disclosure at merge

Applies the reviewed Disclosure line from the catalog sweep review (catalog PR #133524).
---
 plugin-catalog/bento.yaml | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/plugin-catalog/bento.yaml b/plugin-catalog/bento.yaml
index 45d128964c..abc909be05 100644
--- a/plugin-catalog/bento.yaml
+++ b/plugin-catalog/bento.yaml
@@ -1,14 +1,7 @@
 name: bento
 repo: https://github.com/shagghiesuperstar/hermes-plugin-bento
 sha: "f490ed02c0e377acc9112bf57192bacedbbcd9b1"
-description: >-
-  Bento (bentonow.com) email marketing: subscribers, tags, fields, events incl. $purchase, stats,
-  draft/scheduled broadcasts and transactional email, with dry-run + human-approval gates on every
-  send. Native Python plugin, no dependencies. Disclosure: sends real email and can trigger Bento
-  Flows; calls only app.bentonow.com with your keys from .env; no telemetry; no self-update;
-  the approval gate fails closed under cron/gateway only while approvals.cron_mode is not
-  "approve" (with cron_mode=approve, or YOLO, no human is asked; the token and hard guards
-  still apply). environment=staging does not block sends; only environment=disabled does.
+description: "Bento (bentonow.com) email marketing: subscribers, tags, fields, events incl. $purchase, stats, draft/scheduled broadcasts and transactional email, with dry-run + human-approval gates on every send. Native Python plugin, no dependencies. Disclosure — sends real email (bento_email_send, bento_broadcast_schedule), and events, purchases and consent changes can trigger Bento Flows that email people; calls only app.bentonow.com (an operator base_url override is limited to https *.bentonow.com or loopback) with the BENTO_* keys from the profile .env; no telemetry, no self-update; T2/T3 calls go to the Hermes approval prompt, which asks no human under YOLO, approvals.mode off, or cron/single-query/unattended mode set to approve. T3 sends then still need a dry-run confirm token and hard guards, but T2 writes (events, purchases, consent, bulk upserts) need no token unless safety.tier2 is token_only; T1 writes (tags, tag/field definitions, drafts, upserts up to bulk_threshold) are never gated and still run under environment=disabled; environment=staging does not block sends, only environment=disabled blocks T2/T3."
 maintainer: shagghiesuperstar
 tier: community
 category: tools