memory-journal-mcp 9.0.0 → 9.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memory-journal-mcp",
-  "version": "9.0.0",
+  "version": "9.1.0",
   "description": "Persistent knowledge graphs and intelligent context recall across fragmented AI threads.",
   "type": "module",
   "main": "dist/index.js",
@@ -72,7 +72,7 @@
     "dotenv": "^18.0.9",
     "esbuild": "0.28.2",
     "eslint": "^10.14.0",
-    "globals": "^17.13.0",
+    "globals": "^17.14.0",
     "picocolors": "^1.1.1",
     "tsup": "^9.0.0",
     "tsx": "4.23.15",
@@ -121,12 +121,11 @@
     "infra:logs": "docker compose -f test-server/infrastructure/docker-compose.yml logs -f",
     "infra:status": "node test-server/infrastructure/scripts/check-status.mjs",
     "pretest:e2e": "node -e \"fs.rmSync('.test-output/e2e', { recursive: true, force: true, maxRetries: 5, retryDelay: 200 })\"",
-    "test:e2e": "playwright test",
+    "test:e2e": "playwright test && tsx scripts/update-badges.ts",
     "test:wsl": "wsl bash -c \"pnpm run test\"",
     "test:e2e:wsl": "wsl bash -c \"pnpm run test:e2e\"",
     "test:scheduler": "node test-server/scripts/test-scheduler.mjs",
     "test:prompts": "node test-server/scripts/test-prompts.mjs",
-    "backfill:metadata": "tsx scripts/backfill-metadata.ts",
     "encrypt-db": "tsx scripts/encrypt-db.ts"
   }
 }

package/skills/memory-journal-mcp/SKILL.md

@@ -11,30 +11,30 @@ This skill acts as a static anchor to reinforce core usage patterns, commit work
 
 ## 1. Accessing Detailed Server Instructions
 The Memory Journal MCP provides comprehensive, dynamic instructions via its `memory://help` resources:
-- Use `read_resource` on `memory://help` for critical gotchas and core usage patterns.
-- Use `read_resource` on `memory://help/{group}` for specific tool groups (e.g., `core`, `search`, `admin`, `codemode`, `github`, `git`, `templates`, `team`).
+- Use `read_resource` on `memory://help` for the tool group index and `memory://help/gotchas` for critical gotchas and core usage patterns.
+- Use `read_resource` on `memory://help/{group}` for specific tool groups (`core`, `search`, `analytics`, `relationships`, `io`, `admin`, `github`, `git`, `backup`, `team`, `codemode`, `templates`, `gotchas`).
 
 ## 2. Core Agent Directives
-- **Session Briefing:** Read the workspace briefing via `memory://briefing/{repo_name}` (or fallback to `memory://briefing`) at session start. DO NOT autonomously execute tasks listed in the briefing.
+- **Session Briefing:** Read the workspace briefing via `memory://briefing/{+repo}` (or fallback to `memory://briefing`) at session start. DO NOT autonomously execute tasks listed in the briefing.
 - **Context Integrity & Metadata:** Always include mandatory context fields when creating entries:
-  - `workspace_id`: Repository name (e.g. `adamic`, `memory-journal-mcp`). Required string.
+  - `workspace_id`: Repository name (e.g. `adamic`, `memory-journal-mcp`). Required string (auto-resolves from `project_number` / `PROJECT_REGISTRY` if omitted).
   - `session_id`: Current AI conversation ID.
-  - `project_number`: Numeric project ID.
+  - `project_number`: Numeric project ID (strictly required by MCP `create_entry`/`team_create_entry` and CLI `entry create -p <number>` [`--project <number>`] if not auto-resolvable from `workspace_id`, content/tag keyword matching, CWD in `PROJECT_REGISTRY` / `projectRegistry`, or `DEFAULT_PROJECT_NUMBER` / `--default-project`).
   - `impact_score` / `trust_score`: Blast radius and confidence heuristics (0.0 to 1.0).
   - `validation_status`: `'passed'`, `'none'`, or `'failed'`.
-- **Context Recovery:** If you lose workspace context mid-task (e.g., needing a `project_number`), NEVER re-query `memory://briefing`. Query `memory://agent-id`.
+- **Context Recovery:** If you lose workspace context mid-task (e.g., needing a `project_number`), NEVER re-query `memory://briefing`. Query `memory://agent-context/{+repo}` (or `memory://agent-id/{+repo}`; bare `memory://agent-context` and `memory://agent-id` fall back to server CWD).
 
 ## 3. Commit Integration & Entry Creation
 - **Commit Journaling:** When recording commit history in the journal, create an entry (via `mj_execute_code`, `create_entry`, or `memory-journal-mcp entry create`) tagged `commit-narrative` containing `auto_context` with `commits: ["<sha>"]` and heuristic metadata (`impact_score`, `trust_score`, `validation_status`).
 - **Commit Narrative Guardrails:** Any entry tagged `"commit-narrative"` MUST include `auto_context` containing a non-empty `commits` array (e.g., `{ "commits": ["<sha>"] }`).
 
 ## 4. Session Summary Guardrails
-- **Required Structure:** Entries tagged `"session-summary"` (or `entry_type: "retrospective"`) MUST contain **EXACTLY** these 4 top-level section headers:
+- **Required Structure:** Entries tagged `"session-summary"` (which use `entry_type: "retrospective"`) MUST contain **EXACTLY** these 4 top-level section headers:
   - `## Accomplished`
   - `## Unfinished / Blocked`
   - `## Context for Next Session`
   - `## Commits`
-- **Strict Validation:** DO NOT invent extra top-level section headers or duplicate headers. Must include `auto_context` with a non-empty `commits` array.
+- **Strict Validation:** DO NOT invent extra top-level section headers or duplicate headers. If `auto_context` is provided, it must contain a non-empty `commits` array.
 
 ## 5. Tool Execution & Lifecycle Rules
 - **Token Efficiency:** Prioritize MCP Code Mode (`mj_execute_code`) or native MCP tools for token-efficient entry logging, searches, and aggregations.

package/dist/auth/context.d.ts

@@ -1,7 +0,0 @@
-import { AsyncLocalStorage } from 'node:async_hooks';
-export interface AuthContextPayload {
-    sub?: string;
-    scopes: string[];
-}
-export declare const authStorage: AsyncLocalStorage<AuthContextPayload>;
-//# sourceMappingURL=context.d.ts.map

package/dist/auth/context.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../../src/auth/context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,kBAAkB,CAAA;AAEpD,MAAM,WAAW,kBAAkB;IAC/B,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,MAAM,EAAE,MAAM,EAAE,CAAA;CACnB;AAED,eAAO,MAAM,WAAW,uCAA8C,CAAA"}

package/dist/chunk-ELMJYRTT.js

@@ -1,29 +0,0 @@
-// src/utils/progress-utils.ts
-async function sendProgress(ctx, progress, total, message) {
-  if (ctx === void 0) return;
-  if (ctx.progressToken === void 0) return;
-  try {
-    const notification = {
-      method: "notifications/progress",
-      params: {
-        progressToken: ctx.progressToken,
-        progress,
-        ...total !== void 0 && { total },
-        ...message !== void 0 && message !== "" && { message }
-      }
-    };
-    await ctx.server.notification(notification);
-  } catch {
-  }
-}
-function createBatchProgressReporter(ctx, total, throttle = 10) {
-  let lastReported = 0;
-  return async (current, message) => {
-    if (current - lastReported >= throttle || current === total) {
-      await sendProgress(ctx, current, total, message);
-      lastReported = current;
-    }
-  };
-}
-
-export { createBatchProgressReporter, sendProgress };