metheus-governance-mcp-cli 0.2.232 → 0.2.242
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 +31 -0
- package/cli.mjs +18613 -18167
- package/lib/local-ai-adapters.mjs +49 -22
- package/lib/provider-local-transport.mjs +21 -20
- package/lib/runner-delivery.mjs +13 -0
- package/lib/runner-orchestration.mjs +220 -241
- package/lib/runner-trigger.mjs +104 -17
- package/lib/selftest-telegram-e2e.mjs +18 -17
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -204,6 +204,37 @@ Fill provider bot secrets and provider-local transport options locally. Project
|
|
|
204
204
|
- which `project_id -> workspace_dir` mapping to apply locally
|
|
205
205
|
- which workspace source updated that mapping last
|
|
206
206
|
|
|
207
|
+
## Runner Reply-Chain Context
|
|
208
|
+
|
|
209
|
+
Runner follow-up handling is context-first.
|
|
210
|
+
|
|
211
|
+
- Follow-up human replies and bot replies are resolved from the reply chain first.
|
|
212
|
+
- The authoritative source is the normalized runner authority context:
|
|
213
|
+
- `conversation_id`
|
|
214
|
+
- parent/root message linkage
|
|
215
|
+
- persisted conversation contract
|
|
216
|
+
- next expected responders / summary bot
|
|
217
|
+
- The runner also persists authoritative prior-turn content for follow-up requests:
|
|
218
|
+
- `source_message_body`
|
|
219
|
+
- `reply_chain_context`
|
|
220
|
+
- `root_message`
|
|
221
|
+
- `parent_message`
|
|
222
|
+
- `latest_prior_bot_reply`
|
|
223
|
+
- `recent_chain_messages`
|
|
224
|
+
|
|
225
|
+
Design rule:
|
|
226
|
+
|
|
227
|
+
- `reply chain` is not a policy branch tree.
|
|
228
|
+
- `reply chain` is an authority input used once to build normalized context.
|
|
229
|
+
- AI should be controlled by `agent_context`, `conversation`, `project_context_items`, and authoritative `reply_chain_context`.
|
|
230
|
+
- Code should validate, record, and deliver. It should not reinterpret follow-up meaning from trigger heuristics after context is built.
|
|
231
|
+
|
|
232
|
+
Operational note:
|
|
233
|
+
|
|
234
|
+
- `context_comments` / context window are supplementary recent context only.
|
|
235
|
+
- They are not the authoritative source for parent/root follow-up content.
|
|
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
|
+
|
|
207
238
|
Built-in helper command for legacy fallback/testing:
|
|
208
239
|
|
|
209
240
|
```bash
|