chore(catalog): review disclosure for iowap

plugin-catalog/iowap.yaml

@@ -1,7 +1,7 @@
 name: iowap
 repo: https://github.com/iowap-org/iowap-hermes-integration
 sha: 541b42ed40a4bd308e00162d08cf6426fa15db91
-description: "Fleet control for Hermes Desktop: live statusbar chip (N/M IOWAP nodes online), a draggable fleet pane, a full fleet page (status, load, queue depth, capabilities per node, activity) and a tasks page that submits to any task-type capability on the fleet and tracks submitted tasks live (per-stage status dots, result previews, artifacts). The task watcher posts stage/final task updates into the app's chat composer with user-typed authority (fail-closed, never a broadcast; switchable + persisted, a one-time long-run hint for tasks actually claimed beyond 5 minutes) and warns about fleet anomalies (node up/down, relay reachability) under the same toggle. Data stays local via the local node-cli against your own IOWAP relay; agent sessions join through an optional iowap-task bridge into a shared track store. Disclosure — the dashboard backend runs the local node-cli (the IOWAP node client from github.com/iowap-org/iowap-node) to read your relay's node list, capabilities and task results, and to submit tasks you start from the Tasks page to nodes on your IOWAP fleet. Relay health also goes through the local node-cli (`server health`) — the plugin itself makes no raw HTTP calls to the relay; node identity comes from the node's own ~/.relay state files. Tracked task ids are stored in your Hermes home under plugin-data/iowap/. The composer post API is used with the same authority as typing: no hidden broadcasts, no third-party endpoints, messages stay inside the local app."
+description: "Fleet control for Hermes Desktop: live statusbar chip (N/M IOWAP nodes online), a draggable fleet pane, a full fleet page (status, load, queue depth, capabilities per node, activity) and a tasks page that submits to any task-type capability on the fleet and tracks submitted tasks live (per-stage status dots, result previews, artifacts). The task watcher posts stage/final task updates into the app's chat composer with user-typed authority (fail-closed, never a broadcast; switchable + persisted, a one-time long-run hint for tasks actually claimed beyond 5 minutes) and warns about fleet anomalies (node up/down, relay reachability) under the same toggle. Data stays local via the local node-cli against your own IOWAP relay; agent sessions join through an optional iowap-task bridge into a shared track store. Disclosure — the dashboard backend runs the local node-cli (the IOWAP node client from github.com/iowap-org/iowap-node) to read your relay's node list, capabilities and task results, and to submit tasks you start from the Tasks page to nodes on your IOWAP fleet. Relay health also goes through the node-cli, and the plugin makes no raw HTTP calls of its own. Node identity comes from the node's own ~/.relay state files, and tracked task ids are stored in your Hermes home under plugin-data/iowap/. The task and fleet watcher is off by default. When you turn it on, it drafts task-event lines (task name, id and stage status, never node output) into the chat composer, or, in direct mode, which you must choose, sends them with your typing authority into the session that submitted the task or the session you configured. No third-party endpoints."
 maintainer: Kesuek
 tier: community
 category: desktop