@symerian/symi 3.0.20 → 3.0.22

package/docs/web/control-ui.md

@@ -1,247 +0,0 @@
----
-summary: "Browser-based control UI for the Gateway (chat, nodes, config)"
-read_when:
-  - You want to operate the Gateway from a browser
-  - You want Tailnet access without SSH tunnels
-title: "Control UI"
----
-
-# Control UI (browser)
-
-The Control UI is a small **Vite + Lit** single-page app served by the Gateway:
-
-- default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/symi`)
-
-It speaks **directly to the Gateway WebSocket** on the same port.
-
-## Quick open (local)
-
-If the Gateway is running on the same computer, open:
-
-- [http://127.0.0.1:18789/](http://127.0.0.1:18789/) (or [http://localhost:18789/](http://localhost:18789/))
-
-If the page fails to load, start the Gateway first: `symi gateway`.
-
-Auth is supplied during the WebSocket handshake via:
-
-- `connect.params.auth.token`
-- `connect.params.auth.password`
-  The dashboard settings panel lets you store a token; passwords are not persisted.
-  The onboarding wizard generates a gateway token by default, so paste it here on first connect.
-
-## Device pairing (first connection)
-
-When you connect to the Control UI from a new browser or device, the Gateway
-requires a **one-time pairing approval** — even if you're on the same Tailnet
-with `gateway.auth.allowTailscale: true`. This is a security measure to prevent
-unauthorized access.
-
-**What you'll see:** "disconnected (1008): pairing required"
-
-**To approve the device:**
-
-```bash
-# List pending requests
-symi devices list
-
-# Approve by request ID
-symi devices approve <requestId>
-```
-
-Once approved, the device is remembered and won't require re-approval unless
-you revoke it with `symi devices revoke --device <id> --role <role>`. See
-[Devices CLI](/cli/devices) for token rotation and revocation.
-
-**Notes:**
-
-- Local connections (`127.0.0.1`) are auto-approved.
-- Remote connections (LAN, Tailnet, etc.) require explicit approval.
-- Each browser profile generates a unique device ID, so switching browsers or
-  clearing browser data will require re-pairing.
-
-## What it can do (today)
-
-- Chat with the model via Gateway WS (`chat.history`, `chat.send`, `chat.abort`, `chat.inject`)
-- Stream tool calls + live tool output cards in Chat (agent events)
-- Instances: presence list + refresh (`system-presence`)
-- Sessions: list + per-session thinking/verbose overrides (`sessions.list`, `sessions.patch`)
-- Cron jobs: list/add/run/enable/disable + run history (`cron.*`)
-- Skills: status, enable/disable, install, API key updates (`skills.*`)
-- Nodes: list + caps (`node.list`)
-- Exec approvals: edit gateway or node allowlists + ask policy for `exec host=gateway/node` (`exec.approvals.*`)
-- Config: view/edit `~/.symi/symi.json` (`config.get`, `config.set`)
-- Config: apply + restart with validation (`config.apply`) and wake the last active session
-- Config writes include a base-hash guard to prevent clobbering concurrent edits
-- Config schema + form rendering (`config.schema`, including plugin + channel schemas); Raw JSON editor remains available
-- Debug: status/health/models snapshots + event log + manual RPC calls (`status`, `health`, `models.list`)
-- Logs: live tail of gateway file logs with filter/export (`logs.tail`)
-- Update: run a package/git update + restart (`update.run`) with a restart report
-
-Cron jobs panel notes:
-
-- For isolated jobs, delivery defaults to announce summary. You can switch to none if you want internal-only runs.
-- Channel/target fields appear when announce is selected.
-- Webhook mode uses `delivery.mode = "webhook"` with `delivery.to` set to a valid HTTP(S) webhook URL.
-- For main-session jobs, webhook and none delivery modes are available.
-- Set `cron.webhookToken` to send a dedicated bearer token, if omitted the webhook is sent without an auth header.
-- Deprecated fallback: stored legacy jobs with `notify: true` can still use `cron.webhook` until migrated.
-
-## Chat behavior
-
-- `chat.send` is **non-blocking**: it acks immediately with `{ runId, status: "started" }` and the response streams via `chat` events.
-- Re-sending with the same `idempotencyKey` returns `{ status: "in_flight" }` while running, and `{ status: "ok" }` after completion.
-- `chat.history` responses are size-bounded for UI safety. When transcript entries are too large, Gateway may truncate long text fields, omit heavy metadata blocks, and replace oversized messages with a placeholder (`[chat.history omitted: message too large]`).
-- `chat.inject` appends an assistant note to the session transcript and broadcasts a `chat` event for UI-only updates (no agent run, no channel delivery).
-- Stop:
-  - Click **Stop** (calls `chat.abort`)
-  - Type `/stop` (or `stop|esc|abort|wait|exit|interrupt`) to abort out-of-band
-  - `chat.abort` supports `{ sessionKey }` (no `runId`) to abort all active runs for that session
-- Abort partial retention:
-  - When a run is aborted, partial assistant text can still be shown in the UI
-  - Gateway persists aborted partial assistant text into transcript history when buffered output exists
-  - Persisted entries include abort metadata so transcript consumers can tell abort partials from normal completion output
-
-## Tailnet access (recommended)
-
-### Integrated Tailscale Serve (preferred)
-
-Keep the Gateway on loopback and let Tailscale Serve proxy it with HTTPS:
-
-```bash
-symi gateway --tailscale serve
-```
-
-Open:
-
-- `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
-
-By default, Control UI/WebSocket Serve requests can authenticate via Tailscale identity headers
-(`tailscale-user-login`) when `gateway.auth.allowTailscale` is `true`. Symi
-verifies the identity by resolving the `x-forwarded-for` address with
-`tailscale whois` and matching it to the header, and only accepts these when the
-request hits loopback with Tailscale’s `x-forwarded-*` headers. Set
-`gateway.auth.allowTailscale: false` (or force `gateway.auth.mode: "password"`)
-if you want to require a token/password even for Serve traffic.
-Tokenless Serve auth assumes the gateway host is trusted. If untrusted local
-code may run on that host, require token/password auth.
-
-### Bind to tailnet + token
-
-```bash
-symi gateway --bind tailnet --token "$(openssl rand -hex 32)"
-```
-
-Then open:
-
-- `http://<tailscale-ip>:18789/` (or your configured `gateway.controlUi.basePath`)
-
-Paste the token into the UI settings (sent as `connect.params.auth.token`).
-
-## Insecure HTTP
-
-If you open the dashboard over plain HTTP (`http://<lan-ip>` or `http://<tailscale-ip>`),
-the browser runs in a **non-secure context** and blocks WebCrypto. By default,
-Symi **blocks** Control UI connections without device identity.
-
-**Recommended fix:** use HTTPS (Tailscale Serve) or open the UI locally:
-
-- `https://<magicdns>/` (Serve)
-- `http://127.0.0.1:18789/` (on the gateway host)
-
-**Insecure-auth toggle behavior:**
-
-```json5
-{
-  gateway: {
-    controlUi: { allowInsecureAuth: true },
-    bind: "tailnet",
-    auth: { mode: "token", token: "replace-me" },
-  },
-}
-```
-
-`allowInsecureAuth` does not bypass Control UI device identity or pairing checks.
-
-**Break-glass only:**
-
-```json5
-{
-  gateway: {
-    controlUi: { dangerouslyDisableDeviceAuth: true },
-    bind: "tailnet",
-    auth: { mode: "token", token: "replace-me" },
-  },
-}
-```
-
-`dangerouslyDisableDeviceAuth` disables Control UI device identity checks and is a
-severe security downgrade. Revert quickly after emergency use.
-
-See [Tailscale](/gateway/tailscale) for HTTPS setup guidance.
-
-## Building the UI
-
-The Gateway serves static files from `dist/control-ui`. Build them with:
-
-```bash
-pnpm ui:build # auto-installs UI deps on first run
-```
-
-Optional absolute base (when you want fixed asset URLs):
-
-```bash
-SYMI_CONTROL_UI_BASE_PATH=/symi/ pnpm ui:build
-```
-
-For local development (separate dev server):
-
-```bash
-pnpm ui:dev # auto-installs UI deps on first run
-```
-
-Then point the UI at your Gateway WS URL (e.g. `ws://127.0.0.1:18789`).
-
-## Debugging/testing: dev server + remote Gateway
-
-The Control UI is static files; the WebSocket target is configurable and can be
-different from the HTTP origin. This is handy when you want the Vite dev server
-locally but the Gateway runs elsewhere.
-
-1. Start the UI dev server: `pnpm ui:dev`
-2. Open a URL like:
-
-```text
-http://localhost:5173/?gatewayUrl=ws://<gateway-host>:18789
-```
-
-Optional one-time auth (if needed):
-
-```text
-http://localhost:5173/?gatewayUrl=wss://<gateway-host>:18789&token=<gateway-token>
-```
-
-Notes:
-
-- `gatewayUrl` is stored in localStorage after load and removed from the URL.
-- `token` is stored in localStorage; `password` is kept in memory only.
-- When `gatewayUrl` is set, the UI does not fall back to config or environment credentials.
-  Provide `token` (or `password`) explicitly. Missing explicit credentials is an error.
-- Use `wss://` when the Gateway is behind TLS (Tailscale Serve, HTTPS proxy, etc.).
-- `gatewayUrl` is only accepted in a top-level window (not embedded) to prevent clickjacking.
-- For cross-origin dev setups (e.g. `pnpm ui:dev` to a remote Gateway), add the UI
-  origin to `gateway.controlUi.allowedOrigins`.
-
-Example:
-
-```json5
-{
-  gateway: {
-    controlUi: {
-      allowedOrigins: ["http://localhost:5173"],
-    },
-  },
-}
-```
-
-Remote access setup details: [Remote access](/gateway/remote).

