docs(brand): rename SciLaxy references to Liyan Labs

CLAUDE.md

@@ -140,10 +140,10 @@ cargo run --bin lab serve    # Boot engine + gRPC server (TCP + UDS)
 cargo test               # Run all tests (e2e + integration)
 ```
 
-## Integration with SciLaxy
+## Integration with Liyan Labs
 
 ```
-SciLaxy Cloud ←WebSocket→ Runner (gRPC client) ←gRPC→ `lab serve` (OsdlEngine) → Transport → Device
+Liyan Labs Cloud ←WebSocket→ Runner (gRPC client) ←gRPC→ `lab serve` (OsdlEngine) → Transport → Device
 ```
 
 The runner is a **pure gRPC client** of OpenSDL, not an embedded crate:

README.md

@@ -12,7 +12,7 @@ The included UniLabOS adapter supports the
 ecosystem.
 
 ```
-              Your Application (SciLaxy, LIMS, custom)
+              Your Application (Liyan Labs, LIMS, custom)
                         │
                         │  gRPC / CLI
                         │

crates/osdl-core/src/media/mod.rs

@@ -107,7 +107,7 @@ impl MediaSourceConfig {
 /// `http_host` / `webrtc_host`; bare `host[:port]` uses the `http://`
 /// default used by local recipes (`localhost:18085`).
 ///
-/// Why this matters: the SciLaxy web frontend is served over HTTPS, and
+/// Why this matters: the Liyan Labs web frontend is served over HTTPS, and
 /// browsers refuse to `fetch()` `http://...` from an HTTPS page (mixed
 /// content). Deployments behind TLS termination must therefore include the
 /// `https://` prefix so playback requests can leave the renderer.

docs/architecture.md

@@ -187,16 +187,16 @@ osdl/devices/{device_id}/status            # mother publishes parsed device stat
 osdl/devices/{device_id}/online            # retained + LWT
 ```
 
-## Integration with SciLaxy
+## Integration with Liyan Labs
 
-SciLaxy Desktop supervises a standalone `lab serve` process:
+Liyan Labs Desktop supervises a standalone `lab serve` process:
 
 ```
-SciLaxy Cloud → WebSocket → Runner (gRPC client) → `lab serve` → Transport → Device
+Liyan Labs Cloud → WebSocket → Runner (gRPC client) → `lab serve` → Transport → Device
 ```
 
 - The Electron main process starts, monitors, and stops `lab serve`.
-- `scilaxy-runner` depends only on `osdl-proto` behind `feature = "osdl"`.
+- `liyanlabs-runner` depends only on `osdl-proto` behind `feature = "osdl"`.
 - The Runner connects to the configured gRPC endpoint and forwards commands and
   `OsdlEvent` data over its existing cloud WebSocket.
 - `osdl-core` and `osdl-server` remain in the standalone OpenSDL process.

docs/cs-architecture.md

@@ -238,10 +238,10 @@ lab --endpoint http://lab.local:50051 …  ───→  lab serve --listen 0.0.
           │
           ├── UDS (Linux/macOS) or loopback TCP (Windows)
           │
-[ scilaxy-runner: osdl-proto gRPC client ]
+[ liyanlabs-runner: osdl-proto gRPC client ]
           │
           ▼
-   SciLaxy Cloud WebSocket
+   Liyan Labs Cloud WebSocket
 ```
 
 The Runner does not link `osdl-core` or hold an `EngineHandle`. Electron

docs/getting-started.md

@@ -440,10 +440,10 @@ mosquitto_pub -h localhost -t "osdl/serial/pump-01/tx" -m "/1ZR
 3. 在 `adapter/unilabos.rs` 中注册路由
 4. 写测试 → 跑通 → 提交
 
-### 接入 SciLaxy Desktop
+### 接入 Liyan Labs Desktop
 
 ```
-SciLaxy Desktop (Electron) → Runner (gRPC 客户端) → `lab serve` → ESP32 → 设备
+Liyan Labs Desktop (Electron) → Runner (gRPC 客户端) → `lab serve` → ESP32 → 设备
 ```
 
 Electron 主进程负责启动和监管独立的 `lab serve` 进程。Runner 仅依赖

docs/recipes/media-gateway.md

@@ -187,7 +187,7 @@ the HTTP plane have different transport requirements:
 - The playback endpoint serves **HLS playlists**, HTTP-FLV, and **WHEP
   signalling**. Do not send RTMP to an HTTP-only ingress.
 
-The reserved domains below are placeholders, not deployed SciLaxy services:
+The reserved domains below are placeholders, not deployed Liyan Labs services:
 
 ```yaml
 remote_rtmp: