From 8c0370424694e5583aacacae59bc3518943fc67f Mon Sep 17 00:00:00 2001
From: suyua9 <1521777066@qq.com>
Date: Sat, 4 Apr 2026 01:38:49 +0800
Subject: [PATCH] docs: tighten session architecture wording

---
 docs/SESSION_ID_ARCHITECTURE.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/SESSION_ID_ARCHITECTURE.md b/docs/SESSION_ID_ARCHITECTURE.md
index 5ad386df..3570dcf7 100644
--- a/docs/SESSION_ID_ARCHITECTURE.md
+++ b/docs/SESSION_ID_ARCHITECTURE.md
@@ -30,7 +30,7 @@ Claude-mem uses **two distinct session IDs** to track conversations and memory:
                            ↓
 ┌─────────────────────────────────────────────────────────────┐
 │ 3. First SDK message arrives with session_id                │
-│    updateMemorySessionId(sessionDbId, "sdk-gen-abc123")     │
+│    ensureMemorySessionIdRegistered(sessionDbId, "sdk-gen-abc123") │
 │                                                              │
 │    Database state:                                          │
 │    ├─ content_session_id: "user-session-123"               │
@@ -73,8 +73,8 @@ This is why `SDKAgent` persists the SDK-returned `session_id` immediately throug
 const hasRealMemorySessionId = !!session.memorySessionId;
 ```
 
-- When `memorySessionId === null` → Not yet captured
-- When `memorySessionId !== null` → Real SDK session captured
+- When `memorySessionId` is falsy → Not yet captured
+- When `memorySessionId` is truthy → Real SDK session captured
 
 ### 2. Resume Safety