@vheins/local-memory-mcp 0.8.47 → 0.8.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.
|
@@ -3,8 +3,8 @@ import { fileURLToPath } from "url";
|
|
|
3
3
|
import path from "path";
|
|
4
4
|
var __dirname = path.dirname(fileURLToPath(import.meta.url));
|
|
5
5
|
var pkgVersion = "0.1.0";
|
|
6
|
-
if ("0.8.
|
|
7
|
-
pkgVersion = "0.8.
|
|
6
|
+
if ("0.8.48") {
|
|
7
|
+
pkgVersion = "0.8.48";
|
|
8
8
|
} else {
|
|
9
9
|
let searchDir = __dirname;
|
|
10
10
|
for (let i = 0; i < 5; i++) {
|
package/dist/dashboard/server.js
CHANGED
package/dist/mcp/server.js
CHANGED
|
@@ -17,20 +17,26 @@ Goal:
|
|
|
17
17
|
- Extract only source-backed coding standards from the documentation.
|
|
18
18
|
- Produce one atomic CSL entry per distinct rule, constraint, prohibition, or required workflow.
|
|
19
19
|
- Each entry must be ready for the standard-store tool shape: name, content, context, version, language, stack, tags, metadata, repo, is_global.
|
|
20
|
+
- Identify documentation navigation menus (e.g., sidebars, index pages) containing links to related sub-pages. If present, create iterative scraping tasks for these sub-pages.
|
|
20
21
|
|
|
21
22
|
Atomic entry rules:
|
|
22
23
|
- One entry = one rule. Split bundled guidance into separate entries.
|
|
23
24
|
- Keep content concise, imperative, and implementation-relevant.
|
|
25
|
+
- ALWAYS include relevant code examples or snippets from the source that illustrate or enforce the rule. Do NOT discard code blocks.
|
|
24
26
|
- Preserve the source meaning without inventing requirements.
|
|
25
|
-
- Ignore
|
|
27
|
+
- Ignore marketing copy, release notes, and changelog noise. Do NOT ignore code examples.
|
|
26
28
|
- Do not emit duplicates or near-duplicates.
|
|
27
29
|
- Do not infer version, language, stack, or scope unless the source makes them explicit.
|
|
28
30
|
- Use metadata to preserve provenance, including the source_url and a short evidence_excerpt for each entry.
|
|
29
31
|
|
|
30
32
|
Output contract:
|
|
31
|
-
- If tool calls are available
|
|
32
|
-
-
|
|
33
|
-
-
|
|
33
|
+
- If tool calls are available:
|
|
34
|
+
- Emit one `standard-store` call per accepted entry.
|
|
35
|
+
- Emit one `task-create` call for each discovered documentation sub-page URL. The task title should be "Scrape: [URL]" and the description should instruct to use the `csl-scrapper` prompt for that URL.
|
|
36
|
+
- If tool calls are unavailable, return a JSON object with:
|
|
37
|
+
- `standards`: Array of `standard-store`-compatible payloads.
|
|
38
|
+
- `next_urls`: Array of sub-page URLs to scrape.
|
|
39
|
+
- Use title-like names for the "name" field and store the atomic rule text along with its code examples in "content".
|
|
34
40
|
- Use "context" for the topic area (for example: naming, error-handling, routing, testing, hooks, security).
|
|
35
41
|
- Default version to "1.0.0" only when the source gives no versioning signal.
|
|
36
42
|
- Prefer is_global=true unless the source is clearly repo-specific.
|