docs: remove deprecated Graph Memory references

Graph Memory was deprecated on April 16, 2026. This removes remaining
mentions across docs that could mislead readers into thinking it is still
a supported feature.

- Platform pages (overview, quickstart, faqs, platform-vs-oss, vibecoding):
  remove graph memory from feature lists, comparison table, and intro copy
- Platform features (platform-overview, mcp-integration,
  advanced-memory-operations): rephrase "graph-powered retrieval" to
  "advanced retrieval"; drop "Enable graph memories" tip; remove graph-edge
  verification step from the metadata example
- Core concepts (add, search, memory-types, memory-evaluation): remove
  "optional graph storage" / "graph features" / "graph writes" / "graph
  toggles"; drop "graph" from Entity Search description; remove outdated
  add/search architecture diagrams (replacement pending)
- Open source features (overview, rest-api): remove "graph relationships"
  and "graph backend(s)" from REST server config narrative
- API reference (organizations-projects): drop "graph settings" from
  Update Project Settings description
- Cookbooks: remove "Graph Memory on Neptune" card (page removed) and
  Neptune mention from AWS Bedrock card; remove "Graph Capabilities"
  bullet from Gemini cookbook; remove graph-memory conditional bullet from
  controlling-memory-ingestion
- CLI: remove --graph / --no-graph flags from mem0 add / mem0 search
  flag tables and MEM0_ENABLE_GRAPH env var
- Images: delete orphan add_architecture.png and search_architecture.png

docs/cookbooks/essentials/controlling-memory-ingestion.mdx

@@ -323,10 +323,6 @@ Metadata: {'verified': True, 'updated_date': '2025-04-02'}
 That “no duplicates” promise comes from the inference pipeline. Keep `infer=True` when you rely on automatic updates. Raw imports (`infer=False`) skip conflict checks, so mixing the two modes for the same fact will create duplicates.
 </Warning>
 
-**Maintains relationships:**
-
-- If using graph memory, connections to other entities persist
-
 ### Pick the right inference mode
 
 | Mode | What it does | Best for | Watch out for |

docs/cookbooks/frameworks/gemini-3-with-mem0-mcp.mdx

@@ -216,7 +216,6 @@ This information was retrieved from your memory history where you previously men
 
 - **Smart Memory Management** - Organizes memories into searchable information *without setting up vector databases*
 - **Fast Retrieval** - Instant lookups with *sub-millisecond ping*, handles large datasets
-- **Graph Capabilities** - Builds knowledge *automatically* as you push information
 - **Simple Integration** - Uses Mem0 API in the backend, works with *any MCP client* with just a few lines of code
 
 ### Gemini 3 + Mem0 Benefits

docs/cookbooks/overview.mdx

@@ -156,14 +156,7 @@ Here are some examples of how Mem0 can be integrated into various applications:
     icon="aws"
     href="/cookbooks/integrations/aws-bedrock"
   >
-    Mem0 with AWS Bedrock and Neptune.
-  </Card>
-  <Card
-    title="Graph Memory on Neptune"
-    icon="network-wired"
-    href="/cookbooks/integrations/neptune-analytics"
-  >
-    Graph memory with Neptune Analytics.
+    Mem0 with AWS Bedrock.
   </Card>
 </CardGroup>