docs: mark memory_pulse as shipped, add memory_path feature

nexus/mnemosyne/FEATURES.yaml

@@ -163,12 +163,15 @@ planned:
       - "#TBD"  # Will be filled when PR is created
 
   memory_pulse:
-    status: planned
+    status: shipped
+    files: [nexus/components/memory-pulse.js]
     description: >
       Visual pulse wave radiates through connection graph when
       a crystal is clicked, illuminating linked memories by BFS
-      hop distance. Was attempted in PR #1226 — needs rebasing.
+      hop distance.
     priority: medium
+    merged_prs:
+      - "#1263"
 
   embedding_backend:
     status: shipped
@@ -181,6 +184,19 @@ planned:
     merged_prs:
       - "#TBD"  # Will be filled when PR is created
 
+
+  memory_path:
+    status: shipped
+    files: [archive.py, cli.py, tests/test_path.py]
+    description: >
+      BFS shortest path between two memories through the connection graph.
+      Answers "how is memory X related to memory Y?" by finding the chain
+      of connections. Includes path_explanation for human-readable output.
+      CLI command: mnemosyne path <start_id> <end_id>
+    priority: medium
+    merged_prs:
+      - "#TBD"
+
   memory_consolidation:
     status: shipped
     files: [archive.py, cli.py, tests/test_consolidation.py]