metheus-governance-mcp-cli 0.2.250 → 0.2.256
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 +12 -0
- package/cli.mjs +706 -323
- package/lib/bot-commands.mjs +1 -1
- package/lib/local-ai-adapters.mjs +30 -2
- package/lib/provider-local-transport.mjs +5 -0
- package/lib/runner-delivery.mjs +6 -1
- package/lib/runner-helpers.mjs +22 -0
- package/lib/runner-orchestration.mjs +371 -47
- package/lib/runner-runtime.mjs +33 -1
- package/lib/runner-trigger.mjs +25 -18
- package/lib/selftest-runner-scenarios.mjs +777 -44
- package/lib/selftest-telegram-e2e.mjs +101 -59
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -235,6 +235,18 @@ Operational note:
|
|
|
235
235
|
- They are not the authoritative source for parent/root follow-up content.
|
|
236
236
|
- If a user replies to a bot reply, the runner should prefer the persisted authority reply-chain context over generic recent-message scoring.
|
|
237
237
|
|
|
238
|
+
## Telegram Group Privacy
|
|
239
|
+
|
|
240
|
+
Multi-bot Telegram group rooms depend on Telegram-side bot privacy settings, not only local runner code.
|
|
241
|
+
|
|
242
|
+
- `can_read_all_group_messages` is a Telegram bot account capability returned by `getMe`
|
|
243
|
+
- it is not a local `.env` setting
|
|
244
|
+
- mismatched privacy settings across bots can produce inconsistent local inbound visibility and downstream delivery failures
|
|
245
|
+
|
|
246
|
+
See the separate guide:
|
|
247
|
+
|
|
248
|
+
- [`docs/telegram-group-privacy-guide.md`](docs/telegram-group-privacy-guide.md)
|
|
249
|
+
|
|
238
250
|
Built-in helper command for legacy fallback/testing:
|
|
239
251
|
|
|
240
252
|
```bash
|