chore(catalog): review disclosure for operations

plugin-catalog/operations.yaml

@@ -3,7 +3,7 @@ repo: https://github.com/c-pompa/operations-hermes-desktop-plugin
 sha: 56e4d650652770acc634ad65d6d9b1c4b29907e5
 subdir: plugins/operations
 title: Operations
-description: "A Hermes Desktop page for running a fleet - topology, model traffic, handoffs, traces, merge requests and conformance checks in one place. Disclosure — reads hermes-metrics-dash's <hermes root>/metrics/metrics.db, the kanban board, every profile's config.yaml (plugin enable state, rolectl-mcp entries, default model) and plugin-data/gitlab-mr/device-aliases.json, all read-only; calls your GitLab (host and token from the plugin settings or GITLAB_HOST/GITLAB_TOKEN), the local model router (MODEL_ROUTER_URL, default 127.0.0.1:8867) and LM Studio (LMSTUDIO_URL, default 127.0.0.1:1234); runs git status/rev-parse/ls-files in the project folders it checks and shows matching lines (including any keys found) on the page. Page buttons create, assign, schedule, unblock and close kanban cards and start their workers at once, write <hermes root>/conformance/conformance.yaml, and \"Propose a rule\" pushes a branch and opens a merge request on the standard's GitLab project. A hook on every kanban dispatcher tick starts cards scheduled from the page; with alert_target set it posts new attention items through hermes send; with drift_action: automatic it files and starts a fix card for drift_profile for each drifting host with a verified report (at most daily) carrying the standard's remediate commands. With Activity summaries on (off by default), Activity sentences and each \"Explain this session\" click send log lines and trace details to the model set for the operations_summary auxiliary task. From the setup checklist's Connect GitLab step it can also adopt this profile's own login - its environment read through Hermes' secret scope, or the host the gitlab-mr plugin names - or take a host and token typed on the page; the host goes through the plugin-settings writer and the token through Hermes' .env credential route as OPERATIONS_GITLAB_TOKEN, and the token is never sent back to the page. No other credential store is read: a login that exists only in another profile's .env or in the glab CLI's config is typed in instead. Since 0.3.5 the plugin keeps its own metrics store: it tails <hermes root>/metrics/requests.jsonl and moa-refs.jsonl, guardrail lines in logs/agent.log, logs/model-router-requests.jsonl and clientgate/clientgate-usage.jsonl (all read-only, offset-tracked) plus its own host probes into <hermes root>/metrics/operations.db, which this plugin alone writes and prunes to the metrics_retention_days setting (30/60/90 days or forever, chosen on the page and written through Hermes' plugin-settings writer); hermes-metrics-dash's metrics.db is then only a read-only fallback until the own store holds data. It probes the local metrics dashboard's /api/about (METRICS_DASH_URL, default 127.0.0.1:8899, cached five minutes) to link to it rather than duplicate it, and when no kanban dispatcher tick arrives, a single daemon timer runs the alert sweep itself and the page says so. Since 0.3.4 a failed model call is classified with the host app's own error classifier and shown with its cause and remedy commands; no new outbound call is made for that."
+description: "A Hermes Desktop page for running a fleet - topology, model traffic, handoffs, traces, merge requests and conformance checks in one place. Disclosure — reads hermes-metrics-dash's <hermes root>/metrics/metrics.db, the kanban board, every profile's config.yaml (plugin enable state, rolectl-mcp entries, default model) and plugin-data/gitlab-mr/device-aliases.json, all read-only; calls your GitLab (host and token from the plugin settings or GITLAB_HOST/GITLAB_TOKEN), the local model router (MODEL_ROUTER_URL, default 127.0.0.1:8867) and LM Studio (LMSTUDIO_URL, default 127.0.0.1:1234); runs git status/rev-parse/ls-files in the project folders it checks and shows matching lines (including any keys found) on the page. Page buttons create, assign, schedule, unblock and close kanban cards and start their workers at once, write <hermes root>/conformance/conformance.yaml, and \"Propose a rule\" pushes a branch and opens a merge request on the standard's GitLab project. A hook on every kanban dispatcher tick starts cards scheduled from the page; with alert_target set it posts new attention items through hermes send; with drift_action: automatic it files and starts a fix card for drift_profile for each drifting host with a verified report (at most daily) carrying the standard's remediate commands. With Activity summaries on (off by default), Activity sentences and each \"Explain this session\" click send log lines and trace details to the model set for the operations_summary auxiliary task. From the setup checklist's Connect GitLab step it can also adopt this profile's own login - its environment read through Hermes' secret scope, or the host the gitlab-mr plugin names - or take a host and token typed on the page; the host goes through the plugin-settings writer and the token through Hermes' .env credential route as OPERATIONS_GITLAB_TOKEN, and the token is never sent back to the page. No other credential store is read: a login that exists only in another profile's .env or in the glab CLI's config is typed in instead. Since 0.3.5 the plugin keeps its own metrics store: it tails <hermes root>/metrics/requests.jsonl and moa-refs.jsonl, guardrail lines in logs/agent.log, logs/model-router-requests.jsonl and clientgate/clientgate-usage.jsonl (all read-only, offset-tracked) plus its own host probes (CPU and memory via sysctl/vm_stat or PowerShell, LM Studio's lms ps, and every five minutes the local conformance.yaml's install-stamp, launchd/scheduled-task, loopback-port and key-name checks), and reads session titles and costs from <hermes root>/state.db and every profile's gateway_state.json (read-only), into <hermes root>/metrics/operations.db, which this plugin alone writes and prunes to the metrics_retention_days setting (30/60/90 days or forever, chosen on the page and written through Hermes' plugin-settings writer); hermes-metrics-dash's metrics.db is then only a read-only fallback until the own store holds data. It probes the local metrics dashboard's /api/about (METRICS_DASH_URL, default 127.0.0.1:8899, cached five minutes) to link to it rather than duplicate it, and every Hermes process that loads the plugin starts a daemon timer: when no kanban dispatcher tick has arrived for two minutes it runs the same sweep itself every 30 seconds (collection, alerts and, with drift_action: automatic, the fix cards), and the page says so; OPERATIONS_HEARTBEAT_TIMER=0 turns that timer off. Since 0.3.4 a failed model call is classified with the host app's own error classifier and shown with its cause and remedy commands; no new outbound call is made for that."
 maintainer: c-pompa
 tier: community
 category: desktop