dsh-remote-vs 0.8.5 → 0.8.6

package/lib/client.js

@@ -823,7 +823,7 @@ window.__ModuleLoader__.load({
 								onKeyDown: (e) => {
 									if (e.key === "Enter") go();
 								},
-								placeholder: "/home/xiray/project",
+								placeholder: "/home/user/project",
 								spellCheck: false,
 								style: {
 									flex: 1,
@@ -37978,7 +37978,7 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 					const primary = host.querySelectorAll("[class*=\"rvs-ck-\"]").length;
 					const fallback = host.querySelectorAll("span[class^=\"rvs-t-\"]").length;
 					const count = primary > 0 ? primary : fallback;
-					console.info(`[dsh-remote-vs] build 1022-1539 · ${source} · colored tokens: ${count} (${propsRef.current.path})`);
+					console.info(`[dsh-remote-vs] build 1022-1607 · ${source} · colored tokens: ${count} (${propsRef.current.path})`);
 					propsRef.current.onTokens?.(count);
 				};
 				const armFallback = () => {
@@ -40390,7 +40390,7 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 		* path decides between the bindings on it.
 		*
 		* One alias routinely carries SEVERAL bindings (the same host mounted at
-		* `/home/xiray/P710/…` and `/home/xiray/Z700/…`), so an alias-only match hands
+		* `/srv/one/…` and `/srv/two/…`), so an alias-only match hands
 		* back whichever was created first: the editor then opens the file the caller
 		* named while the sidebar, the tree and the workspace selector stay on the
 		* other workspace. The remote root the caller already holds (`summary.root`, a
@@ -40565,8 +40565,8 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 		* `bindingForWorkspacePath` answers only for the workspace path ITSELF (exact
 		* alias-dir match). A session cwd is weaker evidence: the model cd'ed into a
 		* project sub-directory, and the host commits whichever spelling the session
-		* ran in — the local alias (`C:\…\aliases\p710bb\src`) or the REMOTE path
-		* (`/home/xiray/P710/master/userdebug/P710/src`). Both are still inside exactly
+		* ran in — the local alias dir (`C:\…\aliases\<alias>\src`) or the REMOTE
+		* path (`/srv/one/src`). Both are still inside exactly
 		* one binding, so the deepest containing alias dir / remote root decides.
 		*
 		* No fallback to "the first binding": a cwd that names no known binding answers
@@ -41204,7 +41204,7 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 		* workspace showed the sidebar on another — the selector kept whatever
 		* localStorage held (or the FIRST binding, on a fresh profile), and a click in
 		* the change panel matched its binding by alias alone, which is ambiguous as
-		* soon as one host carries two workspaces (P710 and Z700 share `ssh_xiray_new`).
+		* soon as one host carries two workspaces under one alias).
 		*
 		* Resolution order, strongest evidence first (all of it inside
 		* `planWorkspaceFollow`, so the policy has exactly one home):
@@ -43071,8 +43071,8 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 						}),
 						/* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
 							className: "rvs-build",
-							title: `dsh-remote-vs build 1022-1539`,
-							children: "1022-1539"
+							title: `dsh-remote-vs build 1022-1607`,
+							children: "1022-1607"
 						}),
 						tokenCount !== void 0 && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", {
 							className: "rvs-build",
@@ -60933,7 +60933,7 @@ Integer Float Double Long Int32 Int64 Uint8 uint32_t int32_t uint64_t int64_t si
 			* Without this the panel opened on whatever localStorage held — and on a
 			* fresh profile on `workspaces[0]` — so a session working in one remote
 			* workspace showed another workspace's tree until the user corrected it by
-			* hand (the reported bug: a P710 session browsing Z700). The host's own
+			* hand (the reported bug: a session browsing another workspace on one host). The host's own
 			* workspace membership for the on-screen session is the only sanctioned
 			* source (`useRemoteChatTarget`), and it is a soft read: while it answers
 			* nothing the current selection stands.

package/lib/index.js

@@ -1,4 +1,4 @@
-import { a as pushPipeline, c as require_lib, d as ensurePrivateDir, f as keysDir, i as probe, l as aliasRoot, o as seedHelperCache, p as storePath, r as helperAvailability, s as RemoteFiles, t as RemoteWorlds, u as dshHome } from "./worlds-PUumRIh7.js";
+import { a as pushPipeline, c as require_lib, d as ensurePrivateDir, f as keysDir, i as probe, l as aliasRoot, o as seedHelperCache, p as storePath, r as helperAvailability, s as RemoteFiles, t as RemoteWorlds, u as dshHome } from "./worlds-C6W225o9.js";
 import z from "@deepseek-ai/schemastery";
 import { chmodSync, closeSync, existsSync, mkdirSync, openSync, readFileSync, renameSync, statSync, writeSync } from "node:fs";
 import { createHash, randomUUID } from "node:crypto";
@@ -2529,8 +2529,8 @@ function readHeadCommand(root, paths, capBytes, totalCapBytes) {
 /**
 * Name every immediate subdirectory that is a git repository.
 *
-* A session working directory is often a CONTAINER for repositories (the
-* reference host has `/home/xiray/dsh_workbase` holding `emv-toolbox-web`), and
+* A session working directory is often a CONTAINER for repositories (a root
+* that holds another repository inside it), and
 * `git status` at the container answers 128. This is a one-level `ls`-style
 * probe — bounded work, no `find` — so it can never become the expensive part
 * of a scan.
@@ -3357,8 +3357,8 @@ var SessionChanges = class {
 	* index (1.4s measured on the reference monorepo).
 	*
 	* A session working directory is often a CONTAINER for repositories rather
-	* than one itself (the reference host has `/home/xiray/dsh_workbase` holding
-	* `emv-toolbox-web`), and `git status` there answers exit 128 — "not a git
+	* than one itself (a session root that holds another repository inside it),
+	* and `git status` there answers exit 128 — "not a git
 	* repository (or any parent up to mount point /)". When that happens the
 	* ledger looks one level down once and adopts the repository it finds, which
 	* is the same idea the SCM panel's `repoSubdir` expresses by hand.

package/lib/p2-router-fs.js

@@ -1,4 +1,4 @@
-import { l as aliasRoot, n as isWindowsAbsolute } from "./worlds-PUumRIh7.js";
+import { l as aliasRoot, n as isWindowsAbsolute } from "./worlds-C6W225o9.js";
 import { FileSystem, FsError } from "@deepseek-ai/dsh-fs";
 //#region src/p2/router-fs.ts
 /**

package/lib/types/changes/recorder.d.ts

@@ -148,8 +148,8 @@ export declare class SessionChanges {
      * index (1.4s measured on the reference monorepo).
      *
      * A session working directory is often a CONTAINER for repositories rather
-     * than one itself (the reference host has `/home/xiray/dsh_workbase` holding
-     * `emv-toolbox-web`), and `git status` there answers exit 128 — "not a git
+     * than one itself (a session root that holds another repository inside it),
+     * and `git status` there answers exit 128 — "not a git
      * repository (or any parent up to mount point /)". When that happens the
      * ledger looks one level down once and adopts the repository it finds, which
      * is the same idea the SCM panel's `repoSubdir` expresses by hand.

package/lib/types/changes/status.d.ts

@@ -175,8 +175,8 @@ export declare function readHeadCommand(root: string, paths: readonly string[],
 /**
  * Name every immediate subdirectory that is a git repository.
  *
- * A session working directory is often a CONTAINER for repositories (the
- * reference host has `/home/xiray/dsh_workbase` holding `emv-toolbox-web`), and
+ * A session working directory is often a CONTAINER for repositories (a root
+ * that holds another repository inside it), and
  * `git status` at the container answers 128. This is a one-level `ls`-style
  * probe — bounded work, no `find` — so it can never become the expensive part
  * of a scan.

package/lib/types/client/remote-file-open-target.d.ts

@@ -6,7 +6,7 @@
  * opens it through its own right-sidebar preview. That preview resolves the
  * address path against the SESSION WORKSPACE ROOT. A model that quotes a path
  * relative to its CURRENT directory (e.g. `_xfer/reports/x.md` while working
- * in `…/dsh_workbase/emv-toolbox-web`) therefore misses by one segment, and a
+ * in `<workspace>/<inner-repo>`) therefore misses by one segment, and a
  * remote session's workspace root only exists as an EMPTY local alias dir —
  * the click dies with the host-side ENOENT the user sees.
  *
@@ -67,7 +67,7 @@ export declare function bindingForWorkspacePath(table: RemoteOpenBindings, works
  * path decides between the bindings on it.
  *
  * One alias routinely carries SEVERAL bindings (the same host mounted at
- * `/home/xiray/P710/…` and `/home/xiray/Z700/…`), so an alias-only match hands
+ * `/srv/one/…` and `/srv/two/…`), so an alias-only match hands
  * back whichever was created first: the editor then opens the file the caller
  * named while the sidebar, the tree and the workspace selector stay on the
  * other workspace. The remote root the caller already holds (`summary.root`, a
@@ -199,8 +199,8 @@ export declare function selectionIsSessionBinding(options: {
  * `bindingForWorkspacePath` answers only for the workspace path ITSELF (exact
  * alias-dir match). A session cwd is weaker evidence: the model cd'ed into a
  * project sub-directory, and the host commits whichever spelling the session
- * ran in — the local alias (`C:\…\aliases\p710bb\src`) or the REMOTE path
- * (`/home/xiray/P710/master/userdebug/P710/src`). Both are still inside exactly
+ * ran in — the local alias dir (`C:\…\aliases\<alias>\src`) or the REMOTE
+ * path (`/srv/one/src`). Both are still inside exactly
  * one binding, so the deepest containing alias dir / remote root decides.
  *
  * No fallback to "the first binding": a cwd that names no known binding answers

package/lib/types/client/store.d.ts

@@ -222,7 +222,7 @@ export declare function setFollowSession(sessionId: string | undefined): void;
  * workspace showed the sidebar on another — the selector kept whatever
  * localStorage held (or the FIRST binding, on a fresh profile), and a click in
  * the change panel matched its binding by alias alone, which is ambiguous as
- * soon as one host carries two workspaces (P710 and Z700 share `ssh_xiray_new`).
+ * soon as one host carries two workspaces under one alias).
  *
  * Resolution order, strongest evidence first (all of it inside
  * `planWorkspaceFollow`, so the policy has exactly one home):

package/lib/types/p2/worlds.d.ts

@@ -103,7 +103,7 @@ export declare class RemoteWorlds {
      * service canonicalizes through it), and the remote fs view answers the remote
      * absolute path. That is the right spelling for display and for remote
      * processes, but it is not always a spelling the router can route BACK: two
-     * bindings may share one remote root (`mlxy:/home` + `xjp-xiray:/home`), and
+     * bindings may share one remote root (two aliases both mounted at `/home`), and
      * `/home` is then deliberately ambiguous and resolves local. A spawned child
      * session inherits exactly that committed spelling — so every subagent of a
      * remote session in one of those workspaces silently ran on the Host (and a

package/lib/{worlds-PUumRIh7.js → worlds-C6W225o9.js}

@@ -18432,7 +18432,7 @@ var RemoteWorlds = class {
 	* service canonicalizes through it), and the remote fs view answers the remote
 	* absolute path. That is the right spelling for display and for remote
 	* processes, but it is not always a spelling the router can route BACK: two
-	* bindings may share one remote root (`mlxy:/home` + `xjp-xiray:/home`), and
+	* bindings may share one remote root (two aliases both mounted at `/home`), and
 	* `/home` is then deliberately ambiguous and resolves local. A spawned child
 	* session inherits exactly that committed spelling — so every subagent of a
 	* remote session in one of those workspaces silently ran on the Host (and a

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-remote-vs",
   "description": "VSCode-style remote development for DSH: SSH host manager (key/password), helper deploy pipeline with version check, remote file explorer + editor + terminal in dsh-better-sidebar.",
-  "version": "0.8.5",
+  "version": "0.8.6",
   "icon": "icon.svg",
   "keywords": [
     "dsh",

package/src/changes/recorder.ts

@@ -600,8 +600,8 @@ export class SessionChanges {
    * index (1.4s measured on the reference monorepo).
    *
    * A session working directory is often a CONTAINER for repositories rather
-   * than one itself (the reference host has `/home/xiray/dsh_workbase` holding
-   * `emv-toolbox-web`), and `git status` there answers exit 128 — "not a git
+   * than one itself (a session root that holds another repository inside it),
+   * and `git status` there answers exit 128 — "not a git
    * repository (or any parent up to mount point /)". When that happens the
    * ledger looks one level down once and adopts the repository it finds, which
    * is the same idea the SCM panel's `repoSubdir` expresses by hand.

package/src/changes/status.ts

@@ -367,8 +367,8 @@ export function readHeadCommand(
 /**
  * Name every immediate subdirectory that is a git repository.
  *
- * A session working directory is often a CONTAINER for repositories (the
- * reference host has `/home/xiray/dsh_workbase` holding `emv-toolbox-web`), and
+ * A session working directory is often a CONTAINER for repositories (a root
+ * that holds another repository inside it), and
  * `git status` at the container answers 128. This is a one-level `ls`-style
  * probe — bounded work, no `find` — so it can never become the expensive part
  * of a scan.

package/src/client/RemoteDirectoryPicker.tsx

@@ -108,7 +108,7 @@ export function RemoteDirectoryPicker(props: {
             onKeyDown={(e) => {
               if (e.key === 'Enter') go()
             }}
-            placeholder="/home/xiray/project"
+            placeholder="/home/user/project"
             spellCheck={false}
             style={{ flex: 1, background: 'rgba(127,127,127,.12)', color: 'inherit', border: '1px solid rgba(127,127,127,.35)', borderRadius: 6, padding: '4px 8px', fontSize: 13, fontFamily: 'inherit', outline: 'none' }}
           />

package/src/client/RemoteRoot.tsx

@@ -133,7 +133,7 @@ function Shell(props: { ctx: Context; visible: boolean }): ReactNode {
    * Without this the panel opened on whatever localStorage held — and on a
    * fresh profile on `workspaces[0]` — so a session working in one remote
    * workspace showed another workspace's tree until the user corrected it by
-   * hand (the reported bug: a P710 session browsing Z700). The host's own
+   * hand (the reported bug: a session browsing another workspace on one host). The host's own
    * workspace membership for the on-screen session is the only sanctioned
    * source (`useRemoteChatTarget`), and it is a soft read: while it answers
    * nothing the current selection stands.

package/src/client/changes/ChangesDock.tsx

@@ -234,8 +234,8 @@ export function ChangesDock(props: ChangesDockProps): React.ReactNode {
       // sees what the load wrote.
       //
       // Resolved by the session's REMOTE root, never by the alias alone: one
-      // alias carries several bindings (P710 and Z700 both live on
-      // `ssh_xiray_new`), and the alias-only form picked whichever came first —
+      // alias carries several bindings (two workspaces can live on one alias),
+      // and the alias-only form picked whichever came first —
       // the file opened while the tree and the selector stayed on the other
       // workspace. That was the reported bug.
       let binding = bindingForChangedFile(remoteOpenBindings(), summary, file.path)

package/src/client/remote-file-open-target.ts

@@ -6,7 +6,7 @@
  * opens it through its own right-sidebar preview. That preview resolves the
  * address path against the SESSION WORKSPACE ROOT. A model that quotes a path
  * relative to its CURRENT directory (e.g. `_xfer/reports/x.md` while working
- * in `…/dsh_workbase/emv-toolbox-web`) therefore misses by one segment, and a
+ * in `<workspace>/<inner-repo>`) therefore misses by one segment, and a
  * remote session's workspace root only exists as an EMPTY local alias dir —
  * the click dies with the host-side ENOENT the user sees.
  *
@@ -181,7 +181,7 @@ function isRemoteAbsolute(path: string | undefined): path is string {
  * path decides between the bindings on it.
  *
  * One alias routinely carries SEVERAL bindings (the same host mounted at
- * `/home/xiray/P710/…` and `/home/xiray/Z700/…`), so an alias-only match hands
+ * `/srv/one/…` and `/srv/two/…`), so an alias-only match hands
  * back whichever was created first: the editor then opens the file the caller
  * named while the sidebar, the tree and the workspace selector stay on the
  * other workspace. The remote root the caller already holds (`summary.root`, a
@@ -396,8 +396,8 @@ function bindingForHostPath(
  * `bindingForWorkspacePath` answers only for the workspace path ITSELF (exact
  * alias-dir match). A session cwd is weaker evidence: the model cd'ed into a
  * project sub-directory, and the host commits whichever spelling the session
- * ran in — the local alias (`C:\…\aliases\p710bb\src`) or the REMOTE path
- * (`/home/xiray/P710/master/userdebug/P710/src`). Both are still inside exactly
+ * ran in — the local alias dir (`C:\…\aliases\<alias>\src`) or the REMOTE
+ * path (`/srv/one/src`). Both are still inside exactly
  * one binding, so the deepest containing alias dir / remote root decides.
  *
  * No fallback to "the first binding": a cwd that names no known binding answers

package/src/client/store.tsx

@@ -761,7 +761,7 @@ let followFlight: { sessionId: string; promise: Promise<string | undefined> } |
  * workspace showed the sidebar on another — the selector kept whatever
  * localStorage held (or the FIRST binding, on a fresh profile), and a click in
  * the change panel matched its binding by alias alone, which is ambiguous as
- * soon as one host carries two workspaces (P710 and Z700 share `ssh_xiray_new`).
+ * soon as one host carries two workspaces under one alias).
  *
  * Resolution order, strongest evidence first (all of it inside
  * `planWorkspaceFollow`, so the policy has exactly one home):

package/src/p2/router-fs.ts

@@ -189,7 +189,7 @@ export default class TransparentFileSystem extends FileSystem {
     // for remote processes), but that spelling is not guaranteed to route BACK:
     // a session path derived from it (working-directory.set commits THIS value)
     // would resolve local whenever two bindings share the remote root — that is
-    // how subagents of `mlxy`/`xjp-xiray` sessions ended up running on the Host.
+    // how subagents of a session bound to another host ended up running on the Host.
     // toSessionPath keeps the remote spelling where it is unambiguous and uses
     // the binding's unique alias spelling only where it is not.
     return this.remote.toSessionPath(world, fs.processPath(target))

package/src/p2/worlds.ts

@@ -173,8 +173,8 @@ export class RemoteWorlds {
     if (byRemotePath.length === 0) return undefined
     const longest = Math.max(...byRemotePath.map(candidate => candidate.length))
     const top = byRemotePath.filter(candidate => candidate.length === longest)
-    // Two bindings can share one remote directory — here `mlxy:/home` and
-    // `xjp-xiray:/home` do. Picking either would send a write to the wrong host,
+    // Two bindings can share one remote directory — here two aliases both
+    // mounted at `/home` do. Picking either would send a write to the wrong host,
     // and a wrong-host write is silent and destructive in a way a local one is
     // not, so an ambiguous remote-form cwd stays local instead of guessing.
     //
@@ -276,7 +276,7 @@ export class RemoteWorlds {
    * service canonicalizes through it), and the remote fs view answers the remote
    * absolute path. That is the right spelling for display and for remote
    * processes, but it is not always a spelling the router can route BACK: two
-   * bindings may share one remote root (`mlxy:/home` + `xjp-xiray:/home`), and
+   * bindings may share one remote root (two aliases both mounted at `/home`), and
    * `/home` is then deliberately ambiguous and resolves local. A spawned child
    * session inherits exactly that committed spelling — so every subagent of a
    * remote session in one of those workspaces silently ran on the Host (and a