@vheins/local-memory-mcp 0.19.9 → 0.19.10
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/dist/mcp/server.js
CHANGED
|
@@ -74,8 +74,8 @@ import path from "path";
|
|
|
74
74
|
import { fileURLToPath } from "url";
|
|
75
75
|
var __dirname = path.dirname(fileURLToPath(import.meta.url));
|
|
76
76
|
var pkgVersion = "0.1.0";
|
|
77
|
-
if ("0.19.
|
|
78
|
-
pkgVersion = "0.19.
|
|
77
|
+
if ("0.19.10") {
|
|
78
|
+
pkgVersion = "0.19.10";
|
|
79
79
|
} else {
|
|
80
80
|
let searchDir = __dirname;
|
|
81
81
|
for (let i = 0; i < 5; i++) {
|
|
@@ -23,7 +23,19 @@ The `owner` field MUST be the GitHub username or organization that OWNS the repo
|
|
|
23
23
|
|
|
24
24
|
NEVER use the agent's name (e.g., `sentinel`, `test-executor`, `claude`) as the owner.
|
|
25
25
|
NEVER guess the owner from the working directory path.
|
|
26
|
-
|
|
26
|
+
|
|
27
|
+
If unsure, run `git remote -v` in the project directory — the remote URL (e.g., `git@github.com:vheins/sentinel-agent.git`) gives you both `owner` and `repo`.
|
|
28
|
+
|
|
29
|
+
**Two ways to provide owner/repo:**
|
|
30
|
+
|
|
31
|
+
1. **Explicit** (preferred — most reliable):
|
|
32
|
+
```json
|
|
33
|
+
{ "owner": "vheins", "repo": "sentinel-agent" }
|
|
34
|
+
```
|
|
35
|
+
2. **Shorthand** — use `owner/repo` format for `repo`; the server auto-extracts `owner`:
|
|
36
|
+
```json
|
|
37
|
+
{ "repo": "vheins/sentinel-agent" }
|
|
38
|
+
```
|
|
27
39
|
|
|
28
40
|
Violation: tasks created with a wrong owner will be invisible to other agents querying with the correct owner.
|
|
29
41
|
|
|
@@ -62,7 +74,7 @@ S2 | continue to task or respond | S1✅ | ready | —
|
|
|
62
74
|
- Create ONLY for unfinished work (concrete next owner/steps)
|
|
63
75
|
- NO handoff for completion summaries → use task-update comments
|
|
64
76
|
|
|
65
|
-
**Knowledge Graph**:
|
|
77
|
+
**Knowledge Graph**: create_entity | create_relation → delete_entity | delete_relation | delete_observation
|
|
66
78
|
|
|
67
79
|
- Structured entity-relationship storage for domain concepts
|
|
68
80
|
- Auto-extracted via NLP Archivist on every memory-store (people, places, orgs, concepts)
|
|
@@ -22,9 +22,9 @@ S5 | verify: confirm acknowledge called after code gen, no duplicate memories cr
|
|
|
22
22
|
|
|
23
23
|
## Knowledge Graph Tools
|
|
24
24
|
|
|
25
|
-
- `
|
|
26
|
-
- `
|
|
27
|
-
- `
|
|
25
|
+
- `create_entity(name, type?, description?, owner?, repo?)`, `delete_entity(name, owner?, repo?)`
|
|
26
|
+
- `create_relation(from_entity, to_entity, relation_type, owner?, repo?)`, `delete_relation(from_entity, to_entity, relation_type, owner?, repo?)`
|
|
27
|
+
- `delete_observation(id, owner?, repo?)`
|
|
28
28
|
- Specialized for structured data workflows only (entity-relationship modeling). Not part of standard memory/task flow.
|
|
29
29
|
|
|
30
30
|
## Standards Flow
|