From b100b3a77c00e309534f068beefe09188098efa5 Mon Sep 17 00:00:00 2001
From: Pierre <worph@users.noreply.github.com>
Date: Mon, 25 May 2026 23:47:48 +0200
Subject: [PATCH] improve doc + bugfix

---
 README.md                        | 22 +++++++++++-----------
 docs/api-reference.md            | 14 +++++++-------
 docs/vfs-rebuild-architecture.md |  2 +-
 3 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/README.md b/README.md
index fcc1e74..2f927bf 100644
--- a/README.md
+++ b/README.md
@@ -84,7 +84,7 @@ Meta-Fuse is a read-only process in the MetaMesh ecosystem that:
 │  [3] meta-stremio (PROCESS-READ)                                           │
 │      └─► Reads metadata from KV, streams media content                      │
 │                                                                             │
-│  [4] meta-orbit (SHARING-READ-WRITE)                                       │
+│  [4] meta-share (SHARING-READ-WRITE)                                       │
 │      └─► P2P metadata sync across network                                   │
 │                                                                             │
 └────────────────────────────────────────────────────────────────────────────┘
@@ -104,7 +104,7 @@ http://meta-core:9000
 
 /urls API Response (JSON):
 {
-  "hostname": "meta-core-dev",
+  "hostname": "metacore-app",
   "baseUrl": "http://localhost:8083",
   "apiUrl": "http://meta-core:9000",
   "redisUrl": "redis://meta-core:6379",
@@ -606,10 +606,10 @@ journalctl -u meta-fuse-driver -f
 cat /meta-core/locks/kv-leader.info
 
 # Check /urls API
-curl -k https://dev.localhost:8083/api/urls
+curl -k https://metacore-dev.localhost:8083/api/urls
 
 # Verify redis is running (on leader)
-docker exec meta-core-dev redis-cli ping
+docker exec metacore-app redis-cli ping
 
 # Check meta-fuse logs
 docker logs meta-fuse | grep "KV"
@@ -632,10 +632,10 @@ docker logs meta-fuse | grep "wsgidav"
 
 ```bash
 # Check Redis has file data (flat key format)
-docker exec meta-core-dev redis-cli keys "file:*" | head -20
+docker exec metacore-app redis-cli keys "file:*" | head -20
 
 # Check file index
-docker exec meta-core-dev redis-cli scard "file:__index__"
+docker exec metacore-app redis-cli scard "file:__index__"
 
 # Verify source files exist
 ls -la /files/watch/
@@ -644,7 +644,7 @@ ls -la /files/watch/
 curl http://localhost:3000/api/fuse/stats
 
 # Check streaming state builder stats
-docker logs meta-fuse-dev | grep "State builder"
+docker logs metafuse-app | grep "State builder"
 ```
 
 ## Technology Stack
@@ -665,7 +665,7 @@ Meta-Fuse is designed to work seamlessly with other MetaMesh services:
 
 - **meta-sort**: Provides metadata in KV database
 - **meta-stremio**: Can stream files exposed by meta-fuse
-- **meta-orbit**: Syncs metadata across P2P network
+- **meta-share**: Syncs metadata across P2P network
 
 ### Connecting to meta-sort
 
@@ -673,13 +673,13 @@ Ensure meta-sort is running and has processed files:
 
 ```bash
 # Check meta-sort processing status
-curl -k https://dev.localhost:8180/api/processing/status
+curl -k https://metasort-dev.localhost:8180/api/processing/status
 
 # Verify Redis has metadata (via meta-core)
-docker exec meta-core-dev redis-cli scard "file:__index__"
+docker exec metacore-app redis-cli scard "file:__index__"
 
 # Check meta:events stream has events
-docker exec meta-core-dev redis-cli xlen "meta:events"
+docker exec metacore-app redis-cli xlen "meta:events"
 ```
 
 Meta-fuse will automatically discover the KV database through the shared lock file at `/meta-core/locks/kv-leader.info`.
diff --git a/docs/api-reference.md b/docs/api-reference.md
index 6abd38c..24fdbd0 100644
--- a/docs/api-reference.md
+++ b/docs/api-reference.md
@@ -535,29 +535,29 @@ List all discovered MetaMesh services.
     "services": [
         {
             "name": "meta-sort",
-            "url": "http://meta-sort-dev",
-            "api": "http://meta-sort-dev/api",
+            "url": "http://metasort-app",
+            "api": "http://metasort-app/api",
             "status": "healthy",
             "role": "writer"
         },
         {
             "name": "meta-fuse",
-            "url": "http://meta-fuse-dev",
-            "api": "http://meta-fuse-dev/api",
+            "url": "http://metafuse-app",
+            "api": "http://metafuse-app/api",
             "status": "healthy",
             "role": "reader"
         },
         {
             "name": "meta-stremio",
-            "url": "http://meta-stremio-dev",
-            "api": "http://meta-stremio-dev/api",
+            "url": "http://metastremio-app",
+            "api": "http://metastremio-app/api",
             "status": "healthy",
             "role": "reader"
         }
     ],
     "current": "meta-fuse",
     "leader": {
-        "hostname": "meta-core-dev",
+        "hostname": "metacore-app",
         "baseUrl": "http://localhost:8083",
         "apiUrl": "http://meta-core:9000",
         "redisUrl": "redis://meta-core:6379",
diff --git a/docs/vfs-rebuild-architecture.md b/docs/vfs-rebuild-architecture.md
index 0194f15..2e26e5f 100644
--- a/docs/vfs-rebuild-architecture.md
+++ b/docs/vfs-rebuild-architecture.md
@@ -350,7 +350,7 @@ The `onFileComplete` callback is called when:
 ```
 [meta-fuse] Starting meta-fuse...
 [KVManager] Waiting for leader...
-[LeaderClient] Leader found: meta-core-dev at redis://meta-core:6379
+[LeaderClient] Leader found: metacore-app at redis://meta-core:6379
 [meta-fuse] KV Manager ready, initializing VFS with streaming bootstrap...
 [StreamingStateBuilder] Initialized with 12 VFS-relevant properties
 [meta-fuse] Replaying meta:events stream from position 0...