Context

Memory-core processes boot concurrently without awareness of sibling instances holding the shared SQLite database.

The Problem

When diagnosing boot-time identity-binding issues, we cannot easily tell if the current process is competing with siblings at startup.

The Architectural Reality

ai/mcp/server/memory-core/Server.mjs initializes the server and DB connection in initAsync().

The Fix

Add a boot-time self-check in ai/mcp/server/memory-core/Server.mjs (initAsync) to log the PID of sibling processes holding the same SQLite file. Use the logger (which natively honors debug mode).

Acceptance Criteria

• Server.mjs checks for sibling PIDs holding the SQLite file during initAsync.
• Sibling PIDs are logged via the logger.

Out of Scope

• Changing the SQLite WAL pragma or fixing upstream Antigravity duplication.

Related

• Parent Epic: #10186

Handoff Retrieval Hints

• query_raw_memories(query="GraphService vicinityLoadedNodes identity binding")