@banzhe/dsh-devcontainer 0.0.0-stage → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,3 +1,80 @@
1
- # Temporary Holding Version
1
+ # @banzhe/dsh-devcontainer
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Runs every agent command inside the repository's Linux Dev Container — or a Docker Sandbox — and makes the model believe it is already there: `bash`, Linux paths, Linux commands. Any repository that declares a Dev Container gets container execution; every other directory keeps the ordinary local shell, unchanged.
4
+
5
+ [中文版](./README.zh-CN.md)
6
+
7
+ A Host-only [DSH](https://github.com/deepseek-ai/deepseek-harness) Bundle for the **web**, **desktop**, and **CLI** profiles.
8
+
9
+ ## Features
10
+
11
+ - **Repository discovery.** The executor walks up from whatever directory a command names and takes the nearest declaration: `.dsh/devcontainer.json` or `.dsh/docker.json` first, then `.devcontainer/devcontainer.json`, then `.devcontainer.json`. All three accept JSONC (comments and trailing commas).
12
+ - **Real container execution.** Commands run through `docker exec -i -w <container workdir>`, from an explicit `container`/`containerName`, from the running container the Dev Container CLI labelled `devcontainer.local_folder=<repo>`, or from `devcontainer up` when nothing is running yet.
13
+ - **Linux paths in, Linux paths out.** `ctx.shell` reports the container workdir (`/workspaces/<repo>/src`), while the process itself starts in the host repository root — `child_process` cannot enter a Linux path on Windows.
14
+ - **The Session directory is a host path.** `WorkingDirectoryService` records whatever `ctx.fs.processPath` answers, and a container path is not a host path on Windows: `/f/personal/repo` made the `.git` probe resolve `F:\f\personal\repo\.git`, which is inside no repository, and the refusal killed a delegating `… (sbx)` subagent before its first step. For a Windows-rooted repository `processPath` therefore answers the host path of a container target; the container spelling keeps its two uses, the argv a runtime is started with (`cd -- /f/personal/repo`) and the payload of an RPC request.
15
+ - **Host processes start where the host can enter.** A `(devContainer)` session hands every seam container paths, but a child process cannot start in one: the `run_code` PTC worker died with `spawn … ENOENT` before its first `tools.read` call. `ctx.subprocess.spawn` is decorated so a working directory that belongs to a discovered repository is translated back onto that repository's host root — POSIX path arithmetic plus the root's own separator style, so a Windows, Linux, and macOS host take the same code path — while an ordinary session, a host path, and a container path no declaration owns reach the provider exactly as written. Only the directory moves: what the worker then does with files is still `ctx.fs`, still the container RPC pipe. `ctx.ptcRuntime` is decorated for the same reason at its own two entry points: `resolve` fills a directory the caller left out from the sandbox policy's workspace root — the container's `/workspaces/<repo>` — and `run` hands that directory to the worker that `chdir`s into it, so both translate a container path onto the host repository root, and a request or spec that names anything else reaches the provider untouched.
16
+ - **Files run in the container too.** A `(devContainer)` session's `ctx.fs` delegates every operation — `resolve`, `stat`, `lstat`, reads, listings, byte ranges, `write`, `edit`, `patch`, `delete`, and `move` — over a persistent stdio RPC pipe to a Node helper running inside the container (DSH's SSH helper framing, protocol 3). The container resolves the path, follows the symbolic link, and performs the I/O, so no host path is opened, and `read`, `write`, `edit`, `glob`, `grep`, and `working_directory` all keep working with Linux spellings. Ordinary presets keep the earlier behaviour: the container view (`/workspaces/<repo>/…`, and the `F:\workspaces\<repo>\…` a Windows model mangles it into) is mapped onto the host bind mount, with the sandbox write fence inherited unchanged.
17
+ - **A Linux prompt.** The `working-directory:current` context becomes `Current working directory: "/workspaces/<repo>"` plus a `Runtime environment: Linux Docker container … always write POSIX/Linux commands and never PowerShell commands` line.
18
+ - **No environment bleed.** Only `remoteEnv`, the caller's own entries, the `DSH_*` snapshot, and `TERM=dumb`/`GIT_TERMINAL_PROMPT=0`/`NO_COLOR=1` reach the container: no host `PATH`, no `SystemRoot`. The Docker / Dev Container CLI itself starts from a scrubbed environment too — an allowlist of what it needs to find `docker` and read your Docker configuration, plus the `DOCKER_*`/`XDG_*` families, with credential-shaped names dropped — so the harness's own credentials never reach it or the processes it starts.
19
+ - **A settings page that derives presets on demand.** On Windows the shipped presets mount `pwsh` and disable `bash`; a Dev Container is Linux, so checking a preset on the **Settings → Dev Container presets** page derives a `… (devContainer)` copy of it (for example `委派模式 (devContainer)`, `标准模式 (devContainer)`) that mounts `bash` and sends its subagents to their own derived copies. Subagent routes are followed four levels deep; a route that limit stops is dropped (an allowed choice removed, a fixed preset row disabled) instead of being left pointing at the ordinary preset. The page carries two independent groups: **Dev Container** (the `sources` list, heading `(devContainer)`) and **Docker Sandbox** (the `sbxSources` list, heading `(sbx)`), and checking a box in one group never touches the other list. Nothing is derived until you check something, unchecking disposes the copy immediately, and the presets you already have are never modified — a preset that mounts no shell tool (the delegate main agent) derives to one that still mounts none.
20
+ - **Docker Sandbox (`sbx`) is a second track, with no declaration required.** A `… (sbx)` preset derives from the new `sbxSources` list the same way `… (devContainer)` derives from `sources` — same shell-tool flip, same depth-bounded subagent routing, but each track routes only into its own variants. Because a sandbox is given a host directory to mount rather than a build to describe, a repository needs no `.devcontainer/devcontainer.json`: the sandbox `dsh-<repo>-<hash>` is listed (`sbx ls --json`), created (`sbx create --name … shell <root>`) and started detached (`sbx run --detach --name …`) on first use, and commands run as `sbx exec <name> -- /bin/sh -c "cd -- '<workdir>' && exec … '<shell>' -c '<command>'"`. `ctx.fs` delegates to the same container helper over `sbx exec -i <name> -- node …`, so reads and writes happen inside the sandbox, and a missing `sbx` CLI is reported as an install problem rather than as a missing sandbox. A filesystem call names its workspace the way the sandbox mounts it (`/f/personal/repo`), which is no host path at all, while one row serves every session on the host and its configured `cwd` is the directory DSH started in: the host directory is recovered from the mounts `sbx ls` reported — the deepest one wins and names the workspace, declaration or not — and from the drive convention only when a repository really declares a container there, so a path outside every mount is still refused on the host. The shell row reverses the same spelling before it looks a repository up, so a workdir of `/f/personal/repo` runs in that directory's sandbox even when the row was mounted without a `cwd`.
21
+ - **Falls back to the platform's own shell** for ordinary presets: a directory with no Dev Container declaration keeps the local provider it had before — bash on POSIX, PowerShell on Windows (`pwsh -NoLogo -NoProfile -NonInteractive -Command`) — so the ordinary `pwsh` tool keeps working outside container repositories.
22
+ - **Container routing follows the preset.** A `… (devContainer)` preset runs every command in the repository's container; an ordinary preset keeps the host shell it had, even in a repository that declares a container. Set `requireContainer: true` on the rows to make every session container-bound instead.
23
+ - **A `(devContainer)` preset never runs on the host by accident.** The shell tools mark every call issued from a derived preset, so a repository that declares no container gets a warning in the working-directory context (the model is told to say so, in Chinese, and to stop retrying) and the executor **refuses** the command with `exitCode: 1` and a diagnostic instead of falling back. Ordinary presets are unaffected.
24
+ - **Files are refused with the commands.** `ctx.fs` reads the same preset for the agent that issued the call (a subagent answers for its own Session), so in a repository that declares no container every `resolve`, `read`, `write`, `edit`, `stat`, and listing is refused with a structured `FS_PERMISSION_DENIED` — no host file is read, written, or created. A `(devContainer)` session over a repository that DOES declare a container is fully delegated to that container, and an ordinary preset keeps the plain host filesystem. Looking like it is inside the repository is not enough: a symbolic link that resolves outside the repository's mount is refused the same way, and the diagnostic names the link target.
25
+
26
+ A repository opts in with any one of the three shapes, for example:
27
+
28
+ ```jsonc
29
+ // .devcontainer/devcontainer.json
30
+ {
31
+ "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
32
+ "workspaceFolder": "/workspaces/my-repo",
33
+ "remoteUser": "vscode",
34
+ "remoteEnv": { "CI": "1" },
35
+ }
36
+ ```
37
+
38
+ ```jsonc
39
+ // .dsh/docker.json — the lightweight form: reuse a container that is already running
40
+ {
41
+ "container": "my-repo-dev",
42
+ "workspaceFolder": "/workspaces/my-repo",
43
+ }
44
+ ```
45
+
46
+ Every field, the driver fallbacks, and the preset mechanics are documented in the implementation notes.
47
+
48
+ ## Install
49
+
50
+ ### From npm
51
+
52
+ ```sh
53
+ dsh plugin --profile web add @banzhe/dsh-devcontainer
54
+ ```
55
+
56
+ ### From a local checkout
57
+
58
+ ```sh
59
+ pnpm install
60
+ pnpm --filter @banzhe/dsh-devcontainer build
61
+ dsh plugin --profile web add ./plugins/devcontainer
62
+ ```
63
+
64
+ Restart `dsh web` (or the CLI session) afterwards: the Bundle replaces `ctx.shell` and `ctx.fs` at activation, and the preset variants are registered from the Loader tree once it settles. Do not assume HMR.
65
+
66
+ The **`desktop` profile is off limits to the CLI**: add this Bundle through the application's own plugin manager, or add the dependency and the `dsh.profile.bundles` entry to `$DSH_HOME/profiles/desktop/package.json` by hand and run `pnpm install` in that directory. Profiles do not share a bundle list.
67
+
68
+ Remove with:
69
+
70
+ ```sh
71
+ dsh plugin --profile web remove @banzhe/dsh-devcontainer
72
+ ```
73
+
74
+ ## Docs
75
+
76
+ Implementation notes: [`docs/plugins/devcontainer.md`](https://github.com/banzhe/dsh-plugins/blob/master/docs/plugins/devcontainer.md).
77
+
78
+ ## License
79
+
80
+ MIT
@@ -0,0 +1,80 @@
1
+ # @banzhe/dsh-devcontainer
2
+
3
+ 让 Agent 的每条命令都在仓库指定的 Linux Dev Container 里执行,并让模型以为自己本来就在 Linux 里:用 `bash`、写 Linux 路径、写 Linux 命令。声明了 Dev Container 的仓库走容器;其他目录保持原有本地 shell 行为,一切照旧。
4
+
5
+ [English](./README.md)
6
+
7
+ 仅 Host 端的 [DSH](https://github.com/deepseek-ai/deepseek-harness) Bundle,适用于 **web**、**desktop** 与 **CLI** profile。
8
+
9
+ ## 功能
10
+
11
+ - **仓库级发现。** 执行器从命令指向的目录向上查找,取最近的声明:先 `.dsh/devcontainer.json` / `.dsh/docker.json`,再 `.devcontainer/devcontainer.json`,最后 `.devcontainer.json`。三者都接受 JSONC(注释与尾随逗号)。
12
+ - **真正在容器里跑。** 命令通过 `docker exec -i -w <容器内工作目录>` 执行:容器来源可以是配置里显式的 `container`/`containerName`,可以是 Dev Container CLI 打过 `devcontainer.local_folder=<仓库>` 标签的运行中容器,也可以由 `devcontainer up` 现场构建。
13
+ - **进出都是 Linux 路径。** `ctx.shell` 把工作目录报成容器路径(`/workspaces/<仓库>/src`),而进程本身从宿主机仓库根启动——Windows 上的 `child_process` 无法进入不存在的 Linux 路径。
14
+ - **会话目录是宿主路径。** `WorkingDirectoryService` 记录的是 `ctx.fs.processPath` 的返回值,而 Windows 宿主机上的容器路径并不是宿主路径:`/f/personal/repo` 会让 `.git` 探测落到 `F:\f\personal\repo\.git`——一个不属于任何仓库的目录,拒绝直接让委派的 `… (sbx)` 子代理在第一步之前失败。因此对 Windows 根目录的仓库,`processPath` 返回容器目标对应的宿主路径;容器路径只保留两处用途:启动运行时的 argv(`cd -- /f/personal/repo`)和 RPC 请求的载荷。
15
+ - **宿主进程从宿主能进入的目录启动。** `(devContainer)` 会话的每个接缝都在说容器路径,但子进程无法在其中启动:`run_code` 的 PTC Worker 在第一次 `tools.read` 之前就以 `spawn … ENOENT` 失败。插件装饰了 `ctx.subprocess.spawn`:属于已发现仓库的工作目录会被反向映射回该仓库的宿主机根目录(POSIX 相对路径运算,加上宿主根目录自己的分隔符风格,Windows、Linux、macOS 走同一份代码),而普通会话、宿主路径、无声明归属的容器路径原样交给 provider。只有工作目录被改写:Worker 之后对文件做的一切仍然是 `ctx.fs`,仍然走容器内的 RPC 管道。`ctx.ptcRuntime` 出于同一原因被装饰在自己的两个入口上:`resolve` 会用沙箱策略的 workspace root(容器的 `/workspaces/<repo>`)补齐调用方没有给出的目录,`run` 再把这个目录交给要 `chdir` 进去的 Worker,因此两者都把容器路径转成宿主机仓库根目录,其余请求与 spec 原样交给 provider。
16
+ - **文件读写也进容器。** `(devContainer)` 会话的 `ctx.fs` 把每个操作——`resolve`、`stat`、`lstat`、读取、目录列举、字节区间、`write`、`edit`、`patch`、`delete`、`move`——通过一条常驻 stdio RPC 管道交给容器内的 Node helper 执行(沿用 DSH SSH helper 的帧格式,协议版本 3)。路径解析、符号链接跟随与实际 I/O 都发生在容器里,宿主机不会打开任何文件,`read`、`write`、`edit`、`glob`、`grep`、`working_directory` 照旧用 Linux 路径。普通预设保持原行为:把容器视角(`/workspaces/<仓库>/…`,以及 Windows 模型误解析出的 `F:\workspaces\<仓库>\…`)映射回宿主机 bind mount,沙箱写入围栏原样继承。
17
+ - **Linux 提示词。** `working-directory:current` 上下文被改写为 `Current working directory: "/workspaces/<仓库>"` 并追加 `Runtime environment: Linux Docker container … always write POSIX/Linux commands and never PowerShell commands`。
18
+ - **不串环境变量。** 进入容器的只有 `remoteEnv`、调用方自己的条目、`DSH_*` 快照,以及 `TERM=dumb`/`GIT_TERMINAL_PROMPT=0`/`NO_COLOR=1`:没有宿主机 `PATH`,没有 `SystemRoot`。宿主一侧同样清洗:Docker / Dev Container CLI 只带着白名单变量启动(找到 `docker` 与读取你自己的 Docker 配置所需的那几个,加上 `DOCKER_*`/`XDG_*` 家族,并剔除名字像凭据的变量),DSH 自己的凭据不会进入它,也不会进入它启动的进程。
19
+ - **设置页按需派生预设。** Windows 上官方预设挂 `pwsh`、禁用 `bash`;Dev Container 是 Linux,所以在**设置 → Dev Container 预设**页勾选某个预设,就会派生它的 `… (devContainer)` 副本(例如 `委派模式 (devContainer)`、`标准模式 (devContainer)`):改用 `bash`,子代理也指向各自派生的副本,路由最多追踪四层;到达上限的路由会被切断(从可选列表里移除,或禁用整行固定路由),而不是留成原版宿主预设。该页分成两组,互不影响:**Dev Container** 组写 `sources`、派生的预设名后缀是 `(devContainer)`,**Docker Sandbox** 组写 `sbxSources`、后缀是 `(sbx)`。默认不派生任何预设,取消勾选立即注销副本;原有预设一律不改——本来不挂 shell 工具的预设(委派模式主代理)派生后依然不挂。
20
+ - **Docker Sandbox(`sbx`)是第二条派生轨道,且不需要任何声明文件。** `… (sbx)` 预设由新的 `sbxSources` 列表派生,机制与 `sources` 派生 `… (devContainer)` 完全一致:同样翻转 shell 工具、同样限深的子代理路由,但每条轨道只会把子代理指向自己这条轨道的副本。因为沙箱只需要一个宿主目录、不需要任何构建描述,仓库不需要 `.devcontainer/devcontainer.json`:首次使用时会列出(`sbx ls --json`)、创建(`sbx create --name … shell <仓库根>`)并以 detach 方式启动(`sbx run --detach --name …`)名为 `dsh-<仓库>-<哈希>` 的沙箱,命令以 `sbx exec <名字> -- /bin/sh -c "cd -- '<工作目录>' && exec … '<shell>' -c '<命令>'"` 执行。`ctx.fs` 通过 `sbx exec -i <名字> -- node …` 复用同一个容器 helper,读写都发生在沙箱内部;缺少 `sbx` CLI 时给出的是安装指引,而不是「沙箱不存在」。文件调用报出的路径是沙箱挂载的拼写(`/f/personal/repo`),它根本不是宿主路径,而一行配置服务宿主上的所有会话、其 `cwd` 是启动 DSH 的目录:宿主目录由 `sbx ls` 报告的挂载反解得出(最深的挂载优先,并直接给出工作区根目录,无论仓库有没有声明文件),只有仓库确实在该盘符路径上声明了容器时才采用盘符约定,因此落在所有挂载之外的路径仍然在宿主侧被拒绝。shell 行在查找仓库之前会先反解同一个拼写,因此即使该行挂载时没有配置 `cwd`,工作目录 `/f/personal/repo` 也会进入该目录对应的沙箱。
21
+ - **普通预设的本地兜底沿用平台自己的 shell。** 没有声明 Dev Container 的目录保持安装前的本地执行器:POSIX 上用 bash,Windows 上用 PowerShell(`pwsh -NoLogo -NoProfile -NonInteractive -Command`)。因此普通的 `pwsh` 工具在容器仓库之外照常可用。
22
+ - **容器路由跟随预设。**`… (devContainer)` 预设把每条命令送进仓库容器;普通预设保持原来的宿主机 shell,即使该仓库声明了容器。想让所有会话都走容器,请在各行设置 `requireContainer: true`。
23
+ - **`(devContainer)` 预设不会悄悄在宿主机上跑命令。** shell 工具会给来自派生预设的每次调用打标记,所以仓库没有容器配置时:工作目录上下文里会出现明确警告(要求模型立刻用中文说明情况并停止重试),执行器**直接拒绝**执行并返回 `exitCode: 1` 与诊断信息,而不是回退到宿主机。普通预设不受影响。
24
+ - **文件读写与命令一起被拒绝。** `ctx.fs` 按发起调用的 agent 读取同一个预设(子代理用自己的 Session 作答),所以在没有容器配置的仓库里,`resolve`、`read`、`write`、`edit`、`stat` 与目录列举都会被拒绝并抛出结构化的 `FS_PERMISSION_DENIED`:宿主机上的文件不会被读取、写入或创建。仓库确实声明了容器时,`(devContainer)` 会话整体委托给该容器执行;普通预设照旧直读宿主机文件系统。仅仅「看起来在仓库里」不算数:解析到仓库挂载点之外的符号链接会被同样拒绝,诊断信息会指出真实的链接目标。
25
+
26
+ 仓库用三种形态中的任意一种接入,例如:
27
+
28
+ ```jsonc
29
+ // .devcontainer/devcontainer.json
30
+ {
31
+ "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
32
+ "workspaceFolder": "/workspaces/my-repo",
33
+ "remoteUser": "vscode",
34
+ "remoteEnv": { "CI": "1" },
35
+ }
36
+ ```
37
+
38
+ ```jsonc
39
+ // .dsh/docker.json —— 轻量形态:直接复用一个已经在跑的容器
40
+ {
41
+ "container": "my-repo-dev",
42
+ "workspaceFolder": "/workspaces/my-repo",
43
+ }
44
+ ```
45
+
46
+ 字段全表、驱动回退顺序与预设机制见实现说明文档。
47
+
48
+ ## 安装
49
+
50
+ ### 从 npm
51
+
52
+ ```sh
53
+ dsh plugin --profile web add @banzhe/dsh-devcontainer
54
+ ```
55
+
56
+ ### 从本地检出
57
+
58
+ ```sh
59
+ pnpm install
60
+ pnpm --filter @banzhe/dsh-devcontainer build
61
+ dsh plugin --profile web add ./plugins/devcontainer
62
+ ```
63
+
64
+ 装完重启 `dsh web`(或 CLI 会话):本 Bundle 在激活时替换 `ctx.shell` 与 `ctx.fs`,预设变体则要等 Loader 树稳定后才注册。请不要指望 HMR。
65
+
66
+ **`desktop` profile 不对 CLI 开放**:请通过应用自带的插件管理器安装,或手工把依赖与 `dsh.profile.bundles` 条目写进 `$DSH_HOME/profiles/desktop/package.json` 后在该目录执行 `pnpm install`。各 profile 的 bundle 列表互不共享。
67
+
68
+ 卸载:
69
+
70
+ ```sh
71
+ dsh plugin --profile web remove @banzhe/dsh-devcontainer
72
+ ```
73
+
74
+ ## 文档
75
+
76
+ 实现说明:[`docs/plugins/devcontainer.md`](https://github.com/banzhe/dsh-plugins/blob/master/docs/plugins/devcontainer.md)。
77
+
78
+ ## 许可
79
+
80
+ MIT
@@ -0,0 +1,71 @@
1
+ # This layer swaps BOTH execution capabilities for container-aware ones.
2
+ #
3
+ # Loader patch semantics: a non-insert entry targets a row by `id` and can only
4
+ # change `config`/`disabled`; a supplied `name` must equal the target's. Rows the
5
+ # bundles own are disabled here on purpose — each of these services holds exactly
6
+ # one slot, so the built-in provider must not register at all.
7
+ #
8
+ # bash-sandbox / pwsh-sandbox provide the local `ctx.shell`; the devcontainer
9
+ # executor replaces them (it subclasses
10
+ # `SandboxBashExecutor`, so the process mechanics
11
+ # AND the host-side confinement are the same; a
12
+ # container-bound command changes only the argv and
13
+ # cwd, and reports itself unconfined on the host
14
+ # because the container confines it). Outside a Dev
15
+ # Container repository it reproduces the local
16
+ # provider of THIS platform: bash on POSIX,
17
+ # PowerShell on Windows. Basing on the sandboxed
18
+ # executor is what keeps `ctx.shell.sandboxMode`
19
+ # available for permission presets.
20
+ # fs-sandbox provides `ctx.fs`; the bridged filesystem
21
+ # subclasses the SAME `SandboxedFileSystem`, so the
22
+ # per-call write fence is unchanged.
23
+ #
24
+ # `subprocess` keeps its row: the Host row below decorates the mounted seam's
25
+ # `spawn` (one decision — a container-side working directory becomes the host
26
+ # repository root, because no host process can start in `/workspaces/…`) instead
27
+ # of providing a second implementation, which Cordis would refuse.
28
+ #
29
+ # This file deliberately says NOTHING about `tool-bash` / `tool-pwsh`.
30
+ # `packages/bundle/web-app/cordis.patch.yml:493-497` disables both at the host
31
+ # level on purpose: which shell tool an agent gets is decided by its PRESET, not
32
+ # by the deployment. Re-enabling `tool-bash` here would hand `bash` to every
33
+ # agent, including the delegate main agent whose preset mounts no shell tool at
34
+ # all. The shell-tool flip lives in the derived `… (devContainer)` presets
35
+ # instead (docs/plugins/devcontainer.md, "Windows shell tools").
36
+ #
37
+ # The browser half — the settings page that chooses which presets get a
38
+ # `… (devContainer)` variant — is the `dsh.client` entry of the SAME package, added
39
+ # by the client module scanner rather than by a row here. Nothing is derived until
40
+ # someone checks a box on that page: `sources` starts empty. The second track,
41
+ # `… (sbx)` variants derived from `sbxSources`, needs no page and no declaration:
42
+ # the Host row derives it from the profile config, and the executor reaches a
43
+ # Docker Sandbox through the same `ctx.shell` / `ctx.fs` rows below.
44
+ #
45
+ # Rollback: remove this Bundle from the Profile; the disabled rows re-enable
46
+ # themselves and each replaced service goes back to its local provider.
47
+ - id: bash-sandbox
48
+ disabled: true
49
+
50
+ - id: pwsh-sandbox
51
+ disabled: true
52
+
53
+ - id: fs-sandbox
54
+ disabled: true
55
+
56
+ - insert:
57
+ - id: devcontainer
58
+ name: '@banzhe/dsh-devcontainer'
59
+
60
+ # The container executor: registers `ctx.shell` and runs every command
61
+ # through `docker exec` / `devcontainer exec` when the workdir's repository
62
+ # declares a Dev Container, and through the platform's own local executor
63
+ # otherwise.
64
+ - id: devcontainer-shell
65
+ name: '@banzhe/dsh-devcontainer/shell'
66
+
67
+ # The path bridge: registers `ctx.fs` and maps `/workspaces/<repo>/…` (and the
68
+ # `F:\workspaces\<repo>\…` a Windows model mangles it into) onto the host path
69
+ # before delegating to the sandboxed local backend.
70
+ - id: devcontainer-fs
71
+ name: '@banzhe/dsh-devcontainer/fs'