Update Readme

Update Readme

New tool: session_start (mcp_server.py)
- Inserted before get_current_user so it appears first in the tool list
- Parameters: user_email (str), first_message (str)
- Does three things atomically in one round-trip:
  1. Resolves user identity: exact email match → fuzzy ILIKE name fallback
     Returns {matched, user_email, name, user_id} or {matched:false, message}
  2. Searches all team memories (cross-user, no user_id filter, limit=5)
     using first_message as the query. Returns related_work list so Claude
     can surface teammate progress to the user before responding.
  3. Stores "{display_name} started working on: {first_message}" as an
     exact memory (infer=False) under the resolved user, including DB sync
     to openmemory.memories + memory_status_history.

Tool description instructs Claude to:
- Call session_start as the VERY FIRST tool in every new conversation
- MUST surface non-empty related_work to the user before responding
- Use judgment about relevance; not every hit needs mentioning
- Fall back gracefully if the tool errors

Updated get_current_user description to defer to session_start for
conversation starts; use get_current_user only for mid-conversation
identity lookups.

Bug fixed: old_state in MemoryStatusHistory must be NOT NULL per DB
constraint; used MemoryState.deleted as the sentinel value for new
additions (consistent with existing add_memories behavior).

Verified:
- session_start is tool mem0ai#1 in the tool list
- Returns correct user profile + related_work (em dash Oden memory
  surfaces as top result for Oden email copy query, score 0.35)
- Session note "Michael Dunn started working on: ..." stored in DB
- Unknown user returns matched:false + empty related_work

New tool: session_start (mcp_server.py)
- Inserted before get_current_user so it appears first in the tool list
- Parameters: user_email (str), first_message (str)
- Does three things atomically in one round-trip:
  1. Resolves user identity: exact email match → fuzzy ILIKE name fallback
     Returns {matched, user_email, name, user_id} or {matched:false, message}
  2. Searches all team memories (cross-user, no user_id filter, limit=5)
     using first_message as the query. Returns related_work list so Claude
     can surface teammate progress to the user before responding.
  3. Stores "{display_name} started working on: {first_message}" as an
     exact memory (infer=False) under the resolved user, including DB sync
     to openmemory.memories + memory_status_history.

Tool description instructs Claude to:
- Call session_start as the VERY FIRST tool in every new conversation
- MUST surface non-empty related_work to the user before responding
- Use judgment about relevance; not every hit needs mentioning
- Fall back gracefully if the tool errors

Updated get_current_user description to defer to session_start for
conversation starts; use get_current_user only for mid-conversation
identity lookups.

Bug fixed: old_state in MemoryStatusHistory must be NOT NULL per DB
constraint; used MemoryState.deleted as the sentinel value for new
additions (consistent with existing add_memories behavior).

Verified:
- session_start is tool mem0ai#1 in the tool list
- Returns correct user profile + related_work (em dash Oden memory
  surfaces as top result for Oden email copy query, score 0.35)
- Session note "Michael Dunn started working on: ..." stored in DB
- Unknown user returns matched:false + empty related_work

New tool: session_start (mcp_server.py)
- Inserted before get_current_user so it appears first in the tool list
- Parameters: user_email (str), first_message (str)
- Does three things atomically in one round-trip:
  1. Resolves user identity: exact email match → fuzzy ILIKE name fallback
     Returns {matched, user_email, name, user_id} or {matched:false, message}
  2. Searches all team memories (cross-user, no user_id filter, limit=5)
     using first_message as the query. Returns related_work list so Claude
     can surface teammate progress to the user before responding.
  3. Stores "{display_name} started working on: {first_message}" as an
     exact memory (infer=False) under the resolved user, including DB sync
     to openmemory.memories + memory_status_history.

Tool description instructs Claude to:
- Call session_start as the VERY FIRST tool in every new conversation
- MUST surface non-empty related_work to the user before responding
- Use judgment about relevance; not every hit needs mentioning
- Fall back gracefully if the tool errors

Updated get_current_user description to defer to session_start for
conversation starts; use get_current_user only for mid-conversation
identity lookups.

Bug fixed: old_state in MemoryStatusHistory must be NOT NULL per DB
constraint; used MemoryState.deleted as the sentinel value for new
additions (consistent with existing add_memories behavior).

Verified:
- session_start is tool mem0ai#1 in the tool list
- Returns correct user profile + related_work (em dash Oden memory
  surfaces as top result for Oden email copy query, score 0.35)
- Session note "Michael Dunn started working on: ..." stored in DB
- Unknown user returns matched:false + empty related_work