# SSH 插件验收记录

各次验收日期按小节列出，时区为 America/Los_Angeles。

## 2026-10-29 — jay.67: native remote Session actions and shortcut targets

The [release workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/40990490874) completed verify, npm OIDC publish and verify-installation successfully. All 128 files / 1,160 tests, typecheck, build, archive checks, four declared DSH runtime installations, offline downgrade with a real jay.39 consumer, installed incremental history/controller restart and SSH-disconnect acceptance passed. npm and the actual mainland mirror CDN serve the exact tested archive and advertise jay.67 as latest; all four package-name installations passed. macOS separately accepted the pinned npm version in DSH RC3 and matched its installed Host/client bytes.

The archive is 1,498,633 bytes, SHA-256 `8ba0bdca32a08f8e9788e5397c55f9d63bb0d554a37323b4e713d5111ab0527f`. The [GitHub Release](https://github.com/Biogod2020/dsh-ssh/releases/tag/v0.3.24-jay.67) carries the same CI archive and checksum. The independently built macOS archive is also byte-identical.

Generated loopback SSH and built-in-browser acceptance verified parent-window remote new/rename/fork/archive shortcuts, native message copying, archive restore and parked local draft preservation without a model request. Installed-SDK contract tests cover the Desktop keyboard/native-menu bridge; this is not a new native Desktop GUI acceptance claim. The temporary shortcut seam requires reviewed RC2/RC3 resolver implementations; see [the adapter boundary](native-session-adapter-2026-10-29.md).

jay.66 stopped before publication because its downgrade fixture's selective extraction omitted a shared helper already present in the archive. Local test attempts that expired during maintenance sleep were retained; the successful full run is reported above. No failed run is counted as a pass.

The additional macOS `@latest` test selected jay.42 under pnpm's new-package waiting policy even after the public tag had advanced. The pinned jay.67 installation passed; adding only an exact-version age exception in a generated profile made `@latest` select jay.67. User profiles and global policy were unchanged. Daily Web/Desktop services were not updated or restarted, and [PR #3](https://github.com/Biogod2020/dsh-ssh/pull/3) retains owner review.

Follow-up acceptance configured a persistent exception for only the package name `@biogod/dsh-ssh` in a fresh generated profile. Through the unmodified official Add plugin UI, typing only that bare name installed jay.67 from npm; its installed Host/client bytes match the release. This supports [one-time trust followed by package-name-only installation](install-latest-once.md). It does not claim zero-configuration first installation, automatic upgrade, or a global policy change.

## 2026-10-27 — local.2: restore the native Add workspace flow

In an isolated DSH 0.2.1-rc.3 Web instance using the official browse backend, Add workspace → Local folder failed with `directoryPicker.pick needs the native capability; the composed picker serves "browse"`. The SSH extension had replaced both official directory-flow occupants and called `uiWorkspace.pickDirectory()` directly. This also bypassed the Desktop occupant's own picker bridge.

The extension now projects the current original occupant, retaining its injected services, store, locale and child outlets, and renders that occupant when the user chooses Local folder. It follows late/replaced occupants and restores the original registrations on unload. Closing the flow resets the choice before a later open, avoiding an accidental extra native-picker launch.

Web acceptance exercised the sidebar and hero entries, created a generated `web-local-project` directory through the official browser, adopted it into the original sidebar, cancelled/reopened the browser and reopened the SSH flow without connecting a host. Regression tests cover both slots, browse outcomes, the Desktop picker bridge, busy state, cancellation/reopening and occupant replacement/unload. Tests use a private disposable home; the daily profile, real hosts, credentials and models are not involved in browser acceptance.

The verified local archive passed 106 suites / 968 tests, typecheck, build, artifact checks and isolated rc.3 installed-runtime acceptance. The private development workspace passed 78 suites / 693 tests, typecheck, build and artifact checks after the focused fix was applied. The archive was installed into the daily Desktop profile; installed host/client bundles match it. All 4,650 protected files, bundle order and other dependency specifications were preserved. Desktop restart is left to the user after saving work. No npm/GitHub publication was performed for this local revision.

## 2026-10-22 — jay.39: cursor-based disk history deltas

History validation now uses the actual Session event cursor rather than the list activity timestamp, which advances primarily on user messages and can miss assistant/tool events. Complete disk copies are reused: unchanged validation returns no events and does not read or rewrite the full local history document. New records are filtered on the remote machine and gzip/base64 encoded before SSH transport. This read-only helper uses the installer's existing Node and the running DSH's public projections/page APIs; it installs no remote plugin, changes no model settings, and does not restart the remote service.

New copies checkpoint forward prefixes every 500 events, including an fsync before atomic replacement. After a disconnected read or a controller restart, synchronization resumes strictly after the last saved cursor. Older suffix checkpoints retain their saved data and fill only the missing prefix before normal incremental checks. The same private v1 disk format, indefinite retention, selective clearing and cleanup reminders are preserved. A two-reader limit bounds concurrent background batches; running/quiet cached sessions allow checks every five/thirty seconds while the UI polls.

The generated-key SSH + DSH 0.2.1-rc.2 fixture saved 1,100 generated messages. History return payload was 16,255 bytes versus 336,889 bytes of uncompressed JSON; unchanged validation returned zero events in 109 bytes, and one new title event returned exactly one event in 257 bytes. Counts include gzip/base64 history framing but exclude SSH framing, outgoing helper source and unrelated UI traffic. They are not a WAN latency or whole-connection traffic benchmark. Native live chat still obtains its current state from the remote service.

Local regression covers interrupted batches across process restart, no-change disk IO avoidance, committed-data/index recovery, missing-file repair, equal list timestamps with new events, old-cache continuation, malformed/gapped/rewound cuts, bounded parallelism and clear/write races. `scripts/history-delta-smoke.mjs` separately exercises the final installed backend bundle with a real generated-key SSH server, disk reads after Host restart without reconnecting SSH, selective cleanup and the same remote DSH PID. The first jay.38 CI attempt exposed an existing wall-clock health-poll race in the terminal-continuity fixture. That fixture now drives repair explicitly, while retaining carrier replacement, same-shell-PID and once-only-write assertions; production repair behavior is unchanged. The unpublished jay.38 tag is retained as failed evidence. Publication and installed-package evidence are added after the jay.39 gates complete.

### jay.39 publication verified

- [Workflow 39780902969](https://github.com/Biogod2020/dsh-ssh/actions/runs/39780902969) completed verify, direct OIDC publish and verify-installation successfully for tag commit `d9ee27964b44ff0b5c57b6baefd3c4b315ee6cb9`. It passed all 74 suites / 672 tests, three-runtime archive acceptance, alpha.4 real-SSH verification, installed-bundle incremental history and disconnect fault injection, and package-name installs from npm and the mirror.
- The CI archive is 1,223,681 bytes, SHA-256 `0aa53cabb1714fbdee68946efa7394b9efabc079c1017de07ce0a5646c26b1ec`. The [GitHub Release](https://github.com/Biogod2020/dsh-ssh/releases/tag/v0.3.24-jay.39), official npm and actual `cdn.npmmirror.com` download match that artifact. All 87 packaged runtime source files match the tag.
- macOS independently installed `@biogod/dsh-ssh@0.3.24-jay.39` by name from npm into the shipped DSH 0.2.1-rc.2 runtime. Its backend/client bundles match the CI archive; disk persistence, selective cleanup/reminders, native settings and authenticated HTTP/WebSocket checks passed in an isolated home.

### jay.39 daily installation verified

Daily Desktop was fully exited and installed from npm with the exact dependency `0.3.24-jay.39`. Its backend/client bundles match the CI archive. Installation preserved 5,958 original data/configuration files and seven files from the other installed plugins; only package.json, pnpm-lock.yaml and the package manager's existing exact-version freshness exception changed. The policy edit was checked to add only jay.39.

Native delivery restored the original running remote conversation, first showing its saved disk history and then its native chat. Selecting the original local conversation and returning reused the same gateway origin without another opening placeholder. The existing remote daemon retained its PID; no prompt, terminal input, cancellation or remote restart was dispatched. The previous 1,431 saved events were preserved byte-for-byte as a prefix, and 436 missing events were added, yielding a complete 1,867-event disk copy (5,382,529 bytes; UI 5.1 MB). These are delivery checks, not a WAN latency benchmark.

## 2026-10-22 — jay.37: compressed cold loads over slow links

Native daily-profile verification after jay.36 exposed a separate initial-page load failure while the SSH carrier remained established. The gateway stripped Accept-Encoding from every request, forcing static scripts to travel uncompressed. Read-only remote sampling returned the same bootstrap script as 40,330 identity bytes versus 13,072 gzip bytes; this measures those bytes, not a general throughput benchmark.

Only the rewritten entry HTML now requests identity content. Other responses retain the original compressed bytes and matching headers. The native guest gives the initial page and remote-client bootstrap two minutes each, preserving cancellation, lease cleanup and no-replay semantics. Separate translated timeout messages distinguish page transport from client readiness. Focused tests exercise exact gzip-byte/header passthrough, identity HTML, one page navigation beyond the former 30-second deadline, and the same guest beyond the former 45-second client deadline.

Local verification passed all 73 suites / 658 tests, typecheck, build and archive checks; the private checkout passed the same 658 tests and typecheck. The exact archive passed isolated DSH `0.2.1-rc.2` acceptance. Daily Desktop installed that archive, preserved 5,957 original data/configuration files with only two SSH dependency metadata changes, and fully restarted after installation. Its installed backend/client bundles match the tested archive.

Native delivery verification reopened the original macbook conversation on its existing remote DSH `0.2.0-rc.2`; the conversation rendered in the same window and displayed its existing running task. Selecting the original local conversation and returning to the remote reused the same gateway origin and rendered conversation, without another opening placeholder. No message, terminal input, model setting or remote restart was sent for this verification. This is a concrete native-UI acceptance, not an extended outage or latency benchmark.

### jay.37 publication verified

- The [tagged workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/39772494386) completed verify, direct OIDC publish and verify-installation successfully. The release tag points to `b06642fd67d491dec70236740ad780ae90d7a963`. The full CI run passed all 658 tests, the exact archive in all three reviewed runtimes, the additional alpha.4 real-SSH suite, and installed-archive disconnect fault injection.
- npm and the mainland mirror both advertise jay.37 as latest. The exact official and `cdn.npmmirror.com` archives match the tested SHA-512. The public CI archive is 1,218,370 bytes; SHA-256 `4b782e2d078d7461c7bdc301f7241d9343a024fc80aca9146d2d2979112bf788`. The [GitHub Release](https://github.com/Biogod2020/dsh-ssh/releases/tag/v0.3.24-jay.37) carries that archive and checksum. All 86 packaged runtime source files match the release checkout.
- Package-name installation passed from npm into DSH alpha.4 and from the mirror into DSH 0.2.0-rc.2 and 0.2.1-rc.2. macOS independently installed by name from npm into the shipped 0.2.1-rc.2 runtime, including private disk-history persistence, selective cleanup/reminders, authenticated HTTP/WebSocket, settings and enable/disable checks.
- Daily Desktop was then promoted from its verified local tarball to the exact npm dependency `0.3.24-jay.37`. Its installed backend/client bundles match the CI archive byte-for-byte. Promotion preserved 5,958 existing data/configuration files; only package.json, pnpm-lock.yaml and the package manager's exact-version freshness exception changed. The workspace policy edit was verified to add only jay.37 to the existing SSH-package minimumReleaseAgeExclude entry; other plugins and policy fields were preserved.
- npm accepted the signed publication before exposing it publicly. Its [official status](https://status.npmjs.org/) reported degraded publish/install/view performance during this interval; the workflow waited for actual bytes and completed without republishing or weakening checks.

## 2026-10-22 — jay.36: preserve terminals through transient latency

The jay.34 and jay.35 gateway treated one two-second health timeout as a failed carrier. Replacing that carrier then closed every old socket, including an otherwise healthy terminal WebSocket; jay.35's HTTP request grace period did not cover upgraded streams. A local TCP/WebSocket fixture reproduced an abnormal close after a single 2.3-second health delay, with the remote service still healthy.

Health probes now allow five seconds and share one in-flight read per carrier. Automatic repair requires three consecutive failed recovery rounds unless the recorded SSH carrier is already broken or absent. Carrier replacement retains both pending WebSocket handshakes and open streams, including internal catalog/history observers; old carriers are released after their HTTP grace period and the final stream closes. At most two old carriers with active streams are retained, without evicting a live terminal to rotate again. Plugin shutdown releases all owned carriers.

Adding a project to an existing Host uses its actual workspace RPC instead of discarding the remote runtime on a failed health probe. A failed RPC remains a reported failure; no setup, write, command, terminal input or cancellation is automatically replayed. The remote daemon is not restarted by background carrier repair.

Focused regressions cover the original 2.3-second delay, coalesced reads, consecutive failure/reset behavior, same-WebSocket continuity after replacement, pending upgrades, catalog observers, retained-carrier limits, real disconnection with one input dispatch, shutdown and project reuse. The real generated-key SSH/DSH test also compares the PTY shell PID before and after replacement and checks a once-only command marker. Full archive, runtime and publication results are recorded after acceptance.

Local verification passed 73 suites / 655 tests, typecheck, build and archive checks. The exact archive passed isolated DSH `0.2.1-rc.2` acceptance and installed-archive SSH-disconnect fault injection. The private development checkout passed the same 655 tests and typecheck; its runtime sources match the public checkout apart from the existing package identity in `src/index.ts`.

Initial full runs exposed two fixture teardown races: cache-directory initialization completed after a receipt test started removing its root, and a real login shell saved `.zsh_history` during terminal-fixture cleanup. Teardown now waits for initialization and permits bounded asynchronous directory-removal retries. The affected 24 tests passed with these changes; failed initial runs are retained and are not counted as passing release checks.

The jay.36 [tagged workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/39769901055) completed verify, OIDC publish and verify-installation successfully, including all three reviewed runtimes and npm/mirror package-name installation. Daily Desktop installed the locally verified archive, restarted into the native interface, and preserved 5,957 original data/configuration files; only its two SSH dependency metadata files changed. Restoring the real remote conversation then exposed the cold-load issue described above; that UI step is not counted as a jay.36 end-to-end pass.

## 2026-10-22 — jay.35: 本机磁盘历史与会话切换

- [发行流水线](https://github.com/Biogod2020/dsh-ssh/actions/runs/39747401517) 的 verify、publish、verify-installation 全部成功。73 个测试文件、645 项测试，以及 typecheck、build、产物检查通过；最终归档通过三个 DSH 版本与 npm/镜像按包名安装验收。
- 已访问的远端会话历史写入本机私有磁盘目录，无自动过期规则。可按主机、项目、会话筛选清除，达到空间、数量或保留时间阈值时提示检查，可推迟提醒。清除不会改动远端会话，旧的后台读取不会把已清除副本重新写回。
- DSH `0.2.1-rc.2` 与生成密钥的真实 SSH 验证：1,100 条测试消息、1,104 条事件，补取两页历史后完整落盘。控制进程重启后无需 SSH 即可读取；选择清除保留其他副本与远端历史游标，明确打开可重新同步。
- 真实隔离桌面验证应用重启后从缓存管理入口阅读磁盘副本；关闭测试 SSH 服务后，统一侧栏中的会话仍在原聊天区域显示本机历史。图片、附件二进制仍由远端提供。
- 已加载的远端会话通过公开客户端导航切换，保留最近访问的客户端实例；本机磁盘副本的寿命独立于 RAM 保活。普通切换不再触发整轮列表刷新，已知副本按远端活动时间检查变化。
- 同一主机下十个项目连续两轮读取列表，真实 loopback SSH 的远端读取由 40 次降为 2 次；缓存过期后重新读取。该结果是请求数量，不作为公网连接延迟或吞吐基准。
- 修复连接通道替换时过早关闭旧通道导致取消响应丢失的问题；已派发请求完成或到达限定等待时间后才释放旧通道。真正断线仍报告结果不确定，命令、聊天、传输及取消请求均不自动重放。
- 测试使用独立 HOME、生成的 SSH 身份和生成消息，未读取用户模型凭据或使用生产 SSH 主机。

### jay.35 publication and installation verified

- The matching `v0.3.24-jay.35` tag points to release commit `0a00a9b3abbc47677438cf4779b318b3ac7b92c1`. The existing GitHub Actions trusted publisher published the tested archive directly through npm OIDC and signed provenance. Both npm and the mainland mirror advertise jay.35 as latest.
- The CI archive is 1,214,288 bytes; SHA-256 `21befec6f1e0dd20cb4cf8b0eda5ba06c3e26aad7b544d52e14f11b2ff2b89d0`. Its official download and actual `cdn.npmmirror.com` download match the tested SHA-512. Independent macOS downloads also matched this SHA-256, and all 86 packaged runtime source files match the release checkout. The [GitHub Release](https://github.com/Biogod2020/dsh-ssh/releases/tag/v0.3.24-jay.35) includes this exact CI archive and checksum.
- The exact archive passed isolated installation on DSH `0.2.0-rc.2`, `0.2.1-alpha.4` and `0.2.1-rc.2`. Package-name installation passed from npm into alpha.4 and from the mirror into both rc.2 versions. Each acceptance covered authenticated HTTP/WebSocket access, same-origin rejection, existing disk-history persistence, selective cleanup, reminder snoozing, native settings and enable/disable.
- macOS independently installed the published package by name from npm into the shipped DSH `0.2.1-rc.2` runtime and passed the same checks. The retained alpha.4 real-SSH suite also passed all five tests. Installed-archive SSH fault injection confirmed that the DSH host and an independent tunnel survive stale forwarding failures, without reconnecting or replaying an operation.
- This publication did not reinstall or restart the daily Desktop profile. Its existing configuration, sessions and plugin installation were preserved.

## 0.3.24-jay.26：认证与密码保存

- npm 已发布，`latest` 指向该版本；官方源和国内镜像的归档 SHA-256 均为 `8238e7731350f469171424c5e684eca2323a62f627006c009a367e84ba386f56`。
- 按 npm 包名从官方源安装到 DSH alpha.4、从国内镜像安装到 DSH rc.2，均通过隔离运行验收。
- 2026-10-16 实际 macOS 桌面版 rc.2 通过插件页从国内镜像安装并启用 `.26`，组件状态为 Running；原主机配置字节未变，其他插件依赖保持不变。
- 补充升级检查：rc.2 在同一进程中 remove/install/enable 均报告 applied，但仍运行 .25 的后端，PATCH 回退密码时报 `auth.keyPath is required for key auth`。隔离环境完全重启后，新能力字段出现，同一 PATCH 返回 200 并保留私钥路径。安装版本和组件 Running 状态不能单独证明后端已换新；.25 → .26 的桌面迁移需要完全重启。
- 61 个测试文件 / 576 项测试、typecheck、build、产物检查通过。
- 生成的 loopback SSH 身份验证覆盖密钥优先、拒绝或无法读取密钥后的密码回退、不可用 Agent 回退、未知主机密钥拒绝、单次派发后连接断开不重放。
- 键盘交互覆盖空 PAM 提示、账号密码和一次性密码分离。不会把保存的账号密码填入标识为 OTP / verification / one-time password 的提示。
- 存储检查覆盖仅内存、记住密码、取消记住、清除、凭据不返回主机列表、切换账号或地址时不沿用内存密码；私有配置保持 0600。
- DSH `0.2.0-rc.2`、`0.2.1-alpha.4` 均在新建私有 HOME 中安装最终 tarball，通过 HTTP / WebSocket 认证、同源检查、原生设置和插件启停验收。
- 浏览器使用生成的 loopback SSH 测试主机，验证保存回退密码后测试连接成功。工作区新增认证编辑入口，并在打开子弹窗时移动焦点和隐藏父弹窗的辅助功能节点。
- 未为这些测试调用模型 API；生产服务器的密码与 OTP 组合仍由服务器策略决定。

## 0.3.24-jay.25：npm 分发验收

- 公开包名为 `@biogod/dsh-ssh@0.3.24-jay.25`，`latest` 指向该版本。原 GitHub Release 与标签保持不变。
- 本次重新执行 typecheck、58 个测试文件 / 543 项测试、构建和产物检查，全部通过；修复测试用 sshd 日志流过早关闭导致的 write-after-end 时序问题。
- npm 官方源与中国大陆镜像的版本和归档完整性一致。发行归档 SHA-256：`5188d48a8119d2b38778bb25bfb0078ba2f0d5b4b7e1d371b2599da84b6ea355`。
- DSH `0.2.1-alpha.4`（npm 官方源）与 `0.2.0-rc.2`（显式国内镜像源）均在全新独立 HOME 中按包名安装并通过 runtime smoke、原生设置和启停检查。
- 实际 alpha.4 Web 插件页填写公开包名、选择中国大陆镜像，完成安装和启用，侧栏出现 SSH，面板正常打开。另通过同一运行实例的 HTTP / WebSocket 认证、同源限制、主机管理和失败连接检查。
- 旧包卸载后安装公开包的隔离迁移检查通过：主机配置字节保持一致，新运行实例能读出原主机，未派发 SSH 连接。
- 未修改日常 DSH profile，未使用真实主机、凭据或模型请求。

## 既有功能验收

- typecheck、58 个测试文件 / 543 项测试、构建和产物检查通过。
- DSH `0.2.0-rc.2` 与 `0.2.1-alpha.4` 的全新私有 HOME 实际安装通过，覆盖 HTTP / WebSocket 认证、同源限制、客户端清单、主机管理、失败连接、原生设置和开关。
- alpha.4 的本地链接替换为预构建 tarball 通过，无需先卸载或放开原生构建脚本。
- 5 项真实 loopback SSH + alpha.4 远端运行时集成通过，覆盖直接文件操作插件、工作区 / 会话 / 终端 RPC、事件流、隧道恢复、daemon 不重启、已派发准备不重放及主机身份冻结。
- 实际 alpha.4 浏览器检查了原生 SSH 入口、展开与折叠侧栏、终端经 Plugins 页面往返后保持同一 shell。定向测试还覆盖草稿保留和运行中集群观察不取消、不重发。
- 一次性真实 SSH 环境完成 Node 和固定 DSH 的冷安装、下载校验、依赖安装、启动及经过认证的远端完整界面打开。
- 安装包仅携带 ssh2 的必需纯 JS 依赖，不携带可选 `.node` 模块；包路径和依赖闭包均检查。测试使用生成的 SSH 密钥和私有信任文件。

既有 jsdom canvas 和部分 SDK 缺失 sourcemap 的诊断不影响上述通过结果；没有将它们宣称为已修复。

本轮没有重新全面验收生产 PAM / OTP、多 GiB 压力、所有终端协议、Windows 或 Linux 冷安装，也没有调用模型 API。历史支持不等于本轮在所有平台重跑。真实用户配置与日常进程不用于测试。

复验方式见 README 和 `scripts/compatibility-smoke.mjs`、`scripts/remote-browser-smoke.ts`。服务日志可能含临时认证信息，不应上传或分享。


## 2026-10-16 — jay.27: explicit SSH host selection

- Import now previews local `~/.ssh/config` candidates with every checkbox initially empty. Only selected aliases are saved; existing hosts are preserved. GET preview is read-only and excludes credentials, key paths and ProxyCommand text; POST rejects a missing selection. No key checks, proxy commands or SSH connections run during preview.
- Add workspace starts with an empty host choice. Selecting a host, editing the path, saving authentication and importing hosts do not browse or connect. The Browse button explicitly requests remote directories; changing host/path closes browsing and discards stale results. Connect and add remains an explicit action.
- Release snapshot passed typecheck, all 61 suites / 582 tests, build and artifact checks. Verified prebuilt archive SHA-256: `b975f1201963d80e02e3b18881fbc05c9483ddf5fbb695ef202b59ebfe497664`. Isolated runtimes passed on DSH 0.2.0-rc.2 and 0.2.1-alpha.4.
- Isolated browser acceptance used generated loopback SSH identities. Importing only `dev-two` saved only that candidate; opening, importing and choosing it produced zero SSH connections and zero commands. Explicit Browse produced exactly one connection and zero commands. UI screenshot and private evidence: `/Users/jay/scratch/dsh-ssh-selection-release-20261016/`.
- Desktop rc.2 installed the verified .27 tarball through the plugin GUI and was fully quit/reopened. Other plugin dependencies and the private host store were preserved. npm .27 is staged pending the account holder's publication authentication; registry/mirror acceptance will be recorded after approval.


### Automatic publisher bootstrap

GitHub Actions preflight run `38876888021` passed all 61 suites / 582 tests, artifact checks and both DSH runtime acceptances on Ubuntu. The package owner completed the one-time GitHub trusted publisher binding for `Biogod2020/dsh-ssh`, `publish.yml`, with direct publish permission. Tagged run `38877111308` authenticated and signed npm provenance, then npm rejected .27 with E409 because a previously staged version reserves that version number. That pending stage is left unchanged. The same SSH behavior is released as .28 to validate direct OIDC publication without another maintainer approval.


### jay.28 automatic release verified

- Tagged workflow [38877659704](https://github.com/Biogod2020/dsh-ssh/actions/runs/38877659704) completed successfully: full verification, direct OIDC npm publication, and registry/mirror installation acceptance. No per-release maintainer approval was used. npm provenance is present.
- Published archive: 1,119,367 bytes; SHA-256 `be6b267eaf3d41aba7d71282c78b8ae12ac2a2d4d1dabb16605fab7ed8bad0ca`. npm and the actual `cdn.npmmirror.com` archive both matched the tested archive's SHA-512.
- macOS independently installed `@biogod/dsh-ssh@0.3.24-jay.28` by package name from npm into DSH 0.2.1-alpha.4, and from the mainland mirror into DSH 0.2.0-rc.2; authenticated runtime and native settings/enable checks passed.
- Daily Desktop already runs the .27 acceptance package with the same SSH implementation. It was not replaced again after the machine locked; .28 is the formal npm release. Existing host configuration remains byte-identical to the pre-update backup.


## 2026-10-16 — jay.29: remote workspaces inside Desktop

- Replaced Desktop top-level loopback navigation with the shipped `dshDesktop.browser` guest lease interface. The parent stays on `dsh-app://app/`; Return to local retains the owned guest and its draft, and reopening reuses that guest. Closing a view confirms draft loss and leaves remote services running. No automatic external-browser fallback is used. Browser deployments retain in-tab navigation.
- Gateway tickets, Strict/HttpOnly cookies, SSH host-key verification and no-replay rules remain in force. The embedded view mode only hides duplicate local/recovery links; it does not grant authentication. Desktop guests have no local Node/preload/Host privileges, and native page downloads follow the Desktop browser restriction. Local SSH transfer tools remain available.
- Typecheck, all 62 suites / 588 tests, build and artifact checks passed. Real-SSH tests verified the embedded ticket still requires authentication and retains Strict cookies.
- Actual Desktop rc.2 acceptance used a separate HOME/DSH_HOME, a private port and a generated loopback SSH identity; no user SSH host or model credential was used. The remote DSH rendered in the same application window. Returning to local and reopening preserved the exact unsent fixture draft and gateway origin. Evidence: `/Users/jay/scratch/dsh-ssh-desktop-release-20261016/native-verification.json` and `in-app-workspace.png`.


### jay.29 deployment and publication

Daily Desktop rc.2 installed the verified .29 local archive through its plugin GUI, enabled it and was fully quit/reopened. Both installed client/backend files matched the verified archive; the SSH host store remained byte-identical and 0600, and other plugin dependencies were preserved. User workspaces and model configuration were retained; no real SSH target was used for acceptance.

The OIDC [release workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/38886410320) completed all three jobs successfully. The published CI archive (1,131,337 bytes) and its actual mainland mirror CDN download matched the tested SHA-512. Official/mirror package-name installation passed in isolated DSH alpha.4/rc.2 runtimes. The registry check now reads the canonical package document to avoid stale negative caches on newly published version URLs.


## 2026-10-21 — jay.33: native unified project and session navigation

- Local and remote projects/conversations now share the native sidebar. Presentation-only synthetic IDs never enter local Controllers; local callbacks remain intact and remote actions route to their recorded Host. New Session follows the visible project. Legacy local SSH history remains readable and guarded.
- One isolated Desktop guest is retained per Host. Session switching uses the public remote navigation service, preserving per-session drafts without replacing the document. The first server-manifest synchronization cannot remove the page-local navigation bridge. Embedded views hide the duplicate sidebar and toolbar; the local blank draft remains addressable.
- The SSH workspace host picker supports bounded search, keyboard selection and successful-connection recency. Search, selection and cached session display do not connect SSH. Disconnected catalog entries remain explicitly stale; prompt/command/session creation is never replayed.
- The public release source passed typecheck, all 68 suites / 615 tests, build and archive checks on macOS with DSH 0.2.1-rc.2 as the real-SSH fixture runtime. Runtime source matches the locally installed, native-UI-verified jay.32-local.1 candidate byte-for-byte. Its isolated Desktop acceptance covered local/remote session and draft round trips, New Session routing, remote Files ownership, and alpha.4 navigation after the first manifest sync. No model request was used.
- The existing local installation retained 360 protected data/configuration files byte-for-byte; only the two expected Desktop dependency files changed. Production SSH hosts were not used as test targets.
- The release workflow also requires exact-archive acceptance on DSH 0.2.0-rc.2, 0.2.1-alpha.4 and 0.2.1-rc.2, an additional alpha.4 real-SSH test, then npm/mirror integrity and by-name installation checks. Publication results are recorded after these gates complete.
- Remote model relay and local-Agent/remote-executor modes remain documented design options, not enabled features. Independent remote DSH processes continue after local gateway/controller shutdown subject to the remote process and network environment.

The jay.32 tagged run stopped before npm publication: its additional alpha.4 test assumed the root DSH version determined the terminal protocol. A clean alpha.4 installation can resolve a newer terminal-controller dependency with the duplex attach endpoint. The integration fixture now negotiates only the read-only attachment, falling back on explicit endpoint absence, before sending exactly one terminal write. This changes test compatibility, not the generic production gateway. The failed jay.32 tag is retained; jay.33 is the next release candidate.


### jay.33 registry and macOS installation acceptance

- GitHub Actions OIDC accepted the release and signed npm provenance. npm processing delayed public visibility; the official registry and the actual mainland mirror CDN subsequently served the same tested archive: 1,177,983 bytes, SHA-256 `01f3ee02bad6682213ba2663f47cbe30b1f371c3ff0a28b9a5e454693058d030`.
- macOS independently installed `@biogod/dsh-ssh@0.3.24-jay.33` by package name from npm into DSH 0.2.1-rc.2 and from the mirror into DSH 0.2.1-alpha.4. Both authenticated runtime, native settings and enable/disable checks passed in isolated homes. The daily Desktop configuration and sessions were not changed for publication.
- The mirror initially cached the previous package index. The verifier now waits for the official archive before requesting synchronization and uses the mirror-supported cache refresh parameters. A delayed-publication fixture verified that synchronization never precedes official archive acceptance, and the corrected verifier checked the actual npm and `cdn.npmmirror.com` downloads. This only changes future release checks; the published runtime sources are unchanged.

The [tagged release workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/39607583854) completed all three jobs successfully: verify, publish and verify-installation. The exact archive and the three by-name installation acceptances passed on Ubuntu without another publication or a workflow rerun. Both registries advertise jay.33 as latest and expose the signed provenance.


## 2026-10-21 — jay.34: contain disconnected SSH forwarding failures

The installed jay.32-local.1 archive and the public jay.33 archive allow ssh2 forwardOut to throw from the local TCP accept callback after SSH disconnects. The exception escapes the plugin and terminates the DSH host. A separate process reproduced the same Not connected crash without connecting a production host. The isolated installed-archive fault fixture also reproduced it with jay.33 after a real SSH disconnect.

The tunnel now handles local socket errors before opening a channel, contains synchronous forwardOut errors, and releases channels returned after their local socket has closed. Failures only close the affected pair; the listener, other connections and remote processes keep their existing ownership. No reconnect or request replay is added. Four child-process regressions cover public/workspace stale connections, early socket errors with a late channel, and asynchronous rejection. The original code fails three of the four checks; the corrected code passes all four and the existing engine/tunnel tests.

The release workflow now installs the exact archive into an isolated DSH process, disconnects one generated SSH fixture, sends three requests to the stale forward, and requires the DSH HTTP API and an independent tunnel to remain healthy. It also requires no new SSH connection, no dispatched command and no model request.

Local release verification passed all 69 suites / 619 tests, typecheck, build and artifact checks. The exact jay.34 archive passed DSH 0.2.1-rc.2 isolated compatibility and the installed-archive SSH-disconnect test: the process and independent tunnel remained available after three rejected forwards, with no reconnect, command or model request. The archive installed into the daily Desktop profile matched both tested client/backend bundles byte-for-byte; 6,006 protected files remained byte-identical and only the two expected dependency files changed. The article plugin and all other dependency declarations were preserved.


### jay.34 publication verified

The [tagged release workflow](https://github.com/Biogod2020/dsh-ssh/actions/runs/39698581172) completed verify, OIDC publish and verify-installation successfully. This includes the installed-archive fault injection, three reviewed DSH runtimes, and package-name installation from npm and the mainland mirror. macOS also installed the public package by name into the shipped DSH 0.2.1-rc.2 runtime and passed authenticated runtime/settings checks.

Both latest tags point to jay.34. The published CI archive is 1,178,187 bytes; SHA-256 `eea7ac0b5d0eed3ac0dea65c4fd1cbb5c61bf65b26f11ad2a81de88704d786f7`. Its official and actual `cdn.npmmirror.com` downloads match the tested SHA-512. Its 83 runtime source files match the release commit and the locally tested fix. The local installation uses the macOS acceptance build of the same version/source, with its own frozen archive hash `7bac8b5fb31f44bcef705e56dc23bb5bd1cb6d6a0190e6591657d13307ca9cd6`.

The daily Desktop was fully exited before installation and restarted into its normal native interface. The corrected backend remains alive with no new crash report observed after restart. Original projects and session history remain visible; only SSH dependency metadata changed during installation. No production SSH host or model request was used for tests.

## 2026-10-21 — documentation and real onboarding walkthrough

The README now leads with the unified local/remote sidebar, separates Desktop GUI installation from Web-profile CLI commands, and provides a linear first-use path. Four unmodified native-window screenshots show only disposable demo projects. The [walkthrough](onboarding.md) includes the exact remote model-settings entry and [machine-readable acceptance](onboarding-acceptance.json) records archive and screenshot hashes.

Actual macOS Desktop acceptance used the already published jay.34 CI archive with local and remote DSH 0.2.1-rc.2. Focusing the remote composer and pressing Command+Option+Comma opened the remote Settings; Command+Comma opened local Settings. Remote Models successfully created a custom Chat Completions provider, discovered its model, selected it and displayed an explicitly simulated reply. The local mock observed one chat-completions request. The provider was present only in the remote profile. Add workspace → SSH workspace also created a new project through the real GUI; local and remote drafts survived round trips.

The model response is a fixture, not a real-model quality or speed benchmark. The default remote installation pin remains alpha.4; this UI walkthrough does not claim a new Windows or all-version GUI acceptance.

Runtime source, package version and dependencies are unchanged. The full verification was rerun: 69 suites / 619 tests, typecheck, build and artifact checks passed. An initial full run missed the terminal-start marker deadline in one real-SSH test; without changing code or test conditions, its five-test suite passed independently and the subsequent full run passed all 619 tests. The initial failed result is not counted as a pass.

The published jay.34 archive also passed a fresh isolated DSH 0.2.1-rc.2 runtime acceptance, including authenticated HTTP/WebSocket access, same-origin rejection, native settings, and enable/disable. Markdown references and all four screenshot hashes were checked before the documentation push.