dsh-plugin-wsl-env 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -12,18 +12,88 @@ reference below points at that record's numbering.
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-10-02
+
+Repository and release engineering. No runtime behaviour changed.
+
+### Added
+
+- `npm run lint:style` ([`test/style.mjs`](test/style.mjs)): a dependency-free gate
+  over the rules `.editorconfig` states, plus three packaging checks — every `files`
+  entry still matches tracked content, every `exports` target exists, and exactly one
+  readme candidate sits at the package root. That last one is the regression guard
+  for the 0.1.1 readme, and it is why the gate exists at all.
+- `npm run test:coverage`, with thresholds of 85% lines, 85% branches and 70%
+  functions, using Node's built-in coverage. No coverage dependency was added. The
+  spawning half of `lib/wsl.js` and the four service modules are covered by the
+  probes instead, which is why the function threshold is lower than the others.
+- `.github/workflows/release.yml`: a `v*` tag is checked against `package.json`
+  ([`scripts/check-release-tag.mjs`](scripts/check-release-tag.mjs)), gated, then
+  published with `--provenance` through npm trusted publishing, and the GitHub
+  Release is created from the changelog section
+  ([`scripts/changelog-section.mjs`](scripts/changelog-section.mjs)). No npm token is
+  stored in the repository.
+- The governance files a public repository is expected to carry:
+  [`SECURITY.md`](SECURITY.md), [`CONTRIBUTING.md`](CONTRIBUTING.md),
+  [`SUPPORT.md`](SUPPORT.md), [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md),
+  `CODEOWNERS`, a pull-request template, bug-report and contact-link issue templates,
+  and a Dependabot configuration for the pinned workflow actions.
+- [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) describes the plugin as it is
+  today — the providers, how they are mounted, the three path coordinate systems, the
+  sandbox, the runtime mirror and the test layers — so the current design no longer
+  has to be reconstructed from a changelog and a historical record.
+- [`docs/RELEASING.md`](docs/RELEASING.md): the release checklist, including the
+  operational facts that cost time to learn.
+- [`docs/archive/README.en.md`](docs/archive/README.en.md): an English index of the
+  Chinese archive.
+- `.nvmrc` names the Node version the coverage job uses.
+
+### Changed
+
+- The probes no longer carry a user name, a home directory or a distro name.
+  [`test/probe/env.sh`](test/probe/env.sh) derives them from the machine
+  (`%USERPROFILE%`, `%LOCALAPPDATA%`, `WSL_DISTRO_NAME`) and
+  [`test/probe/env.mjs`](test/probe/env.mjs) does the same for the Node-side probes,
+  which learn their own location from `import.meta.url`. The YAML overlays are now
+  templates with `@NAME@` placeholders, and the scripts substitute real values into
+  generated copies that `.gitignore` keeps out of the tree. The two profile layers
+  use `distro: ''` (WSL's default distro) instead of naming one.
+- CI runs the unit suite on Windows as well as Linux. The plugin targets Windows, and
+  the Windows legs also prove that the LF guarantee in `.gitattributes` holds on the
+  platform whose default is CRLF. The workflow gained least-privilege `permissions`,
+  a `concurrency` group, timeouts, and actions pinned by commit SHA.
+- `package.json`: `packageManager` is gone, because the package has no dependencies
+  and npm is the reference toolchain everywhere else; `author` and `publishConfig`
+  are set; `prepublishOnly` runs the gates; and `files` ships `CONTRIBUTING.md`,
+  `SECURITY.md` and `SUPPORT.md` so a tarball without the repository still says how
+  to contribute, report and get help.
+- Both READMEs gained a *Contributing and support* section, and list the new gates.
+
+### Fixed
+
+- Corrected the 0.1.2 entry. It had named the npm CLI's readme rule as the cause of
+  the 0.1.1 readme mix-up; that rule does not match `.md` names and is not the code
+  path that decides a published package's readme, so the entry now records what was
+  observed instead of a mechanism that does not hold. The GitHub Release notes for
+  v0.1.2 were corrected the same way.
+- Six lines in [`lib/index.js`](lib/index.js) were indented with tabs while the rest
+  of the file uses spaces, which the new style gate caught.
+
 ## [0.1.2] - 2026-10-02
 
 ### Fixed
 
-- The npm package page rendered the Chinese README instead of the English one. npm
-  chooses a package's readme by globbing `{README,README.*}` in the package root and
-  taking the first `.md` match (`@npmcli/package-json/lib/normalize.js`), so two
-  candidate files made the choice depend on directory enumeration order. 0.1.1
-  shipped with `readmeFilename: README.zh.md`. The translation now lives at
-  `docs/README.zh.md`, which leaves exactly one candidate at the root and removes
-  the ambiguity by construction rather than by luck. The English header still links
-  to it and it still ships in the tarball through `files`. 0.1.1 remains on the
+- The npm package page rendered the Chinese README instead of the English one. 0.1.1
+  published `README.md` and `README.zh.md` side by side, and the registry answered
+  with `readmeFilename: README.zh.md`. Two candidates are enough to make the outcome
+  unreliable, and neither obvious rule explains which one won: it is not the tarball's
+  entry order (0.1.1's tarball listed `package/README.md` first), and it is not the
+  npm CLI's own selection rule (`@npmcli/package-json/lib/normalize.js` globs
+  `{README,README.*}` and accepts `/\.m?a?r?k?d?o?w?n$/i`, which does not match a
+  `.md` name at all). The registry is picking by a rule this repository should not
+  depend on. The translation now lives at `docs/README.zh.md`, which leaves exactly
+  one candidate at the package root and removes the question by construction. The
+  English header still links to it and `files` still ships it. 0.1.1 remains on the
   registry with the wrong readme; 0.1.2 supersedes it.
 
 ## [0.1.1] - 2026-10-02

package/CONTRIBUTING.md

@@ -0,0 +1,127 @@
+# Contributing
+
+This document covers the development loop, the gates a pull request must pass, and
+the conventions this repository uses.
+
+## Prerequisites
+
+| Requirement | Notes |
+|---|---|
+| Windows 10 or 11 | the plugin targets Windows only |
+| WSL2 with at least one distro | `wsl.exe -l -v` lists the installed distros |
+| `bubblewrap` in the distro | `sudo apt install bubblewrap`. The sandbox fails closed without it. |
+| Node 20, 22, or 24 | the versions CI runs. `engines` requires `>=20`. |
+
+## Toolchain
+
+The package has no dependencies, so there is no install step. Run the scripts
+straight from a checkout.
+
+`npm` runs the scripts in this repository, and CI uses npm. Treat
+`npm run <script>` as the reference toolchain.
+
+Do not add a runtime dependency. The package ships an empty `dependencies` object
+on purpose, because it is loaded into the DSH process and everything it needs
+arrives as a peer package.
+
+Style tooling is kept out for the same reason. There is no ESLint, no Prettier, and
+no `devDependencies` at all. The checks that would normally need them are built
+from Node builtins instead. `test/style.mjs` verifies the rules `.editorconfig`
+states, and it checks that every `files` entry still matches tracked content and
+every `exports` target still exists. The syntax pass inside `npm test` uses Node's
+own parser.
+
+## The development loop
+
+1. Clone the repository inside the distro. Most contributors develop there.
+2. Make the change.
+3. Run the gates below.
+4. Restart the DSH app before testing by hand, if you changed anything under
+   `lib/`. A running process caches ES modules, so it keeps the old code
+   otherwise.
+
+### The runtime mirror
+
+A DSH profile can only link a Windows path. pnpm rewrites
+`link:\\wsl.localhost\...` into a broken `/wsl.localhost/...` symlink, so the
+harness cannot load the plugin from a distro checkout.
+
+The Windows copy under `default-workspace/dsh-plugin-wsl` is a runtime mirror. Sync
+it before launching the app:
+
+```bash
+npm run sync:windows
+```
+
+The mirror destination sits outside a session workspace. An agent that runs the
+sync from a confined shell is refused by the `workspace-write` policy and has to
+approve a wider permission for that one command. Run the sync from a plain distro
+terminal if you would rather not see the prompt.
+
+## Gates before a pull request
+
+| Command | Covers | Needs a harness |
+|---|---|---|
+| `npm test` | style checks, syntax pass, and unit tests | no |
+| `npm run test:coverage` | unit tests with coverage | no |
+| `npm run lint:style` | style and lint rules | no |
+| `npm run probe` | filesystem behaviour against a real distro | yes |
+| `npm run probe:sandbox` | what bubblewrap confines and what it does not | no |
+| `npm run probe:sandbox-shell` | the confined executor through a real boot | yes |
+| `npm run probe:terminal` | the terminal provider | yes |
+
+Every script above is wired in `package.json`. `npm test` runs `lint:style`,
+`test:syntax` and `test:unit` in that order. `prepublishOnly` runs `npm test` again
+at publish time, so a broken gate stops a release before the upload.
+
+CI runs `npm test` on Node 20, 22 and 24, on both `ubuntu-latest` and
+`windows-latest`, and `npm run test:coverage` on Node 24. The Windows runners are
+there because the plugin targets Windows; the coverage thresholds need Node 22.8 or
+newer, which is why that job runs on one version.
+
+The probes marked "yes" need Windows, WSL2, a mounted harness profile and a linked
+checkout, which a hosted runner does not have. Run them on your own machine and
+paste the output into the pull request.
+
+## Adding a test
+
+Choose the layer by what the test needs.
+
+| Layer | Location | Use it for |
+|---|---|---|
+| Unit test | `test/*.test.mjs` | pure logic: path translation, listing, shell argument building, terminal helpers |
+| Probe | `test/probe/` | behaviour that needs a real distro, a real profile, or bubblewrap |
+
+Unit tests run under `node --test` and import only Node builtins. Add a file named
+`<area>.test.mjs`, then add it to both the `test:unit` and the `test:coverage`
+scripts in `package.json`. Both scripts list their files explicitly.
+
+Probes are shell scripts that mount a throwaway profile, plus the small plugin
+files they load. Those plugin files are the `*-probe.mjs` and `*-probe.yml` files
+in the same directory. The setup steps for the throwaway profile are in the header
+of `test/probe/run.sh`. `terminal.sh` and `sandbox-shell.sh` reuse it.
+
+Keep probe output idempotent. Several probes delete their scratch files at the
+start, because a leftover file from an earlier run changes the result.
+
+## Commit and pull request conventions
+
+- Write an imperative subject line: `Fix the npm readme`, not `Fixed` or `Fixes`.
+- Do not use conventional-commit prefixes. No `feat:`, `fix:`, or `chore:`.
+- Explain why in the body. What changed is already visible in the diff.
+- Add a `CHANGELOG.md` entry under `## [Unreleased]` for a behaviour change. A
+  change to documentation or to comments does not need one.
+- Keep one topic per commit.
+- In the pull request, say how you tested it. Paste probe output where a probe is
+  relevant.
+- Update `README.md` and `docs/README.zh.md` together when a change affects usage.
+  The two files match section for section.
+
+## Reporting bugs and security issues
+
+Open a GitHub issue for a bug:
+
+https://github.com/Big-Dao/dsh-plugin-wsl-env/issues
+
+Report a security issue privately. Follow [SECURITY.md](SECURITY.md) instead of
+opening a public issue.

package/README.md

@@ -12,7 +12,8 @@ This plugin lets [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harn
 
 [What you get](#what-you-get) · [Install](#install) · [Using it](#using-it) ·
 [Configure](#configure) · [Sandbox](#sandbox) · [Troubleshooting](#troubleshooting) ·
-[Limitations](#limitations) · [Development](#development) · [Design notes](#design-notes)
+[Limitations](#limitations) · [Development](#development) · [Design notes](#design-notes) ·
+[Contributing and support](#contributing-and-support)
 
 ## What you get
 
@@ -147,13 +148,16 @@ These are the same arguments DSH uses on a Linux host (`dsh-sandbox-local`), so
 ## Development
 
 ```bash
-npm test                     # syntax check and unit tests; no dependencies, runs anywhere
+npm test                     # style and packaging checks, syntax check, unit tests
+npm run test:coverage        # the unit tests with coverage thresholds (Node 22.8+)
 npm run probe:sandbox        # measure inside the distro what bubblewrap does and does not confine
 npm run probe                # filesystem probe against a real distro (Windows + WSL only)
 npm run probe:sandbox-shell  # boot a real harness and drive the confined executor
 npm run probe:terminal       # open a PTY through the terminal provider
 ```
 
+The package has no dependencies, so there is nothing to install first.
+
 Layout:
 
 ```text
@@ -197,7 +201,8 @@ Counts: 42 unit assertions, 18 filesystem-probe assertions, 10 shell-probe check
 
 **The runtime mirror.** The checkout is developed inside the distro, but the harness is a Windows process, and a profile can only link a Windows path: pnpm rewrites `link:\\wsl.localhost\...` into a broken `/wsl.localhost/...` symlink. The Windows copy at `default-workspace/dsh-plugin-wsl` is therefore a runtime mirror. Sync it with `test/probe/sync-to-windows.sh` before launching the app. That destination is outside every session workspace, so an agent running the sync in a confined shell is refused by `workspace-write` and must approve `danger-full-access` for that one command. That is the sandbox behaving as designed, not a broken script; run the sync from a normal distro terminal if you prefer not to see the prompt.
 
-**CI** runs `npm test` on Linux with Node 20, 22 and 24.
+**CI** runs `npm test` on Node 20, 22 and 24, on Linux and on Windows, and runs
+`npm run test:coverage` on Node 24 to enforce the coverage thresholds.
 
 ## Design notes
 
@@ -211,6 +216,17 @@ For that reason, [`cordis.patch.yml`](cordis.patch.yml) replaces the **app-wide*
 
 **Why the sandbox is on the Linux side.** The Windows ACL runner's restricted token cannot reach WSL at all, so the confinement has to be built on the Windows side and run inside the distro. `lib/sandbox.js` copies the Linux `bwrap` approach from `dsh-sandbox-local` instead of using `ctx.sandbox`. `dsh-tool-bash` never asks for `ctx.sandbox` anyway: it reads the executor's `sandboxMode` and `ctx.sandboxPolicy`, and this plugin supplies both.
 
+## Contributing and support
+
+| Document | What it covers |
+|---|---|
+| [CONTRIBUTING.md](CONTRIBUTING.md) | the development loop, the gates a pull request must pass, and the conventions used here |
+| [SECURITY.md](SECURITY.md) | reporting a vulnerability privately, response targets, and what counts as in scope |
+| [SUPPORT.md](SUPPORT.md) | what is supported, where to ask, and what a useful bug report contains |
+| [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) | how the providers are mounted, the sandbox design, and the test layers |
+| [docs/RELEASING.md](docs/RELEASING.md) | the release checklist, including the trusted-publisher setup |
+| [docs/archive/README.en.md](docs/archive/README.en.md) | an English index of the archived engineering record |
+
 ## License
 
 MIT. See [LICENSE](LICENSE).

package/SECURITY.md

@@ -0,0 +1,82 @@
+# Security policy
+
+## Supported versions
+
+Only the latest published version receives security fixes.
+
+| Version | Supported |
+|---|---|
+| the version npm's `latest` tag points at | yes |
+| every earlier version | no |
+
+## Reporting a vulnerability
+
+Report a suspected vulnerability privately. Use GitHub's private vulnerability
+reporting on this repository:
+
+https://github.com/Big-Dao/dsh-plugin-wsl-env/security/advisories/new
+
+If that form is not available to you, open an ordinary issue that asks for a
+private channel. Do not put exploit details in that issue. A maintainer will reply
+with a private place to send them.
+
+Do not post exploit details in a public issue, a discussion, or a pull request
+before a fix is released.
+
+## What to include in a report
+
+- The plugin version you tested. `npm ls dsh-plugin-wsl-env` prints it, or name the
+  tag you built from.
+- Your Windows build and the distro you used. `wsl.exe -l -v` lists the distros.
+- The DSH version and the profile name.
+- What you expected to happen, and what happened instead.
+- The smallest reproduction you can produce, with the exact command.
+- Whether the sandbox was enabled at the time. `sandbox: true` is the default.
+
+## Response times
+
+These are targets, not a contract.
+
+| Stage | Target |
+|---|---|
+| Acknowledge the report | within 3 business days |
+| Initial assessment and severity | within 10 business days |
+| A fix, or a documented mitigation | within 30 business days |
+
+If a report is out of scope, we will say so and explain why.
+
+## Scope
+
+In scope:
+
+- the plugin's own code under `lib/`;
+- the published package `dsh-plugin-wsl-env`.
+
+Out of scope:
+
+- the upstream DSH packages under `@deepseek-ai/`. Report those to their own
+  projects.
+- WSL itself, the Windows kernel, and `bubblewrap`.
+- The configuration of a user's own distro. That includes its `sudoers` rules, its
+  mounted filesystems, and the interpreters installed in it.
+- Anything that requires an attacker to already control the user's Windows account
+  or their distro account.
+
+## Sandbox enforcement is `partial` by design
+
+The plugin reports the sandbox enforcement level as `partial`, not `full`. A
+process inside the distro can still start a Windows program through WSL interop,
+for example `/mnt/c/.../*.exe`. That program runs outside the Linux sandbox.
+
+This is a documented design boundary, not a vulnerability by itself. The command
+`npm run probe:sandbox` demonstrates it on your machine, and the README states it
+in its Sandbox section.
+
+A report is still welcome if you find an escape that does not depend on interop,
+or if the plugin ever reports `full` while interop is reachable.
+
+## Credentials
+
+No credential, token, or private key belongs in this repository. That includes npm
+tokens, GitHub tokens, and distro passwords. If you find one committed here, report
+it through the private channel above. Do not open a public issue for it.

package/SUPPORT.md

@@ -0,0 +1,69 @@
+# Support
+
+## What is supported
+
+| Area | Supported |
+|---|---|
+| Operating system | Windows 10 and Windows 11 |
+| Linux side | WSL2 with at least one distro |
+| DSH packages | the `0.2.0-rc.2`-era packages listed in `peerDependencies` |
+| Plugin version | the latest published version only |
+| Node | 20, 22, or 24 |
+
+Outside Windows there is nothing for the plugin to attach to. It runs `ctx.shell`
+inside the distro through `wsl.exe`. A Linux host, a macOS host, or WSL1 is not a
+supported configuration.
+
+## Where to get help
+
+Open an issue in the repository:
+
+https://github.com/Big-Dao/dsh-plugin-wsl-env/issues
+
+Use it for bug reports and for questions about configuration. Search the open and
+the closed issues first.
+
+For a security issue, follow [SECURITY.md](SECURITY.md). Do not open a public
+issue for one.
+
+## What is not supported
+
+- macOS, and Linux hosts that are not WSL2.
+- Windows without WSL2.
+- A modified DSH build, or a fork of the harness packages.
+- A distro the plugin cannot recognize. Examples are a replaced `/bin/sh`, a
+  container-style root filesystem, and a missing `bwrap`.
+- The upstream `@deepseek-ai/*` packages. Report those to their own projects.
+- Third-party npm mirrors. Install from the registry the package was published to.
+
+## Compatibility expectations
+
+The upstream packages are a release candidate, so the peer versions are pinned
+exactly. One example is `@deepseek-ai/dsh-fs: 0.2.0-rc.2`. An upstream change can
+require a new release of this plugin. The exact pins are what make that break
+loudly instead of quietly.
+
+There is no long-term support branch. Fixes go to the latest version.
+
+## What a good bug report contains
+
+| Item | How to get it |
+|---|---|
+| Plugin version | `npm ls dsh-plugin-wsl-env`, or the git tag you built from |
+| DSH version | the version of the harness you run |
+| Distro and kernel | `wsl.exe -l -v`, and `uname -r` inside the distro |
+| Windows build | `winver` |
+| The composed configuration | `dsh --profile <name> --dump-config`, in particular the `dsh-plugin-wsl-env` layer and the rows it patches |
+| Sandbox behaviour | the output of `npm run probe:sandbox`, when the sandbox is involved |
+| What you expected and what happened | one paragraph each |
+| A reproduction | the exact command, or the exact sequence of clicks |
+
+Redact your user name and any path you would rather not publish. The useful part
+of `--dump-config` is usually the layer heading and the patched rows, not the whole
+file.
+
+## Response times
+
+This is a small project maintained in spare time. There is no service-level
+agreement and no guaranteed response time. Security reports have their own targets,
+which are listed in [SECURITY.md](SECURITY.md).

package/docs/README.zh.md

@@ -10,7 +10,7 @@
 
 **只支持 Windows + WSL2。** 安装只有一条命令，插件自身没有依赖。WSL 环境按会话生效：会话如果打开的是 Windows 文件夹，它继续使用原来的 Windows 环境，不受影响。
 
-目录：[能做什么](#能做什么) · [安装](#安装) · [使用](#使用) · [配置](#配置) · [沙箱](#沙箱) · [常见问题](#常见问题) · [已知限制](#已知限制) · [开发](#开发) · [设计说明](#设计说明)
+目录：[能做什么](#能做什么) · [安装](#安装) · [使用](#使用) · [配置](#配置) · [沙箱](#沙箱) · [常见问题](#常见问题) · [已知限制](#已知限制) · [开发](#开发) · [设计说明](#设计说明) · [参与与支持](#参与与支持)
 
 ## 能做什么
 
@@ -145,13 +145,16 @@ wsl.exe -d <发行版> --cd <Linux 目录> --exec bwrap \
 ## 开发
 
 ```bash
-npm test                     # 语法检查 + 单元测试，无依赖，任何平台都能跑
+npm test                     # 风格与打包检查、语法检查、单元测试
+npm run test:coverage        # 带覆盖率阈值的单元测试（需 Node 22.8+）
 npm run probe:sandbox        # 在发行版里实测 bubblewrap 能约束什么、不能约束什么
 npm run probe                # 文件系统探针，需要真实发行版（仅 Windows + WSL）
 npm run probe:sandbox-shell  # 启动真实 harness，驱动受限执行器
 npm run probe:terminal       # 通过终端 provider 打开一个 PTY
 ```
 
+这个包没有依赖，所以不需要先安装任何东西。
+
 目录结构：
 
 ```text
@@ -195,7 +198,8 @@ docs/archive/       被本设计替换掉的方案，以及原因
 
 **运行时镜像。** checkout 在发行版内开发，但 harness 是 Windows 进程，而 profile 只能链接 Windows 路径：pnpm 会把 `link:\\wsl.localhost\...` 改写成坏掉的 `/wsl.localhost/...` 符号链接。所以 `default-workspace/dsh-plugin-wsl` 这份 Windows 副本是运行时镜像，启动应用前用 `test/probe/sync-to-windows.sh` 同步。该目标目录不在任何会话工作区内，所以 agent 在受限 shell 里执行同步时会被 `workspace-write` 拒绝，需要为这一条命令批准 `danger-full-access`。这是沙箱的预期行为，不是脚本坏了；不想看到提示就在普通 distro 终端里执行。
 
-**CI** 在 Linux 上用 Node 20、22、24 运行 `npm test`。
+**CI** 在 Linux 和 Windows 上用 Node 20、22、24 运行 `npm test`，并在 Node 24 上运行
+`npm run test:coverage` 以执行覆盖率阈值。
 
 ## 设计说明
 
@@ -209,6 +213,17 @@ docs/archive/       被本设计替换掉的方案，以及原因
 
 **为什么沙箱放在 Linux 侧。** Windows ACL runner 的受限令牌完全到不了 WSL，所以约束只能在 Windows 侧构造、在发行版内执行。`lib/sandbox.js` 因此照搬 `dsh-sandbox-local` 的 Linux `bwrap` 方案，而不是去用 `ctx.sandbox`；后者 `dsh-tool-bash` 从来不用，它读的是执行器的 `sandboxMode` 和 `ctx.sandboxPolicy`，这两样都由本插件提供。
 
+## 参与与支持
+
+| 文档 | 内容 |
+|---|---|
+| [CONTRIBUTING.md](../CONTRIBUTING.md) | 开发循环、提交前必须通过的质量门、本仓库的约定 |
+| [SECURITY.md](../SECURITY.md) | 如何私下上报漏洞、响应时限、以及哪些问题在范围内 |
+| [SUPPORT.md](../SUPPORT.md) | 支持范围、去哪里提问、以及一份有用的缺陷报告应包含什么 |
+| [docs/ARCHITECTURE.md](ARCHITECTURE.md) | provider 如何挂载、沙箱设计、测试分层 |
+| [docs/RELEASING.md](RELEASING.md) | 发布检查单，含信任发布（trusted publishing）的配置 |
+| [docs/archive/README.en.md](archive/README.en.md) | 归档工程记录的英文索引 |
+
 ## 许可
 
 MIT，见 [LICENSE](../LICENSE)。

package/lib/index.js

@@ -228,12 +228,12 @@ export class WslShellExecutor extends LocalBashExecutor {
    * @returns an absolute path to the shell inside the distro.
    */
   async shellName() {
-  	// Consumed by the shell tool after upstream change A: it names and describes
-  	// itself from the executor, so a zsh distro is never presented as bash.
-  	const shell = await this.shell();
-  	const base = String(shell ?? "").split("/").pop() ?? "";
-  	const name = base.replace(/\.exe$/i, "").replace(/^[-.]+/, "");
-  	return /^[a-z0-9_+-]+$/i.test(name) ? name : "bash";
+    // Consumed by the shell tool after upstream change A: it names and describes
+    // itself from the executor, so a zsh distro is never presented as bash.
+    const shell = await this.shell();
+    const base = String(shell ?? "").split("/").pop() ?? "";
+    const name = base.replace(/\.exe$/i, "").replace(/^[-.]+/, "");
+    return /^[a-z0-9_+-]+$/i.test(name) ? name : "bash";
   }
 
   async shell() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-wsl-env",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Run a DeepSeek Harness session against a WSL distro: a ctx.shell executor that runs commands inside the distro and a ctx.fs backend over its UNC share",
   "keywords": [
     "deepseek-harness",
@@ -36,12 +36,18 @@
     "README.md",
     "docs/README.zh.md",
     "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "SECURITY.md",
+    "SUPPORT.md",
     "LICENSE"
   ],
   "scripts": {
-    "test": "npm run test:syntax && npm run test:unit",
+    "test": "npm run lint:style && npm run test:syntax && npm run test:unit",
+    "test:coverage": "node --test --experimental-test-coverage --test-coverage-lines=85 --test-coverage-branches=85 --test-coverage-functions=70 test/paths.test.mjs test/listing.test.mjs test/shell.test.mjs test/terminal.test.mjs",
     "test:syntax": "node test/syntax.mjs",
     "test:unit": "node --test test/paths.test.mjs test/listing.test.mjs test/shell.test.mjs test/terminal.test.mjs",
+    "lint:style": "node test/style.mjs",
+    "prepublishOnly": "npm test",
     "probe": "bash test/probe/run.sh",
     "probe:terminal": "bash test/probe/terminal.sh",
     "probe:sandbox": "bash test/probe/sandbox.sh",
@@ -51,7 +57,14 @@
   "engines": {
     "node": ">=20"
   },
-  "packageManager": "pnpm@11.7.0",
+  "author": {
+    "name": "Andy Zhao",
+    "url": "https://github.com/Big-Dao"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
+  },
   "license": "MIT",
   "repository": {
     "type": "git",