@hyzyn/dsh-tty 0.19.1 → 0.19.2

package/README.en.md

@@ -179,12 +179,12 @@ lacks that service the box is switched back off and disabled, with a note that o
   empty or 22 (the default)** — matching the connecting side's `spec.port ?? 22` (empty means 22), so
   “empty / `22` / `" 22 "`” all collapse into one key and the same account never ends up with two names or one
   password stored twice; a non-default port does take part (the same host on another port is often a different
-  box behind NAT). `field` is `PASSWORD` / `PASSPHRASE`; e.g. `hsadmin@192.168.80.248:22` →
+  box behind NAT). `field` is `PASSWORD` / `PASSPHRASE`; e.g. `hsadmin@192.0.2.10:22` →
   `DSH_TTY_HSADMIN_192_168_80_248_PASSWORD`. It is **derived from the resource identity and carries no hash** — the
   same school as git-credential-store's `protocol://username@host` and docker credential helpers'
   `ServerURL` + `Username`: host and username **are ASCII identifiers already**, so nothing needs sanitizing and
   nothing needs a hash to disambiguate. The old hash-based version was patching over "sanitize a human label into a
-  key": the reference grammar accepts ASCII only, so `HS 248` / `HS-248` / `HS_248` collapse to exactly the same
+  key": the reference grammar accepts ASCII only, so `HS 248` / `lab-a` / `HS_248` collapse to exactly the same
   string and only a hash could stop them silently overwriting each other. A resource identity has no such trap — a
   collision can only happen for **the same host, the same user, the same port**, which is the same password by
   definition (sharing it is correct behaviour). **The connection name never takes part in the key**, so renaming a
