docs(dsh): keep the example endpoint out of the GUI's link renderer

The Web GUI renders a code span whose content is exactly an http(s) URL as a
clickable link inside the code chip, so the leftover endpoint example became
a link. The example is now written without its scheme, which no renderer
linkifies, and the space added by 2fc90233 (outside the code span, so it never
had any effect) is dropped again.

The guarantee is also narrowed to what the code does: a leftover record is
re-keyed when it can be proven to be this plugin's service.

integrations/dsh/docs/environment.md

@@ -164,10 +164,11 @@ processes it manages when the Host exits. The plugin owns a small service adapte
 - A service that occupies the port but fails the health check is reported as a conflict; if it is provably this
   plugin's service, the tab still offers **Stop**.
 - A record left by an older version under a path prefix of the same origin (for example
-  `http://127.0.0.1:2333/reme`) describes the **same** local service, because the launch configures only host
-  and port. Such a record is re-keyed to the endpoint on screen and then managed like any other launch: **Stop**
-  is offered, and **Start** replaces it. It is never reported as a foreign process the tab cannot act on, which
-  would leave the user with a process to kill by hand.
+  `127.0.0.1:2333/reme`) describes the **same** local service, because the launch configures only host
+  and port. When it can be proven to be this plugin's service, such a record is re-keyed to the endpoint on
+  screen and then managed like any other launch: **Stop** is offered, and **Start** replaces it. It is then
+  not reported as a foreign process the tab cannot act on, which would leave the user with a process to
+  kill by hand.
 - **Stop** tree-kills the recorded process (process group on POSIX, `taskkill /T /F` on Windows), waits for it to
   exit, escalates (POSIX: `SIGTERM` then `SIGKILL`; Windows: force `taskkill` again), and clears the record only
   after the pid is gone. A service started elsewhere stays untouched and is only observed.

integrations/dsh/docs/environment_ZH.md

@@ -130,9 +130,10 @@ ReMe 在服务启动时读取 workspace 目录下的 `.env`；标签页从不把
   **忘记**针对的正是那条记录（可能是另一个端口上的记录，而不是当前显示的地址），并带上它的 pid：记录在此期间被换掉时，
   Host 会拒绝而不是静默丢弃新记录。
 - 服务占用端口但健康检查失败时显示为“端口被占用”；若能证明是本插件启动的，标签页仍给出**停止**按钮。
-- 旧版本遗留在同一源（origin）某个路径前缀下（例如 `http://127.0.0.1:2333/reme` ）的记录，描述的是**同一个**本地服务——
-  启动只配置 host 与端口。这种记录会被重新登记到当前显示的地址，随后与其他启动一样被管理：给出**停止**按钮，
-  **启动**也会替换它。它不会再被当成标签页无从处理的外部进程，否则用户只能自己去杀进程。
+- 旧版本遗留在同一源（origin）某个路径前缀下（例如 `127.0.0.1:2333/reme`）的记录，描述的是**同一个**本地服务——
+  启动只配置 host 与端口。只要能证明它是本插件启动的，这种记录就会被重新登记到当前显示的地址，随后与其他启动
+  一样被管理：给出**停止**按钮，**启动**也会替换它。它不会再被当成标签页无从处理的外部进程，否则用户只能自己去
+  杀进程。
 - **停止**会树杀记录的进程（POSIX 上按进程组、Windows 上为 `taskkill /T /F`），等待其退出，必要时升级（POSIX：
   `SIGTERM` 后 `SIGKILL`；Windows：再次强制 `taskkill`），并**在 pid 真正消失之后**才清除记录。别处启动的服务不受影响，
   只会被观察。