package/docs/web/dashboard.md

@@ -1,46 +0,0 @@
----
-summary: "Gateway dashboard (Control UI) access and auth"
-read_when:
-  - Changing dashboard authentication or exposure modes
-title: "Dashboard"
----
-
-# Dashboard (Control UI)
-
-The Gateway dashboard is the browser Control UI served at `/` by default
-(override with `gateway.controlUi.basePath`).
-
-Quick open (local Gateway):
-
-- [http://127.0.0.1:18789/](http://127.0.0.1:18789/) (or [http://localhost:18789/](http://localhost:18789/))
-
-Key references:
-
-- [Control UI](/web/control-ui) for usage and UI capabilities.
-- [Tailscale](/gateway/tailscale) for Serve/Funnel automation.
-- [Web surfaces](/web) for bind modes and security notes.
-
-Authentication is enforced at the WebSocket handshake via `connect.params.auth`
-(token or password). See `gateway.auth` in [Gateway configuration](/gateway/configuration).
-
-Security note: the Control UI is an **admin surface** (chat, config, exec approvals).
-Do not expose it publicly. The UI stores the token in `localStorage` after first load.
-Prefer localhost, Tailscale Serve, or an SSH tunnel.
-
-## Fast path (recommended)
-
-- After onboarding, the CLI auto-opens the dashboard and prints a clean (non-tokenized) link.
-- Re-open anytime: `symi dashboard` (copies link, opens browser if possible, shows SSH hint if headless).
-- If the UI prompts for auth, paste the token from `gateway.auth.token` (or `SYMI_GATEWAY_TOKEN`) into Control UI settings.
-
-## Token basics (local vs remote)
-
-- **Localhost**: open `http://127.0.0.1:18789/`.
-- **Token source**: `gateway.auth.token` (or `SYMI_GATEWAY_TOKEN`); the UI stores a copy in localStorage after you connect.
-- **Not localhost**: use Tailscale Serve (tokenless for Control UI/WebSocket if `gateway.auth.allowTailscale: true`, assumes trusted gateway host; HTTP APIs still need token/password), tailnet bind with a token, or an SSH tunnel. See [Web surfaces](/web).
-
-## If you see “unauthorized” / 1008
-
-- Ensure the gateway is reachable (local: `symi status`; remote: SSH tunnel `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/`).
-- Retrieve the token from the gateway host: `symi config get gateway.auth.token` (or generate one: `symi doctor --generate-gateway-token`).
-- In the dashboard settings, paste the token into the auth field, then connect.

package/docs/web/index.md

@@ -1,118 +0,0 @@
----
-summary: "Gateway web surfaces: Control UI, bind modes, and security"
-read_when:
-  - You want to access the Gateway over Tailscale
-  - You want the browser Control UI and config editing
-title: "Web"
----
-
-# Web (Gateway)
-
-The Gateway serves a small **browser Control UI** (Vite + Lit) from the same port as the Gateway WebSocket:
-
-- default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/symi`)
-
-Capabilities live in [Control UI](/web/control-ui).
-This page focuses on bind modes, security, and web-facing surfaces.
-
-## Webhooks
-
-When `hooks.enabled=true`, the Gateway also exposes a small webhook endpoint on the same HTTP server.
-See [Gateway configuration](/gateway/configuration) → `hooks` for auth + payloads.
-
-## Config (default-on)
-
-The Control UI is **enabled by default** when assets are present (`dist/control-ui`).
-You can control it via config:
-
-```json5
-{
-  gateway: {
-    controlUi: { enabled: true, basePath: "/symi" }, // basePath optional
-  },
-}
-```
-
-## Tailscale access
-
-### Integrated Serve (recommended)
-
-Keep the Gateway on loopback and let Tailscale Serve proxy it:
-
-```json5
-{
-  gateway: {
-    bind: "loopback",
-    tailscale: { mode: "serve" },
-  },
-}
-```
-
-Then start the gateway:
-
-```bash
-symi gateway
-```
-
-Open:
-
-- `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
-
-### Tailnet bind + token
-
-```json5
-{
-  gateway: {
-    bind: "tailnet",
-    controlUi: { enabled: true },
-    auth: { mode: "token", token: "your-token" },
-  },
-}
-```
-
-Then start the gateway (token required for non-loopback binds):
-
-```bash
-symi gateway
-```
-
-Open:
-
-- `http://<tailscale-ip>:18789/` (or your configured `gateway.controlUi.basePath`)
-
-### Public internet (Funnel)
-
-```json5
-{
-  gateway: {
-    bind: "loopback",
-    tailscale: { mode: "funnel" },
-    auth: { mode: "password" }, // or SYMI_GATEWAY_PASSWORD
-  },
-}
-```
-
-## Security notes
-
-- Gateway auth is required by default (token/password or Tailscale identity headers).
-- Non-loopback binds still **require** a shared token/password (`gateway.auth` or env).
-- The wizard generates a gateway token by default (even on loopback).
-- The UI sends `connect.params.auth.token` or `connect.params.auth.password`.
-- The Control UI sends anti-clickjacking headers and only accepts same-origin browser
-  websocket connections unless `gateway.controlUi.allowedOrigins` is set.
-- With Serve, Tailscale identity headers can satisfy Control UI/WebSocket auth
-  when `gateway.auth.allowTailscale` is `true` (no token/password required).
-  HTTP API endpoints still require token/password. Set
-  `gateway.auth.allowTailscale: false` to require explicit credentials. See
-  [Tailscale](/gateway/tailscale) and [Security](/gateway/security). This
-  tokenless flow assumes the gateway host is trusted.
-- `gateway.tailscale.mode: "funnel"` requires `gateway.auth.mode: "password"` (shared password).
-
-## Building the UI
-
-The Gateway serves static files from `dist/control-ui`. Build them with:
-
-```bash
-pnpm ui:build # auto-installs UI deps on first run
-```

package/docs/web/tui.md

@@ -1,162 +0,0 @@
----
-summary: "Terminal UI (TUI): connect to the Gateway from any machine"
-read_when:
-  - You want a beginner-friendly walkthrough of the TUI
-  - You need the complete list of TUI features, commands, and shortcuts
-title: "TUI"
----
-
-# TUI (Terminal UI)
-
-## Quick start
-
-1. Start the Gateway.
-
-```bash
-symi gateway
-```
-
-2. Open the TUI.
-
-```bash
-symi tui
-```
-
-3. Type a message and press Enter.
-
-Remote Gateway:
-
-```bash
-symi tui --url ws://<host>:<port> --token <gateway-token>
-```
-
-Use `--password` if your Gateway uses password auth.
-
-## What you see
-
-- Header: connection URL, current agent, current session.
-- Chat log: user messages, assistant replies, system notices, tool cards.
-- Status line: connection/run state (connecting, running, streaming, idle, error).
-- Footer: connection state + agent + session + model + think/verbose/reasoning + token counts + deliver.
-- Input: text editor with autocomplete.
-
-## Mental model: agents + sessions
-
-- Agents are unique slugs (e.g. `main`, `research`). The Gateway exposes the list.
-- Sessions belong to the current agent.
-- Session keys are stored as `agent:<agentId>:<sessionKey>`.
-  - If you type `/session main`, the TUI expands it to `agent:<currentAgent>:main`.
-  - If you type `/session agent:other:main`, you switch to that agent session explicitly.
-- Session scope:
-  - `per-sender` (default): each agent has many sessions.
-  - `global`: the TUI always uses the `global` session (the picker may be empty).
-- The current agent + session are always visible in the footer.
-
-## Sending + delivery
-
-- Messages are sent to the Gateway; delivery to providers is off by default.
-- Turn delivery on:
-  - `/deliver on`
-  - or the Settings panel
-  - or start with `symi tui --deliver`
-
-## Pickers + overlays
-
-- Model picker: list available models and set the session override.
-- Agent picker: choose a different agent.
-- Session picker: shows only sessions for the current agent.
-- Settings: toggle deliver, tool output expansion, and thinking visibility.
-
-## Keyboard shortcuts
-
-- Enter: send message
-- Esc: abort active run
-- Ctrl+C: clear input (press twice to exit)
-- Ctrl+D: exit
-- Ctrl+L: model picker
-- Ctrl+G: agent picker
-- Ctrl+P: session picker
-- Ctrl+O: toggle tool output expansion
-- Ctrl+T: toggle thinking visibility (reloads history)
-
-## Slash commands
-
-Core:
-
-- `/help`
-- `/status`
-- `/agent <id>` (or `/agents`)
-- `/session <key>` (or `/sessions`)
-- `/model <provider/model>` (or `/models`)
-
-Session controls:
-
-- `/think <off|minimal|low|medium|high>`
-- `/verbose <on|full|off>`
-- `/reasoning <on|off|stream>`
-- `/usage <off|tokens|full>`
-- `/elevated <on|off|ask|full>` (alias: `/elev`)
-- `/activation <mention|always>`
-- `/deliver <on|off>`
-
-Session lifecycle:
-
-- `/new` or `/reset` (reset the session)
-- `/abort` (abort the active run)
-- `/settings`
-- `/exit`
-
-Other Gateway slash commands (for example, `/context`) are forwarded to the Gateway and shown as system output. See [Slash commands](/tools/slash-commands).
-
-## Local shell commands
-
-- Prefix a line with `!` to run a local shell command on the TUI host.
-- The TUI prompts once per session to allow local execution; declining keeps `!` disabled for the session.
-- Commands run in a fresh, non-interactive shell in the TUI working directory (no persistent `cd`/env).
-- A lone `!` is sent as a normal message; leading spaces do not trigger local exec.
-
-## Tool output
-
-- Tool calls show as cards with args + results.
-- Ctrl+O toggles between collapsed/expanded views.
-- While tools run, partial updates stream into the same card.
-
-## History + streaming
-
-- On connect, the TUI loads the latest history (default 200 messages).
-- Streaming responses update in place until finalized.
-- The TUI also listens to agent tool events for richer tool cards.
-
-## Connection details
-
-- The TUI registers with the Gateway as `mode: "tui"`.
-- Reconnects show a system message; event gaps are surfaced in the log.
-
-## Options
-
-- `--url <url>`: Gateway WebSocket URL (defaults to config or `ws://127.0.0.1:<port>`)
-- `--token <token>`: Gateway token (if required)
-- `--password <password>`: Gateway password (if required)
-- `--session <key>`: Session key (default: `main`, or `global` when scope is global)
-- `--deliver`: Deliver assistant replies to the provider (default off)
-- `--thinking <level>`: Override thinking level for sends
-- `--timeout-ms <ms>`: Agent timeout in ms (defaults to `agents.defaults.timeoutSeconds`)
-
-Note: when you set `--url`, the TUI does not fall back to config or environment credentials.
-Pass `--token` or `--password` explicitly. Missing explicit credentials is an error.
-
-## Troubleshooting
-
-No output after sending a message:
-
-- Run `/status` in the TUI to confirm the Gateway is connected and idle/busy.
-- Check the Gateway logs: `symi logs --follow`.
-- Confirm the agent can run: `symi status` and `symi models status`.
-- If you expect messages in a chat channel, enable delivery (`/deliver on` or `--deliver`).
-- `--history-limit <n>`: History entries to load (default 200)
-
-## Connection troubleshooting
-
-- `disconnected`: ensure the Gateway is running and your `--url/--token/--password` are correct.
-- No agents in picker: check `symi agents list` and your routing config.
-- Empty session picker: you might be in global scope or have no sessions yet.

package/docs/web/webchat.md

@@ -1,53 +0,0 @@
----
-summary: "Loopback WebChat static host and Gateway WS usage for chat UI"
-read_when:
-  - Debugging or configuring WebChat access
-title: "WebChat"
----
-
-# WebChat (Gateway WebSocket UI)
-
-Status: the macOS/iOS SwiftUI chat UI talks directly to the Gateway WebSocket.
-
-## What it is
-
-- A native chat UI for the gateway (no embedded browser and no local static server).
-- Uses the same sessions and routing rules as other channels.
-- Deterministic routing: replies always go back to WebChat.
-
-## Quick start
-
-1. Start the gateway.
-2. Open the WebChat UI (macOS/iOS app) or the Control UI chat tab.
-3. Ensure gateway auth is configured (required by default, even on loopback).
-
-## How it works (behavior)
-
-- The UI connects to the Gateway WebSocket and uses `chat.history`, `chat.send`, and `chat.inject`.
-- `chat.history` is bounded for stability: Gateway may truncate long text fields, omit heavy metadata, and replace oversized entries with `[chat.history omitted: message too large]`.
-- `chat.inject` appends an assistant note directly to the transcript and broadcasts it to the UI (no agent run).
-- Aborted runs can keep partial assistant output visible in the UI.
-- Gateway persists aborted partial assistant text into transcript history when buffered output exists, and marks those entries with abort metadata.
-- History is always fetched from the gateway (no local file watching).
-- If the gateway is unreachable, WebChat is read-only.
-
-## Remote use
-
-- Remote mode tunnels the gateway WebSocket over SSH/Tailscale.
-- You do not need to run a separate WebChat server.
-
-## Configuration reference (WebChat)
-
-Full configuration: [Configuration](/gateway/configuration)
-
-Channel options:
-
-- No dedicated `webchat.*` block. WebChat uses the gateway endpoint + auth settings below.
-
-Related global options:
-
-- `gateway.port`, `gateway.bind`: WebSocket host/port.
-- `gateway.auth.mode`, `gateway.auth.token`, `gateway.auth.password`: WebSocket auth (token/password).
-- `gateway.auth.mode: "trusted-proxy"`: reverse-proxy auth for browser clients (see [Trusted Proxy Auth](/gateway/trusted-proxy-auth)).
-- `gateway.remote.url`, `gateway.remote.token`, `gateway.remote.password`: remote gateway target.
-- `session.*`: session storage and main key defaults.

package/docs/zh-CN/AGENTS.md

@@ -1,59 +0,0 @@
-# AGENTS.md - zh-CN 文档翻译工作区
-
-## Read When
-
-- 维护 `docs/zh-CN/**`
-- 更新中文翻译流水线（glossary/TM/prompt）
-- 处理中文翻译反馈或回归
-
-## Pipeline（docs-i18n）
-
-- 源文档：`docs/**/*.md`
-- 目标文档：`docs/zh-CN/**/*.md`
-- 术语表：`docs/.i18n/glossary.zh-CN.json`
-- 翻译记忆库：`docs/.i18n/zh-CN.tm.jsonl`
-- 提示词规则：`scripts/docs-i18n/translator.go`
-
-常用运行方式：
-
-```bash
-# 批量（doc 模式，可并行）
-go run scripts/docs-i18n/main.go -mode doc -parallel 6 docs/**/*.md
-
-# 单文件
-
-go run scripts/docs-i18n/main.go -mode doc docs/channels/matrix.md
-
-# 小范围补丁（segment 模式，使用 TM；不支持并行）
-go run scripts/docs-i18n/main.go -mode segment docs/channels/matrix.md
-```
-
-注意事项：
-
-- doc 模式用于整页翻译；segment 模式用于小范围修补（依赖 TM）。
-- 超大文件若超时，优先做**定点替换**或拆分后再跑。
-- 翻译后检查中文引号、CJK-Latin 间距和术语一致性。
-
-## zh-CN 样式规则
-
-- CJK-Latin 间距：遵循 W3C CLREQ（如 `Gateway 网关`、`Skills 配置`）。
-- 中文引号：正文/标题使用 `“”`；代码/CLI/键名保持 ASCII 引号。
-- 术语保留英文：`Skills`、`local loopback`、`Tailscale`。
-- 代码块/内联代码：保持原样，不在代码内插入空格或引号替换。
-
-## 关键术语（#6995 修复）
-
-- `Gateway 网关`
-- `Skills 配置`
-- `沙箱`
-- `预期键名`
-- `配套应用`
-- `分块流式传输`
-- `设备发现`
-
-## 反馈与变更记录
-
-- 反馈来源：GitHub issue #6995
-- 反馈用户：@AaronWander、@taiyi747、@Explorer1092、@rendaoyuan
-- 变更要点：更新 prompt 规则、扩充 glossary、清理 TM、批量再生成 + 定点修复
-- 参考链接：https://github.com/symi/symi/issues/6995