prism-mcp-server 20.21.19 → 20.21.20

package/README.md

@@ -158,6 +158,18 @@ or by re-enabling after each run.
 <details>
 <summary>Release history (optional)</summary>
 
+## What's New in v20.21.20
+
+- Fixed: a `session_save_ledger` call refused with `context_not_loaded`, or the
+  greeting-only reply that writes nothing, restarted the hourly drift reminder.
+  A ledger save restarts it now only when it writes an entry.
+- A written ledger entry's reply also asks for the handoff when the checkpoint
+  ends a unit of work.
+- A ledger save skipped as a duplicate of one saved in the last 5 minutes now
+  says nothing new was written, instead of "saved".
+- Fixed: with Supabase storage, a handoff whose save failed was reported as
+  updated. It is now an error the agent can see and retry.
+
 ## What's New in v20.21.19
 
 - Prism Browser emulates phones and tablets. `--device iphone-17`, or one of

package/dist/server.js

@@ -764,14 +764,8 @@ export function createServer() {
                         if (!SESSION_MEMORY_ENABLED)
                             throw new Error("Session memory not configured. Set SUPABASE_URL and SUPABASE_KEY.");
                         result = await sessionSaveLedgerHandler(args);
-                        // GATE 5: Reset drift timer — save_ledger counts as a drift checkpoint
-                        {
-                            const cid = args?.conversation_id;
-                            if (cid) {
-                                const { noteDriftCheck } = await import("./session/sessionContext.js");
-                                noteDriftCheck(cid);
-                            }
-                        }
+                        // GATE 5: the handler resets the drift timer itself, and only when
+                        // it wrote an entry (not on a refusal or the greeting-only skip).
                         // Savings sync (paid, opt-in, fail-soft): session end is the natural
                         // push point. pushSavings gates itself — disabled/free/no-jwt all
                         // return without a request, and nothing here awaits it.

package/dist/storage/supabase.js

@@ -154,11 +154,11 @@ export class SupabaseStorage {
             };
         }
         catch (e) {
-            debugLog("[SupabaseStorage] saveHandoff RPC failed: " + (e instanceof Error ? e.message : String(e)));
-            return {
-                status: "updated",
-                version: handoff.version ?? 1,
-            };
+            // The write failed. Reporting "updated" here told the agent its handoff
+            // was saved when nothing was; the caller turns this into an error reply.
+            const message = e instanceof Error ? e.message : String(e);
+            debugLog("[SupabaseStorage] saveHandoff RPC failed: " + message);
+            throw new Error(`Handoff for project "${handoff.project}" was not saved: ${message}`);
         }
     }
     async patchHandoff(project, userId, data) {

package/dist/tools/ledgerHandlers.js

@@ -810,6 +810,22 @@ export async function sessionSaveLedgerHandler(args) {
         keywords,
         role: effectiveRole, // v3.0: Hivemind role scoping (dashboard fallback)
     });
+    // SQLite skips an identical (project, conversation_id, summary) saved in the
+    // last 5 minutes and returns { id, deduplicated: true } without writing.
+    // Nothing new was saved, so this is not a drift checkpoint and must not read
+    // as one: no timer reset, no "saved" line, no handoff nudge, and no second
+    // embedding or auto-link pass over the existing row.
+    if (result?.deduplicated === true) {
+        return {
+            content: [{
+                    type: "text",
+                    text: (_saveLedgerGateWarning ? `⚠️ ${_saveLedgerGateWarning}\n\n` : "") +
+                        `ℹ️ An identical ledger entry for project "${project}" was already saved in the last 5 minutes; nothing new was written.` +
+                        resolverNote,
+                }],
+            isError: false,
+        };
+    }
     // ─── Fire-and-forget embedding generation ───
     let embeddingQueued = false;
     if (result) {
@@ -908,6 +924,14 @@ export async function sessionSaveLedgerHandler(args) {
         debugLog(`[session_save_ledger] Background decay failed (non-fatal): ${err instanceof Error ? err.message : String(err)}`);
     });
     const metricsBlock = formatInferenceMetrics();
+    // GATE 5: a ledger entry that was WRITTEN is a drift checkpoint. Reset the
+    // timer here, on the write path only. It used to be reset by the server
+    // after every returned result, so a context_not_loaded refusal or the
+    // greeting-only skip silenced the hourly reminder without saving anything.
+    {
+        const { noteDriftCheck } = await import("../session/sessionContext.js");
+        noteDriftCheck(conversation_id);
+    }
     return {
         content: [{
                 type: "text",
@@ -920,6 +944,9 @@ export async function sessionSaveLedgerHandler(args) {
                     (embeddingQueued
                         ? `📊 Embedding generation queued for semantic search.`
                         : `📊 Primary history saved; optional semantic indexing was not queued.`) +
+                    // The ledger logs what happened; the next session starts from the
+                    // handoff. Only a written entry asks, never the skip or a refusal.
+                    `\n💾 If this checkpoint ends a unit of work, also save the handoff with session_save_handoff.` +
                     metricsBlock +
                     resolverNote,
             }],

package/docs/prism-browser.md

@@ -99,11 +99,13 @@ size alone. Emulate the device instead:
   `viewport-fit=cover`; without it an iPhone 17 reports 0. Chromium applies
   them either way, so check that your page sets it.
 
-Flags given explicitly override the preset, so a phone turned sideways is
-`--device iphone-17 --viewport 874x402 --safe-area 0,62,21,62`. Landscape
-insets are not part of the presets. The engine stays Chromium, and the user
-agent stays the desktop one, so pages that branch on the user-agent string
-still take their desktop path.
+Flags given explicitly override the preset, so
+`--device iphone-17 --viewport 874x402 --safe-area T,R,B,L` is the same phone
+turned sideways. Landscape insets were not measured and are not part of the
+presets: put the values your device reports in place of `T,R,B,L`, because
+without `--safe-area` the portrait insets still apply. The engine stays
+Chromium, and the user agent stays the desktop one, so pages that branch on the
+user-agent string still take their desktop path.
 
 ```bash
 printf '%s\n' \

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prism-mcp-server",
-  "version": "20.21.19",
+  "version": "20.21.20",
   "mcpName": "io.github.dcostenco/prism-coder",
   "description": "Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work, semantic drift detection, and local inference. Local-first by default. Works with Claude Code, Cursor, and Codex.",
   "module": "index.ts",
@@ -83,7 +83,7 @@
     "hono": "^4.13.5",
     "ip-address": "^10.2.0",
     "protobufjs": "^7.6.5",
-    "sharp": "^0.35.4",
+    "sharp": "^0.35.5",
     "tar": "^7.5.19",
     "nanoid": "^3.3.17"
   },