metheus-governance-mcp-cli 0.2.47 → 0.2.48
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 -14
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -50,17 +50,10 @@ Gemini CLI note:
|
|
|
50
50
|
- `gemini mcp` commands require Gemini auth to be configured first (`GEMINI_API_KEY` or `~/.gemini/settings.json` auth).
|
|
51
51
|
- `setup` registers Gemini in both `user` and `project` scopes to improve auto-discovery across folders.
|
|
52
52
|
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
metheus-governance-mcp-cli setup --project-id <project_uuid> --ctxpack-key "<ctxpack_key>" --base-url https://metheus.gesiaplatform.com --workspace-dir auto --workspace-fallback-dir C:\code_test
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
This sets fallback workspace context for clients that do not pass workspace metadata:
|
|
61
|
-
- Codex/Antigravity/Cursor: `METHEUS_WORKSPACE_DIR` env
|
|
62
|
-
- Gemini: pinned `--workspace-dir <fallback>` and `METHEUS_WORKSPACE_DIR` in MCP registration
|
|
63
|
-
- fallback env is used only when workspace cannot be resolved (or resolves to home); when current `cwd` is a real project folder, sync uses that folder.
|
|
53
|
+
Workspace signal guardrail:
|
|
54
|
+
- default recommendation is `--workspace-dir auto` with no fixed fallback path.
|
|
55
|
+
- if a client session does not provide trusted workspace signals (`workspaceFolders` / `rootUri` / `cwd`), ctxpack local write is blocked (`sync_status=guarded`, `local_file_count=0`).
|
|
56
|
+
- use `--workspace-fallback-dir` only when you intentionally want a shared fallback root.
|
|
64
57
|
|
|
65
58
|
Guardrail note:
|
|
66
59
|
- By default, CLI blocks reading/writing ctxpack sync metadata when workspace root resolves to the home directory.
|
|
@@ -105,8 +98,8 @@ Cursor note:
|
|
|
105
98
|
|
|
106
99
|
Tool naming compatibility:
|
|
107
100
|
- Claude/Codex/Gemini keep canonical MCP tool names (`project.summary`, `ctxpack.merge.brief`, ...).
|
|
108
|
-
- Cursor/Antigravity sessions
|
|
109
|
-
- Proxy maps alias calls back to canonical names automatically.
|
|
101
|
+
- Cursor/Antigravity sessions use safe aliases only (`project_summary`, `ctxpack_merge_brief`, ...).
|
|
102
|
+
- Proxy maps safe alias calls back to canonical names automatically.
|
|
110
103
|
|
|
111
104
|
Local bootstrap tools exposed by proxy:
|
|
112
105
|
|
|
@@ -127,7 +120,12 @@ These tools accept `project_id` and return:
|
|
|
127
120
|
- same version -> keep current
|
|
128
121
|
- newer server version -> update local cache
|
|
129
122
|
- workspace path -> auto-detected from client metadata/env by default
|
|
130
|
-
-
|
|
123
|
+
- if workspace signal is missing in auto mode, sync is guarded (no local write)
|
|
124
|
+
- use `--workspace-fallback-dir <path>` only when you intentionally want fallback writes
|
|
125
|
+
|
|
126
|
+
Project-ID first-call rule:
|
|
127
|
+
- when user gives only `Project ID`, call `project.summary` first.
|
|
128
|
+
- call `ctxpack.ensure` after `project.summary` only when extra ctxpack refresh/export context is needed.
|
|
131
129
|
|
|
132
130
|
Ctxpack merge safety flow:
|
|
133
131
|
- call `ctxpack.merge.brief` first
|