@perrylink/dsh-test-kit 0.0.0-stage → 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,70 @@
+# Changelog — dsh-test-kit
+
+## 0.1.0 (unreleased)
+
+First implementation of the standalone kit. The source now lives in its own
+repository, `PerryLink/dsh-test-kit`. **Not published and not tagged**; npm
+publication and release tags require explicit owner approval.
+
+### Added
+
+- `dsh-test-kit run <target>`: drives `github:`, `git+https`, `npm:`, local
+  path, and `.tgz` targets through the extracted `dsh-test-drive` engine
+  (install → patch check → boot smoke → uninstall → cleanup) in a throwaway
+  `DSH_HOME`, and writes the frozen `schema: "dsh-test-drive/v1"` JSON record.
+- `dsh-test-kit render --input <json> --out-dir <dir>`: validates the record and
+  emits Markdown (PR comment) and JUnit XML; rejects placeholder/invalid JSON.
+- `node:child_process` subprocess adapter (`src/subprocess.ts`) implementing the
+  engine's subprocess seam outside DSH: PATH/PATHEXT resolution, scrubbed
+  parent env, tail-bounded collected output, abort → tree termination.
+- Composite `action.yml`: install/build kit → run with `--no-fail` → render →
+  enforce `pass` (with `fail`/`unknown` always failing, `partial` opt-in).
+- Standalone extraction: `src/core/` (10 engine modules) lives in this
+  repository; imports are package-relative (`./core/...`), with no monorepo
+  path or `@deepseek-ai/*` runtime dependency. CLI/subprocess tests moved to
+  `tests/` and run with plain `npm test`.
+- `.github/workflows/ci.yml`: Ubuntu/Windows on Node 22 and 24, a dedicated
+  `macos-latest` job (Node 24), and a composite-action end-to-end job.
+- Exit codes by verdict: 0 pass, 1 fail, 2 partial, 3 unknown.
+
+### Fixed in P0 verification
+
+- **Boot verdicts are honest.** `pass` now requires `smoke.status=pass` with exit 0 (or an explicitly skipped smoke from an empty task). `boot-ok` (non-zero exit) is `partial`, and `Cannot find module` / `Cannot find package` / `ERR_MODULE_NOT_FOUND` are boot-failure markers → `fail`. The `dsh-todo@0.1.0` real boot crash is no longer reported as pass.
+- **Published package is self-contained.** A clean standalone checkout resolved `zod` from outside the package and emitted a 105 KB externalized bundle. The build now aliases `zod` via `import.meta.resolve`, `verify-build.mjs` fails the build unless zod is bundled, and `zod` is also declared as a dependency. `npm pack` + bare install runs.
+- **Empty headless-task no longer defaults to partial.** The action's default (empty task → `--no-smoke`) yields `pass` from install/patch/uninstall; only an explicit config skip is accepted as a pass.
+- **Empty/unknown matrices are failures.** Empty matrix → `unknown`, with a synthetic JUnit `empty-matrix` failure; `unknown` rows and the overall drive verdict are counted as JUnit failures.
+- **CI gates** now build/typecheck/test/verify/pack the kit and run the composite action against a scripted `dsh` (default empty task must pass).
+
+### Fixed in P2 verification
+
+- **`render` cannot publish a green report over failed stages.** A record that
+  claims `verdict: pass` while its own stages say `fail` now renders the
+  stage-derived verdict (including a corrected `verdictReason`) and exits `1`
+  instead of `0`. Contradictions with partial/inconclusive evidence exit `2`/`3`
+  respectively. Regression test: `tests/cli.spec.ts` forges `pass` over a failed
+  install and asserts exit `1` plus a `fail` report.
+- **Windows JS/ESM `--dsh` entries run.** A `.js`/`.mjs`/`.cjs` executable is
+  launched through `node` on Windows (direct `CreateProcess` fails with
+  `EFTYPE`), so the scripted test dsh and JS-entry deployments work there.
+  Aborted runs settle with `exitCode: null` on Windows too (the `taskkill /F`
+  path used to surface exit `1`).
+- **Cross-platform test suite is green locally.** `npm test` passes 30/30 on
+  Linux and on Windows (Node 24); macOS is covered by the `macos-latest` CI
+  job because no macOS hardware was available for the extraction.
+
+### Changed in the shared engine
+
+- Engine modules moved to `src/core/` and re-exported from their original
+  paths, so the existing `dsh-test-drive` public API and tests remain valid.
+- The subprocess seam is structural (`DriverSubprocessService`) instead of a
+  `@deepseek-ai/*` type, and `resolveConfig` no longer imports Schemastery;
+  the plugin still exports the loader-facing Schemastery `Config` schema.
+- `classifyTarget` recognizes the explicit `npm:` registry form and the drive
+  strips the marker before `dsh plugin add`.
+
+### Not done (needs owner approval or a later release)
+
+- npm publish, git tag, GitHub release, announcements (owner action).
+- Batch/matrix CLI, multi-target runs, capability-credential automation.
+- macOS was not available on the extraction host; the `macos-latest` CI job is
+  the verification path.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,317 @@
-# Temporary Holding Version
+# dsh-test-kit
 
