fix(config): migrate device API URLs to kikivok domain

docs/knowledge vault/device-auth-v2-flow.zh-CN.md

@@ -695,7 +695,7 @@ control_plane_multimodal_auth_fetch();
 再请求：
 
 ```text
-POST https://gz.api.talkingq.com/token/api/device/token
+POST https://gz.api.kikivok.com/token/api/device/token
 ```
 
 请求头：

docs/knowledge vault/runtime-diagnostics-and-network-recovery-config.md

@@ -121,7 +121,7 @@ The 2026-08-12 device log captured the complete failure and recovery chain:
 1. Downstream TTS audio stopped arriving and the three-second playback watchdog
    retired the unresponsive WebSocket after its bounded Stop acknowledgement
    also timed out.
-2. The token HTTPS preflight failed to resolve `gz.api.talkingq.com`. The STA
+2. The token HTTPS preflight failed to resolve `gz.api.kikivok.com`. The STA
    still reported an IP address, DHCP state, strong RSSI (`-38` to `-41 dBm`),
    and configured DNS servers.
 3. The gateway and fallback-DNS probes received no reply. More importantly, a

docs/knowledge vault/websocket-and-audio-flow.md

@@ -91,7 +91,7 @@ sequenceDiagram
 | `CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS` | 未启用 | 不直接使用静态 API Key |
 | `CONFIG_MULTIMODAL_AUTH_BYPASS_TOKEN_SERVICE` | 未启用 | 不绕过设备 Token 服务 |
 | `CONFIG_AUTH_V2_ENABLE` | `y` | 获取业务 Token 时使用设备 JWT 鉴权 |
-| `CONFIG_MULTIMODAL_DEVICE_TOKEN_URL` | `https://gz.api.talkingq.com/token/api/device/token` | 设备业务 Token 接口 |
+| `CONFIG_MULTIMODAL_DEVICE_TOKEN_URL` | `https://gz.api.kikivok.com/token/api/device/token` | 设备业务 Token 接口 |
 | `CONFIG_MULTIMODAL_WS_URI` | `wss://dashscope.aliyuncs.com/api-ws/v1/inference` | 多模态 WebSocket 地址 |
 | `CONFIG_MULTIMODAL_CONNECT_TIMEOUT_MS` | `10000` | 建连网络超时，10 秒 |
 | `CONFIG_MULTIMODAL_RECONNECT_DELAY_MS` | `2000` | WebSocket 自动重连间隔，2 秒 |