metheus-governance-mcp-cli 0.2.60 → 0.2.62

package/README.md

@@ -84,7 +84,7 @@ Runner template:
         "mentions_only": true,
         "direct_messages": true,
         "reply_to_bot_messages": true,
-        "ignore_edited_messages": false
+        "ignore_edited_messages": true
       },
       "archive_policy": {
         "mirror_replies": true,
@@ -182,6 +182,7 @@ Guardrail note:
 
 ```bash
 metheus-governance-mcp-cli doctor --project-id <project_uuid> --base-url https://metheus.gesiaplatform.com
+metheus-governance-mcp-cli doctor --project-id <project_uuid> --base-url https://metheus.gesiaplatform.com --strict true
 ```
 
 Checks:
@@ -190,6 +191,7 @@ Checks:
 - local bot runner v2 config validity
 - project workspace mapping presence
 - role profile -> local CLI availability
+- route dry-run / trigger-policy safety warnings
 - local provider token presence for active project destinations
 - codex/claude/gemini/antigravity/cursor registration state
 - gateway `tools/list` reachability
@@ -197,16 +199,25 @@ Checks:
 - ctxpack auto sync status
 - smoke calls: `workitem.list`, `evidence.list`, `decision.list`
 
+`--strict true` upgrades local runner route safety warnings into failures.
+Use it for production validation before enabling long-running bot routes.
+
 Direct bot posting:
 - `me.send-bot-message` uses local provider tokens from `~/.metheus/<provider>.env`
 - it does not use a server-stored bot token
 - the destination identifier is resolved from the current project's saved Chat Destinations on the Metheus server
 - if multiple active destinations exist for the same provider, pass `destination_id` or `destination_label`
+- pass `dry_run_delivery=true` to preview the resolved bot/destination locally without sending the provider message
 - direct local delivery is implemented today for:
   - Telegram
   - Slack
 - KakaoTalk profiles and destinations can be stored now, but direct local delivery is not implemented yet
 
+Provider support matrix in this CLI:
+- `telegram`: local token verification, direct local delivery, typing, reply-to-message, and automatic inbound runner are implemented
+- `slack`: local token verification and direct local delivery are implemented, but automatic inbound runner is not
+- `kakaotalk`: local config can be stored, but token verification, direct local delivery, and automatic inbound runner are not implemented
+
 ## Local bot runner
 
 The local runner closes the loop:
@@ -224,23 +235,28 @@ Execution model:
 - runner resolves `project_id -> workspace_dir`
 - runner resolves server bot role to a local `role_profile`
 - runner executes the mapped client adapter (`codex` / `claude` / `gemini`)
-- legacy `command` remains supported only as fallback for older configs
+- legacy `command` remains readable for migration, but execution is disabled by default unless `METHEUS_ALLOW_LEGACY_RUNNER_COMMAND=1`
 
 Commands:
 
 ```bash
-metheus-governance-mcp-cli runner once
-metheus-governance-mcp-cli runner start
+metheus-governance-mcp-cli runner once --route-name telegram-monitor
+metheus-governance-mcp-cli runner start --route-name telegram-monitor
 ```
 
-Common flags:
+Recommended operational path:
+
+```bash
+metheus-governance-mcp-cli runner once --route-name telegram-monitor --dry-run-delivery true
+metheus-governance-mcp-cli runner start --route-name telegram-monitor
+```
+
+Debug/selection overrides:
 
 ```bash
 metheus-governance-mcp-cli runner once --project-id <project_uuid> --provider telegram --role monitor
 metheus-governance-mcp-cli runner start --project-id <project_uuid> --provider telegram --role monitor --poll-interval-ms 5000
-metheus-governance-mcp-cli runner start --project-id <project_uuid> --provider telegram --role monitor --mentions-only true
 metheus-governance-mcp-cli runner once --project-id <project_uuid> --provider telegram --role monitor --role-profile review
-metheus-governance-mcp-cli runner once --project-id <project_uuid> --provider telegram --role monitor --command "python C:\\path\\to\\reply.py"
 ```
 
 Recommended production path:
@@ -262,6 +278,11 @@ Role profile fields:
 - `permission_mode`: `read_only`, `workspace_write`, `danger_full_access`
 - `reasoning_effort`: `low`, `medium`, `high`
 
+Role profile note:
+- Claude maps `reasoning_effort` to `--effort`.
+- Codex maps `reasoning_effort` to `-c model_reasoning_effort="..."`.
+- Gemini CLI still has no dedicated effort flag, so the runner keeps the value in env/prompt context for policy parity.
+
 Trigger policy fields:
 - `mentions_only`: in groups, react only when the bot is mentioned or when a message replies to the bot
 - `direct_messages`: allow or block private chat messages
@@ -299,14 +320,19 @@ Notes:
 - `runner once` processes the most recent pending archived inbound message
 - `runner start` keeps polling and stores per-route cursor state in `~/.metheus/bot-runner-state.json`
 - first start primes the cursor to the latest inbound message and does not reply to old backlog
+- when inline filters match a configured route in `~/.metheus/bot-runner.json`, the runner reuses that route's canonical name/destination and state cursor instead of creating a new anonymous route key
+- stale anonymous route keys in `~/.metheus/bot-runner-state.json` are auto-migrated to the matching configured route when possible; `doctor` warns if ambiguous legacy keys still remain
+- `--dry-run-delivery true` resolves the real bot and destination but skips provider send and archive mirror writes
 - when `trigger_policy.mentions_only=true`, unmentioned group messages are archived but skipped for reply generation
 - mirrored bot replies are deduped by `chat_id + message_id`
 - provider bot messages are ignored during inbound import by default
 - `local-bot-bridge` reads stdin JSON from the runner and can call Codex/Claude/Gemini for you
+- `route.command` fallback is disabled by default; enable it only temporarily with `METHEUS_ALLOW_LEGACY_RUNNER_COMMAND=1`
 - today this automation path is implemented for Telegram end-to-end
 - set `METHEUS_TELEGRAM_API_BASE_URL=http://127.0.0.1:<port>` only for local mock or regression testing; normal usage should keep the default Telegram API base
 - Slack can use direct local send, but automatic inbound runner flow is not completed yet
 - KakaoTalk config can be stored now, but direct send/runner flow is not implemented yet
+- `doctor` now reports provider support for both enabled runner routes and active project chat destinations
 
 ## Use in MCP