livedesk 0.1.592 → 0.1.593

package/README.md

@@ -1,10 +1,10 @@
-# LiveDesk
+# VuvoDesk
 
 `livedesk` is a thin cross-platform launcher. npm installs only the matching
 RemoteFast package for the current operating system and CPU, so Windows, macOS,
 and Linux native binaries are no longer downloaded together.
 
-One-command LiveDesk application. The same launcher resolves this computer's
+One-command VuvoDesk application. The same launcher resolves this computer's
 Hub or Client role. A Client starts one managed Agent. A Hub starts the Hub
 server plus one headless Self Agent, so the Hub computer also appears on the
 wall and can be controlled like the other computers.
@@ -15,7 +15,7 @@ generated copies. Edit the source packages and run
 the product. The published `livedesk` package owns both runtime roles; the
 source-only `@livedesk/client` workspace is not a runtime dependency.
 
-LiveDesk's top runtime contract is transmission performance together with
+VuvoDesk's top runtime contract is transmission performance together with
 long-running stability. A faster path is not accepted if it permits duplicate
 capture helpers, stale monitor generations, unbounded frame queues, or an
 unproven Direct/P2P/relay transition. Release builds run the same lifecycle,
@@ -45,7 +45,7 @@ npx -y --prefer-online livedesk@latest --force-role client
 npx -y --prefer-online livedesk@latest hub
 ```
 
-This starts the LiveDesk Hub, opens the local screen wall, accepts clients, and
+This starts the VuvoDesk Hub, opens the local screen wall, accepts clients, and
 connects one local Self Agent through loopback TCP. The Self Agent reuses the
 Hub computer's stable device identity and does not open another login or status
 page. Hub shutdown, update, and role change drain that exact Agent tree before
@@ -54,7 +54,7 @@ The Hub UI/API listens on `127.0.0.1` by default while the client endpoint
 continues to listen on the LAN.
 
 On startup, the launcher checks the Hub ports (`5179` and `5197`), identifies
-stale LiveDesk Hub processes from their Node command line, stops each PID only
+stale VuvoDesk Hub processes from their Node command line, stops each PID only
 once, waits for the ports to be released and bindable, and then starts the new
 Hub. Unrelated processes are preserved and reported with their PID, name, and
 command line. The client endpoint remains fixed at TCP `5197` by default so
@@ -77,7 +77,7 @@ reboot; the generated startup command uses the unified launcher.
 
 ## macOS physical diagnostic
 
-On a Mac with two connected displays, stop every running LiveDesk runtime,
+On a Mac with two connected displays, stop every running VuvoDesk runtime,
 start visibly different continuously moving content on both displays, grant
 Screen Recording and Accessibility permissions, then explicitly confirm that
 the motion is already running:
@@ -87,7 +87,7 @@ npx -y --prefer-online livedesk@latest diagnose mac-physical --confirm-active-mo
 ```
 
 This command branches before role resolution, state migration, and the normal
-runtime lock. It refuses to overlap an existing LiveDesk runtime or capture
+runtime lock. It refuses to overlap an existing VuvoDesk runtime or capture
 helper, and normal macOS startup reciprocally refuses an active diagnostic
 lease. The lease owner authorizes exactly one direct-child production unified
 Hub launcher and one direct-child production unified Client launcher using the
@@ -164,5 +164,5 @@ VITE_LIVEDESK_ADSENSE_CLIENT=ca-pub-...
 VITE_LIVEDESK_ADSENSE_SLOT=...
 ```
 
-Without those values, LiveDesk renders a neutral sponsored-placement placeholder
+Without those values, VuvoDesk renders a neutral sponsored-placement placeholder
 so the free-plan layout can still be tested.