@nhatnguyen9317/memory-mcp-server 1.4.0 → 1.4.1

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/CHANGELOG.md CHANGED
@@ -1,5 +1,26 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.4.1 (2026-11-16)
4
+
5
+ ### Fixed
6
+
7
+ - Auto-recall no longer gives unknown-project (`NULL` workspace) memories
8
+ the same eligibility threshold as home memories when the session's
9
+ workspace is known. Non-preference memories from unknown or other
10
+ projects must match at least `max(2, ceil(0.75 * N))` of the distinct
11
+ title terms. A one-term title cannot recall those memories; a two-term
12
+ title requires both terms. Strong unknown-project matches remain eligible.
13
+ - Home memories and cross-project preferences keep the base floor. When
14
+ the session workspace is unknown, all memories keep the existing base
15
+ floor. Candidate priorities, score weights, manual search/get, tool
16
+ contracts and stored data are unchanged; no migration is required.
17
+ - Added threshold-boundary and compatibility regressions, including
18
+ recorded recalled ids, stale/unsafe feedback and FTS failure handling.
19
+ - Synchronized the lockfile's root package version with the release version
20
+ without changing dependency versions. `GUIDELINES.md` remains v9.
21
+
22
+ Design: [1.4.1 unknown-workspace recall](docs/design/2026-11-16-spec-v1.4.1-unknown-workspace-recall.md).
23
+
3
24
  ## 1.4.0 (2026-10-06)
4
25
 
5
26
  Theme: a smaller tool surface — 12 tools that were unused or never exploited removed, one retrieval tool added, recalled memories recorded per session. Design: [`docs/design/2026-10-06-spec-v1.4.0-tool-surface-reduction.md`](docs/design/2026-10-06-spec-v1.4.0-tool-surface-reduction.md).
package/README.md CHANGED
@@ -147,7 +147,14 @@ the versioned [GUIDELINES.md](./GUIDELINES.md).
147
147
  longer crowd out local ones. Since v1.3.3 an explicit `workspace` argument
148
148
  is honored, `/` and the home directory are treated as unknown, and
149
149
  memories from other projects are recalled only on a near-complete title
150
- match (user preferences excepted).
150
+ match (user preferences excepted). Since v1.4.1, when the session knows
151
+ its workspace, memories with an unknown (`NULL`) workspace also need
152
+ that strong match: at least `max(2, ceil(0.75 * N))` of the distinct title
153
+ terms. A one-term title cannot recall unknown-project non-preference
154
+ memories; two terms require both. Home memories and preferences retain
155
+ the base floor (one match for fewer than three terms, otherwise two).
156
+ If the session's workspace is unknown, that base floor still applies to
157
+ everyone. Manual `memory_search` / `memory_get` remain available.
151
158
  - **Project-scoped**: point `MEMORY_DB_PATH` at a file inside the project
152
159
  (e.g. `.memory/project-memory.db`) for hard isolation per repository or
153
160
  customer.
package/dist/constants.js CHANGED
@@ -2,7 +2,7 @@ import path from "node:path";
2
2
  import os from "node:os";
3
3
  /** Max characters returned in a single tool response before truncation. */
4
4
  export const CHARACTER_LIMIT = 25000;
5
- export const MCP_VERSION = "1.4.0";
5
+ export const MCP_VERSION = "1.4.1";
6
6
  /**
7
7
  * Diagnostics-event recording is opt-in: set MEMORY_TELEMETRY=on to enable.
8
8
  * Read at call time so tests and long-lived processes can toggle it.
@@ -140,7 +140,7 @@ function recallRelatedMemories(database, title, workspace) {
140
140
  matchCounts.set(row.rowid, (matchCounts.get(row.rowid) ?? 0) + 1);
141
141
  }
142
142
  }
143
- // Eligibility gate. Other projects' non-preference memories must match
143
+ // Eligibility gate. Other/unknown projects' non-preference memories must match
144
144
  // nearly the whole title; everyone else needs the base floor. Nothing
145
145
  // eligible means nothing returned — no best-effort lifeline.
146
146
  const total = terms.length;
@@ -152,8 +152,10 @@ function recallRelatedMemories(database, title, workspace) {
152
152
  matched: matchCounts.get(candidate.row_id) ?? 1,
153
153
  }))
154
154
  .filter((candidate) => {
155
- const crossProject = workspace !== null && candidate.workspace_priority === 0;
156
- return candidate.matched >= (crossProject ? crossProjectFloor : baseFloor);
155
+ const needsStrongMatch = workspace !== null &&
156
+ candidate.workspace_priority !== 2 &&
157
+ candidate.type !== "preference";
158
+ return candidate.matched >= (needsStrongMatch ? crossProjectFloor : baseFloor);
157
159
  });
158
160
  if (eligible.length === 0)
159
161
  return [];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nhatnguyen9317/memory-mcp-server",
3
- "version": "1.4.0",
3
+ "version": "1.4.1",
4
4
  "keywords": [
5
5
  "mcp",
6
6
  "model-context-protocol",