metheus-governance-mcp-cli 0.2.49 → 0.2.50

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -24,21 +24,19 @@ Install creates a local Telegram settings template here:
24
24
 
25
25
  - `~/.metheus/telegram.env`
26
26
 
27
- This file is for local bot secrets only.
27
+ This file is for the local Telegram bot secret only.
28
28
 
29
29
  - Store locally:
30
30
  - `TELEGRAM_BOT_TOKEN`
31
31
  - Server-side Metheus stores project Telegram destination metadata separately:
32
32
  - `chat_id`
33
33
  - label / active state
34
+ - Do not put project `chat_id` in the local Telegram env file.
34
35
 
35
36
  Example template:
36
37
 
37
38
  ```env
38
39
  TELEGRAM_BOT_TOKEN=
39
- TELEGRAM_DEFAULT_CHAT_ID=
40
- TELEGRAM_ALLOWED_CHAT_IDS=
41
- TELEGRAM_DEFAULT_PARSE_MODE=
42
40
  ```
43
41
 
44
42
  ## One command bootstrap (recommended)
@@ -75,7 +73,7 @@ metheus-governance-mcp-cli setup --project-id <project_uuid> --ctxpack-key "<ctx
75
73
 
76
74
  - `~/.metheus/telegram.env`
77
75
 
78
- Fill only the bot token locally. Project Telegram `chat_id` destinations should be managed on the Metheus server.
76
+ Fill only the bot token locally. Project Telegram `chat_id` destinations should be managed on the Metheus server as project Telegram destinations, not as local env values and not inside Chat Hooks.
79
77
 
80
78
  Gemini CLI note:
81
79
  - `gemini mcp` commands require Gemini auth to be configured first (`GEMINI_API_KEY` or `~/.gemini/settings.json` auth).
package/cli.mjs CHANGED
@@ -487,15 +487,10 @@ function telegramEnvTemplate() {
487
487
  return [
488
488
  "# Metheus local Telegram bot settings",
489
489
  "# Keep this file on your machine only. Do not commit it.",
490
- "# Server-side project Telegram destinations store chat_id metadata separately.",
490
+ "# Store only the Telegram bot token locally.",
491
+ "# Project chat_id must be managed on the Metheus server as a project Telegram destination.",
491
492
  "",
492
493
  "TELEGRAM_BOT_TOKEN=",
493
- "# Optional local default for quick tests. Project chat_id is normally resolved from Metheus server.",
494
- "TELEGRAM_DEFAULT_CHAT_ID=",
495
- "# Optional CSV allowlist to avoid accidental sends to the wrong chats.",
496
- "TELEGRAM_ALLOWED_CHAT_IDS=",
497
- "# Optional parse mode: Markdown, MarkdownV2, HTML",
498
- "TELEGRAM_DEFAULT_PARSE_MODE=",
499
494
  "",
500
495
  ].join("\n");
501
496
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "metheus-governance-mcp-cli",
3
- "version": "0.2.49",
3
+ "version": "0.2.50",
4
4
  "description": "Metheus Governance MCP CLI (setup + stdio proxy)",
5
5
  "type": "module",
6
6
  "files": [
package/postinstall.mjs CHANGED
@@ -16,15 +16,10 @@ function template() {
16
16
  return [
17
17
  "# Metheus local Telegram bot settings",
18
18
  "# Keep this file on your machine only. Do not commit it.",
19
- "# Server-side project Telegram destinations store chat_id metadata separately.",
19
+ "# Store only the Telegram bot token locally.",
20
+ "# Project chat_id must be managed on the Metheus server as a project Telegram destination.",
20
21
  "",
21
22
  "TELEGRAM_BOT_TOKEN=",
22
- "# Optional local default for quick tests. Project chat_id is normally resolved from Metheus server.",
23
- "TELEGRAM_DEFAULT_CHAT_ID=",
24
- "# Optional CSV allowlist to avoid accidental sends to the wrong chats.",
25
- "TELEGRAM_ALLOWED_CHAT_IDS=",
26
- "# Optional parse mode: Markdown, MarkdownV2, HTML",
27
- "TELEGRAM_DEFAULT_PARSE_MODE=",
28
23
  "",
29
24
  ].join("\n");
30
25
  }