@@ -559,7 +559,7 @@ single command** (the typical use is dsh-docker’s card “Terminal” button
 ctx.inject(['ttyTerminal'], (c) => {
   c.ttyTerminal.open({
     command: "docker exec -it 'ems-consumer-test' sh",  // required, single line, ≤2000 characters
-    book: 'HS-248',        // one of the two: connection-book entry name → SSH tab
+    book: 'lab-a',        // one of the two: connection-book entry name → SSH tab
     // spec: { host, port, username, auth, agentForward },  // inline SSH fields
     // (neither = local tab, with cwd giving the working directory)
     label: 'ems-consumer-test · exec',
@@ -592,7 +592,7 @@ ctx.inject(['ttyTerminal'], (c) => {
   if (Number(c.ttyTerminal.version ?? 0) < 2) { /* older version: fall back to open */ }
   const dispose = c.ttyTerminal.mount(hostEl, {
     command: "docker exec -it 'ems-consumer-test' sh",  // the same set of options as open
-    book: 'HS-248',                                     // book > spec > local
+    book: 'lab-a',                                     // book > spec > local
     label: 'ems-consumer-test · exec',
   })
   // When collapsing your own drawer:
@@ -628,8 +628,8 @@ A mount slot is **connection-scoped**: its credentials / target come from the te
 So since 0.19.0 every pane records its **owner tab** (`options.ownerSid`, defaulting to the active tab at
 mount time): switching to another tab **hides** the pane (`data-dock-hidden`; its DOM and your rendered tree
 survive, in-flight transfers keep running) and switching back restores the scene; closing the owner tab tears
-the pane down. Without this, the pane stayed put across a tab switch — its title read `SFTP · cdc-test-161`
-while the active tab was `192.168.80.248`, leaving **another host**’s file listing on screen (worst case:
+the pane down. Without this, the pane stayed put across a tab switch — its title read `SFTP · lab-b`
+while the active tab was `192.0.2.10`, leaving **another host**’s file listing on screen (worst case:
 uploading to the wrong host). Passing `ownerSid: null` means “owned by no tab” (always visible); that is what
 happens automatically when the panel is open with no tabs at all, and a consumer can use it to declare “this
 pane has nothing to do with tabs, do not hide it on a switch”.

package/README.md

@@ -166,12 +166,12 @@ SSH 会话同表调度：`tty_list` 里 `kind: 'ssh'` 的条目按 `target`
 - **名字**（规则恒定）：`DSH_TTY_<用户名>_<主机>[_<端口>]_<字段>`，**端口留空或 22（默认）时省略**
   —— 与连接侧的 `spec.port ?? 22` 一致（留空即 22），所以"留空 / `22` / `" 22 "`"三种写法归成同一个键，
   同一个账号不会有两个名字、同一个密码不会存两份；非默认端口进键（同一主机不同端口常是 NAT 后面的
-  不同盒子）。字段 = `PASSWORD` / `PASSPHRASE`；例 `hsadmin@192.168.80.248:22` →
+  不同盒子）。字段 = `PASSWORD` / `PASSPHRASE`；例 `hsadmin@192.0.2.10:22` →
   `DSH_TTY_HSADMIN_192_168_80_248_PASSWORD`。**按资源身份派生、不带哈希**——与
   git-credential-store 的 `protocol://username@host`、docker credential helpers 的
   `ServerURL` + `Username` 同一派：host 与 username **本来就是 ASCII 标识符**，不需要清洗、
   也就不需要哈希兜底。曾经的哈希版是在补救"把人类标签清洗成键"：引用文法只认 ASCII，
-  `HS 248` / `HS-248` / `HS_248` 折出来完全一样，只能靠哈希避免静默覆盖 ✗。资源身份没有这个
+  `HS 248` / `lab-a` / `HS_248` 折出来完全一样，只能靠哈希避免静默覆盖 ✗。资源身份没有这个
   死结——撞名只可能发生在**同一主机、同一用户、同一端口**，而那本来就该是同一个密码（共享是
   正确行为）。**连接名完全不参与键**，所以改连接名/改备注都不会换键。空主机或空用户名则拒绝
   存入（键的全部来源，缺一就退化成常量）。代价是可读性弱于人类标签：本对话框的「存入」**只按
@@ -516,7 +516,7 @@ ctx.inject(['ttyConnbar'], (c) => {
 ctx.inject(['ttyTerminal'], (c) => {
   c.ttyTerminal.open({
     command: "docker exec -it 'ems-consumer-test' sh",  // 必填，单行，≤2000 字符
-    book: 'HS-248',        // 二选一：连接簿条目名 → SSH 标签
+    book: 'lab-a',        // 二选一：连接簿条目名 → SSH 标签
     // spec: { host, port, username, auth, agentForward },  // 内联 SSH 字段
     // （都不传 = 本地标签，用 cwd 指定工作目录）
     label: 'ems-consumer-test · exec',
@@ -546,7 +546,7 @@ ctx.inject(['ttyTerminal'], (c) => {
   if (Number(c.ttyTerminal.version ?? 0) < 2) { /* 老版本：退回 open */ }
   const dispose = c.ttyTerminal.mount(hostEl, {
     command: "docker exec -it 'ems-consumer-test' sh",  // 与 open 同一套 options
-    book: 'HS-248',                                     // book > spec > 本地
+    book: 'lab-a',                                     // book > spec > 本地
     label: 'ems-consumer-test · exec',
   })
   // 收起自己的抽屉时：
@@ -578,7 +578,7 @@ ctx.inject(['ttyTerminal'], (c) => {
 pane 记一个「归属标签」（`options.ownerSid`，默认 = 挂载那一刻的活动标签）：切到别的
 标签时整块**收起**（`data-dock-hidden`，DOM 与你 render 的树都保活，在途传输继续跑），
 切回来恢复现场；归属标签被关掉时 pane 一并收掉。不这么做的话，切完标签面板还停在原处
-——标题写着 `SFTP · cdc-test-161`、底下活动标签却是 `192.168.80.248`，面板里躺着**另一台
+——标题写着 `SFTP · lab-b`、底下活动标签却是 `192.0.2.10`，面板里躺着**另一台
 主机**的文件列表（最坏的情况是往错主机上传）。显式传 `ownerSid: null` 表示「不隶属任何
 标签」（一直可见）——面板开着但一个标签都没有时自动落进这一档；消费方也可以用它声明
 「这块与标签无关，别跟着切」。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyzyn/dsh-tty",
-  "version": "0.19.1",
+  "version": "0.19.2",
   "description": "DSH Web GUI 的终端面板插件：侧边栏「终端」大弹窗，xterm.js + PTY 全交互终端（路线1），ssh2 原生 SSH 远程连接（方案 C），tmux 会话持久化（0.10.0），连接栏扩展点 ttyConnbar（0.13.0）、终端服务 ttyTerminal（0.14.0 open / 0.15.0 mount 就地嵌入）、面板内挂载位 ttyPanel（0.16.0 右侧 dock）、服务器状态条（0.17.0：按标签可见性采端主机 CPU / 内存 / 磁盘 / 在线时长 / TCP / 网速 / 温度，SSH 走同连接的非 PTY exec channel、本地走 os/proc，best-effort、不碰 PTY 流）、连接密码存入官方凭据存储（0.18.0：字段里只留 env: 引用、引用名按资源身份派生、候选来自凭据存储 ∪ 连接簿；设置卡片的连接编辑与连接对话框共用同一套表单）、Windows 宿主支持（0.18.1：默认 shell = %COMSPEC%、不做 POSIX 包装层、PowerShell 走 -NoLogo/-Command；shell 集成 / tmux / 状态条三项在 Windows 本地不适用，README 有完整边界）。",
   "keywords": [
     "dsh",