-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.
+[![ci](https://github.com/PerryLink/dsh-test-kit/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/PerryLink/dsh-test-kit/actions/workflows/ci.yml)
+
+**Run a DeepSeek Harness plugin's install-and-smoke check outside DeepSeek Harness.**
+
+`dsh-test-kit` is the standalone home of the extracted `dsh-test-drive` engine.
+It installs a target into a throwaway `DSH_HOME` profile, verifies that the
+bundle patch layer actually mounted, runs a keyless boot smoke, uninstalls the
+package, cleans up every directory it owns, and writes the frozen
+`dsh-test-drive/v1` JSON record plus Markdown and JUnit reports.
+
+This repository is self-contained: `src/core/` lives here, no monorepo checkout,
+no `@deepseek-ai/*` runtime import, and no DSH host process are required. The
+only things a drive needs are the `dsh` CLI, pnpm, and network access for the
+throwaway profile's install.
+
+- **Starts with plain Node.** The CLI bundles `zod`; a clean checkout boots with
+  `node lib/cli.js --version`.
+- **Never reports success for unknown output.** Missing or invalid JSON is
+  rejected; `fail`, `partial`, and `unknown` all have non-zero exit codes.
+- **`boot-ok` is not `pass`.** A non-zero boot without loader-failure markers is
+  `partial`; `pass` requires a real boot (`smoke.status=pass`, exit 0) or an
+  explicitly skipped smoke.
+- **Isolation by construction.** Throwaway `DSH_HOME`, throwaway cwd, redirected
+  pnpm store; the host profile is never read or written.
+- **Sanitized reports.** Token literals, URL credentials, bearer headers, and
+  temp paths are redacted before any string reaches a report.
+
+## Status
+
+- **Source of truth:** this repository. The package was extracted from the
+  `dsh-test-drive` monorepo into a self-contained `src/` + `src/core/` tree.
+- **npm:** not published by this repository yet. Publication is handled by the
+  owner; until then, build from source or use the GitHub Action.
+- **Schema:** frozen at `schema: "dsh-test-drive/v1"`. The kit does not add
+  fields, so existing scorers and dashboards keep working.
+- **macOS:** verified in GitHub-hosted CI (`macos-latest`, Node 24). The
+  extraction host has no macOS hardware, so the local macOS run is **BLOCKED**;
+  the `macos-latest` Actions job is the authoritative macOS result.
+
+## Requirements
+
+| Requirement | Notes |
+|---|---|
+| Node.js | `^22.19.0` or `>=24.9.0` |
+| `dsh` CLI | any 0.2.x build that provides `plugin add` and `--dump-config`; pass `--dsh <path>` or put `dsh` on `PATH` |
+| Network | only for the throwaway profile's pnpm install |
+| pnpm | the `dsh plugin` manager uses its own pnpm; a working registry is required |
+
+## Install
+
+Once the owner publishes the package:
+
+```sh
+npm install -g @perrylink/dsh-test-kit
+dsh-test-kit --version
+```
+
+Until then, build the standalone checkout:
+
+```sh
+git clone https://github.com/PerryLink/dsh-test-kit.git
+cd dsh-test-kit
+npm ci
+npm run build
+node lib/cli.js --version
+```
+
+`lib/cli.js` is a single self-contained ESM entry (zod bundled); the build fails
+if zod is externalized or the frozen schema string is missing.
+
+## Quick start
+
+```sh
+# A GitHub ref (the checkout/pack path plugin authors actually ship)
+dsh-test-kit run github:owner/repo#<sha> --dsh /path/to/dsh --json out.json
+
+# A published plugin
+dsh-test-kit run npm:dsh-score@0.2.28 --dsh /path/to/dsh --json out.json
+
+# A local checkout or tarball
+dsh-test-kit run ./my-plugin --json out.json
+dsh-test-kit run ./my-plugin.tgz --json out.json
+
+# Render the CI report pair from the settled record
+dsh-test-kit render --input out.json --out-dir reports
+```
+
+`render` writes `reports/out.md` (PR comment body) and
+`reports/out.junit.xml` (test reporter input), then prints one JSON line with
+the absolute paths and the verdict.
+
+## Targets
+
+| Form | Example | Notes |
+|---|---|---|
+| GitHub ref | `github:owner/repo#<sha>` | passed to `dsh plugin add` |
+| git URL | `git+https://host/repo.git#ref` | any pnpm-supported git spec |
+| npm registry | `npm:name`, `npm:@scope/name@1.2.3` | the `npm:` marker is stripped before install |
+| local path | `./plugin`, `/abs/plugin` | anchored at the invoking directory |
+| tarball | `./plugin.tgz` | packed plugin |
+
+## The result record
+
+```json
+{
+  "schema": "dsh-test-drive/v1",
+  "run": { "runId": "tdr_…", "harnessVersion": "0.2.2-rc.3", "pluginVersion": "0.1.0", "…": "…" },
+  "target": { "kind": "npm", "spec": "dsh-score@0.2.28", "resolved": { "packageName": "dsh-score", "packageVersion": "0.2.28", "hasBundleManifest": true } },
+  "stages": {
+    "install":   { "status": "pass", "…": "…" },
+    "config":    { "status": "pass", "patchEffective": true, "layers": ["dsh-score"], "…": "…" },
+    "smoke":     { "status": "boot-ok", "bootFailed": false, "taskCompleted": false, "…": "…" },
+    "uninstall": { "status": "pass", "…": "…" },
+    "cleanup":   { "status": "pass", "quarantined": true, "removed": true, "…": "…" }
+  },
+  "verdict": "partial",
+  "verdictReason": "install, patch, and uninstall verified; boot smoke exited 1 without loader-failure markers, so a successful boot is not proven"
+}
+```
+
+`verdict=pass` requires `smoke.status=pass` with exit 0, or an explicitly
+skipped smoke. A non-zero boot (`boot-ok`) is **always** `partial`. An empty
+matrix is `unknown`, never `pass`.
+
+### Verdicts
+
+| Verdict | Meaning | `run` exit code |
+|---|---|---|
+| `pass` | install, patch layer, and uninstall verified, plus either a real boot (`smoke.pass` with exit 0) or an explicitly skipped smoke (empty task / `--no-smoke`) | 0 |
+| `fail` | install failed, boot found loader failures (including `Cannot find module`), or a capability assertion failed | 1 |
+| `partial` | install passed but the patch/boot/uninstall could not be fully verified; `boot-ok` (non-zero exit) is always here | 2 |
+| `unknown` | the stage combination has no conclusive rule (typically install never ran) | 3 |
+
+## `render` integrity rules (P2 fix)
+
+`render` re-folds the verdict from the record's own stages before writing a
+report. A record that **claims `pass` while its stages say otherwise** is never
+rendered as green:
+
+- any failed stage (`install`, `config`, `smoke`, `capability`, `uninstall`, or
+  `cleanup`) → report shows the stage-derived `fail`, exit **1**;
+- partial evidence such as `patchEffective: false` → report shows `partial`,
+  exit **2**;
+- inconclusive evidence → `unknown`, exit **3**.
+
+Exit codes for `render` are therefore:
+
+| Code | Meaning |
+|---|---|
+| `0` | reports written from a consistent record |
+| `1` | record claimed `pass` but a stage is `fail` |
+| `2` | record claimed `pass` but the stage evidence is `partial` |
+| `3` | record claimed `pass` but the stage evidence is inconclusive |
+| `64` | usage error |
+| `65` | input is not a `dsh-test-drive/v1` record (including placeholder JSON) |
+
+Placeholder JSON such as `{"note":"replace this step"}` is **rejected**, never
+rendered as a success.
+
+### What the stages actually check
+
+1. **install** — `dsh plugin --profile <name> add <target>` in the throwaway
+   home. A pnpm `allowBuilds` gate hit on a git source is allowlisted and
+   retried once.
+2. **config** — `dsh --profile <name> --dump-config`; the installed package must
+   appear as a layer or a row. Install success alone is not enough.
+3. **smoke** — one headless invocation. Exit 0 with no loader-failure markers
+   is `pass`; a non-zero exit **is not a verified boot** and yields `boot-ok`
+   → verdict `partial`; loader/module failures (`Cannot find module` etc.) make
+   it `fail`. An empty task skips the stage entirely (install/patch/uninstall
+   still yield `pass`).
+4. **capability** (optional) — prove one named tool/command is registered,
+   invoked, and observed in the durable session log. Needs a model credential
+   forwarded explicitly; otherwise the stage is `skipped`, not failed.
+5. **uninstall / cleanup** — remove the package and always run the owned
+   quarantine → delete ladder, including on abort and pipeline errors.
+
+## GitHub Action
+
+The action lives at the repository root; reference `@main` until a release tag
+exists:
+
+```yaml
+name: test-drive
+on: [pull_request, workflow_dispatch]
+jobs:
+  smoke:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install the dsh CLI (or use your own cache)
+        run: npm install -g @deepseek-ai/dsh@0.2.2-rc.3
+      - name: Drive this plugin
+        id: drive
+        uses: PerryLink/dsh-test-kit@main
+        with:
+          target: github:${{ github.repository }}#${{ github.sha }}
+          # Optional: headless-task: 'Reply with exactly: ok'
+          # Optional: dsh: /usr/local/bin/dsh
+      - name: Publish JUnit
+        uses: EnricoMi/publish-unit-test-result-action@v2
+        with:
+          files: ${{ steps.drive.outputs.junit }}
+      - name: Comment the report
+        run: cat "${{ steps.drive.outputs.markdown }}"
+```
+
+| Input | Default | Purpose |
+|---|---|---|
+| `target` | — (required) | same target forms as the CLI |
+| `headless-task` | `''` | empty skips the smoke stage |
+| `dsh` | `dsh` | absolute path, bare command, or `npm:<pkg>@<version>` |
+| `node-version` | `24` | Node used by the kit |
+| `kit-version` | `latest` | only used when the checkout has no local kit |
+| `allow-partial` | `false` | `partial` passes only when explicitly allowed |
+
+Outputs: `markdown`, `junit`, `verdict`, `result`.
+
+The action installs/builds the kit, runs the drive with `--no-fail`, validates
+and renders the record, then **fails the job on `fail` or `unknown`** (and on
+`partial` unless `allow-partial: true`). It never substitutes a placeholder
+result.
+
+## Security model
+
+- **Owned temp roots only.** Every directory is created with `mkdtemp` under the
+  OS temp dir with the `dsh-test-drive-` prefix, registered, and removed through
+  the dry-run → quarantine-rename → delete ladder. `assertOwned` refuses
+  anything else.
+- **Throwaway profile.** The child gets `DSH_HOME=<owned root>/home`, a
+  throwaway cwd, and `npm_config_store_dir=<owned root>/store`. The real
+  `~/.dsh` is never read or written; the record asserts
+  `isolation.hostHomeTouched: false`.
+- **No implicit secrets.** The adapter starts from the parent environment minus
+  credential-shaped names (`/KEY|PASSWORD|SECRET|TOKEN/i`) and all `DSH_*`
+  names; only values named with `--forward-env` survive.
+- **Sanitized output.** Every report string passes the engine sanitizers; stage
+  output is byte-capped and temp paths are redacted.
+
+## Source layout
+
+```
+src/core/                  self-contained engine (10 modules)
+  config.ts                defaults + fail-loud resolveConfig (no Schemastery)
+  driver.ts                dsh location, argv-only spawning, allowBuilds, dump parsing
+  drive.ts                 install → config → smoke → capability → uninstall → cleanup
+  result.ts                frozen zod schema + verdictOf
+  report.ts                Markdown + JUnit renderers
+  workspace.ts             owned temp roots, quarantine ladder
+  capability.ts            session-log capability analyzer
+  session-log.ts           multi-frame zstd session reader
+  sanitize.ts              secret/temp-path redaction
+  version.ts               engine version
+
+src/cli.ts                 run / render, argument parsing, exit codes
+src/subprocess.ts          node:child_process adapter for the engine seam
+action.yml                 composite GitHub Action
+lib/cli.js                 built single-file bundle (committed so the Action needs no build)
+tests/                     CLI + subprocess specs and the scripted fake dsh
+```
+
+Dependency direction is one-way: the CLI imports the engine, the engine imports
+nothing from DSH (type-only seams live in `driver.ts`), and only
+`subprocess.ts` starts processes. That is what makes `dsh-test-kit run` startable
+with plain Node.
+
+## Development
+
+```sh
+npm ci
+npm run typecheck      # tsc --noEmit over src/ and tests/
+npm test               # vitest: CLI + subprocess specs
+npm run build          # tsdown bundle + self-contained bundle guard
+npm run verify         # verify lib/cli.js bundles zod and the frozen schema
+node lib/cli.js run npm:dsh-score@0.2.28 --json /tmp/out.json
+node lib/cli.js render --input /tmp/out.json --out-dir /tmp/reports
+```
+
+The tests use a scripted `dsh` (`tests/fixtures/fake-dsh.mjs`), so the full
+run → JSON → render loop is exercised without a network install. The P2
+regression test forges `verdict: pass` over a failed install and asserts
+`render` exits `1` and writes a `fail` report.
+
+## CI
+
+`.github/workflows/ci.yml` runs `npm ci`, typecheck, tests, build, and
+`node lib/cli.js --version` on:
+
+| Job | Runner | Node |
+|---|---|---|
+| `test` | `ubuntu-latest`, `windows-latest` | 22, 24 |
+| `macos` | `macos-latest` | 24 |
+| `action` | `ubuntu-latest` | 24 |
+
+The `action` job runs this repository's composite action end-to-end against the
+scripted `dsh` and asserts a `pass` verdict. The `macos` job exists because the
+extraction host has no macOS hardware (local macOS run: BLOCKED); CI is the
+authoritative macOS check.
+
+## v0.1 limits
+
+- One target per `run`; batch matrices are still a plugin-only feature
+  (`/testdrive` + `drive-batch`).
+- The smoke stage is keyless by default; forwarding a model credential is
+  always an explicit `--forward-env` decision.
+- Windows: the adapter refuses to spawn `.cmd`/`.bat`/`.ps1` shims directly (no
+  shell). Pass a `.exe`, or a JS/ESM entry (`.js`/`.mjs`/`.cjs`) — JS entries are
+  launched through `node`.
+- `--dsh npm:<pkg>@<version>` uses `npm exec --package=… -- dsh`; npm must be
+  resolvable as a JS entry (the adapter locates `npm-cli.js`).
+- No git tag or npm release is created by this repository yet.
+
+## License
+
+Apache-2.0. The bundled `zod` is MIT; see [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,23 @@
+# Third-party notices — dsh-test-kit
+
+`dsh-test-kit` is Apache-2.0. Its source is derived from the `dsh-test-drive`
+engine (same author, Apache-2.0).
+
+## Bundled at build time
+
+The published `lib/cli.js` bundles the following package so the CLI has no
+runtime npm dependencies:
+
+| Package | Version | License | Use |
+|---|---|---|---|
+| [`zod`](https://github.com/colinhacks/zod) | 4.6.6 | MIT | frozen result-schema validation |
+
+The MIT notice of `zod` is reproduced by the package's own `LICENSE` file in
+the npm tarball of `zod`; its copyright notice is:
+
+```
+Copyright (c) 2020 Colin Hacks
+```
+
+No other third-party code is bundled. `node:child_process`, `node:fs`,
+`node:path`, and the other `node:` builtins are part of Node.js.