The integration tests load the real plugin module against a thin mock Cordis
context and drive the tool through a real shell into the real slopo binary. The
mock implements only the seams the plugin touches, so a wrong assumption about a
dsh service fails a test instead of producing a plugin that silently does
nothing at runtime.
Two real bugs were caught this way and are now pinned:
* renderSlopoConfig would write the embedding API key to disk if it were
handed one. It cannot now.
* --config-version was placed before the subcommand, which slopo rejects with
exit code 2. It is declared on the command, not the callback.
The end-to-end test is opt-in (DSH_SLOPO_E2E=1) because it needs a reachable
embedding backend; it indexes a real repository, embeds it, and asserts a real
duplicate cluster comes back.
42 lines
867 B
JSON
42 lines
867 B
JSON
{
|
|
"name": "dsh-slopo",
|
|
"version": "0.1.0",
|
|
"private": true,
|
|
"type": "module",
|
|
"description": "Slopo as a DeepSeek Harness bundle — embedding-based duplicate-code review, exposed as three user-triggered skills and one config-aware tool.",
|
|
"main": "index.js",
|
|
"files": [
|
|
"index.js",
|
|
"lib",
|
|
"skills",
|
|
"cordis.patch.yml",
|
|
"README.md",
|
|
"NOTICE.md",
|
|
"LICENSE"
|
|
],
|
|
"engines": {
|
|
"node": ">=20"
|
|
},
|
|
"scripts": {
|
|
"test": "node --test test/*.test.js"
|
|
},
|
|
"dsh": {
|
|
"bundle": {
|
|
"patch": "./cordis.patch.yml"
|
|
}
|
|
},
|
|
"keywords": [
|
|
"dsh-plugin",
|
|
"deepseek-harness",
|
|
"cordis",
|
|
"slopo",
|
|
"duplicate-code",
|
|
"code-embeddings"
|
|
],
|
|
"license": "AGPL-3.0-or-later",
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "git+https://git.notexpectedyet.com/Not-Expected-Yet/dsh-slopo.git"
|
|
}
|
|
}
|