dsh-research-suite-plugin 0.0.0-stage → 0.1.4

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/CHANGELOG.md ADDED
@@ -0,0 +1,39 @@
1
+ # Changelog
2
+
3
+ ## [0.1.4] - 2026-11-20
4
+
5
+ ### Changed
6
+
7
+ - Publish under the bare npm name dsh-research-suite-plugin.
8
+
9
+
10
+ ## [0.1.3] - 2026-11-20
11
+
12
+ ### Changed
13
+
14
+ - Publish under the bare npm name dsh-research-suite-plugin (the name must keep the dsh prefix).
15
+
16
+
17
+ ## [0.1.2] - 2026-11-20
18
+
19
+ ### Changed
20
+
21
+ - Publish under the bare npm name dsh-research-suite-plugin (the scoped name was retired from the release path).
22
+
23
+
24
+ All notable changes to this project are documented here. The format follows
25
+ [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
26
+ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
27
+
28
+ ## [0.1.0] - 2026-11-10
29
+
30
+ ### Added
31
+
32
+ - `dsh-research-suite-plugin`: one bundle layer for `dsh-research-core`,
33
+ `dsh-doc-anchor`, `dsh-cite-verify`, `dsh-claim-check`, `dsh-statcheck`,
34
+ `dsh-retraction-watch`, `dsh-repro-audit`, `dsh-sr-ledger`,
35
+ `dsh-meta-analysis`, `dsh-manuscript-check`, `dsh-research-report` and
36
+ `dsh-library`.
37
+ - `research_doctor`: read-only REP inspection (root, mounted services, journal
38
+ line/malformed counts, sealed-record count and latest record, actionable
39
+ hints). It never repairs or writes.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README-zh.md ADDED
@@ -0,0 +1,90 @@
1
+ # dsh-research-suite-plugin
2
+
3
+ **一条命令装好科研插件族 —— 再加一个体检工具,告诉你证据库是否健康。**
4
+
5
+ *把证据、核验、系统综述与报告插件作为一个 bundle 层安装,并挂载 `research_doctor`:只读检查 REP 根、已挂载的服务、每个 journal,以及最新一条密封记录。*
6
+
7
+ [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
8
+ [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24.9-brightgreen.svg)]()
9
+ [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
10
+
11
+ [English](README.md) · 简体中文
12
+
13
+ ---
14
+
15
+ ## 为什么要 bundle
16
+
17
+ 科研族是刻意拆开的独立包:`dsh-research-core`、`dsh-doc-anchor`、`dsh-cite-verify`、`dsh-claim-check`、`dsh-statcheck`、`dsh-retraction-watch`、`dsh-repro-audit`、`dsh-sr-ledger`、`dsh-meta-analysis`、`dsh-manuscript-check`、`dsh-research-report` 与 `dsh-library`。这对组合有利,对上手不利:新 profile 要装十二次,而且装完不知道行有没有真的挂上。
18
+
19
+ 这个包就是那套东西的 **bundle**:一棵依赖树、一个 `cordis.patch.yml`、一行 `research_doctor`。它不重新实现任何工具。
20
+
21
+ ## 安装
22
+
23
+ ```sh
24
+ dsh plugin --profile <name> add dsh-research-suite-plugin
25
+ dsh --profile <name> --dump-config | grep -E 'research|cite-verify|doc-anchor|statcheck|claim-check|sr-ledger|meta-analysis|manuscript|retraction|repro-audit|library'
26
+ ```
27
+
28
+ 然后对 agent 说:
29
+
30
+ ```text
31
+ Run research_doctor.
32
+ ```
33
+
34
+ 健康的 profile 会报告 `research_doctor: ok`、两个服务都 `on`,最新记录带 `(sealed)`。
35
+
36
+ ## `research_doctor` 检查什么
37
+
38
+ | 检查 | 含义 |
39
+ |---|---|
40
+ | `services.researchEvidence` | `ctx.researchEvidence` 已挂载(core 生效) |
41
+ | `services.researchReport` | `ctx.researchReport` 已挂载(`dsh-research-report` 生效) |
42
+ | `journals[]` | `snapshots/evidence/evidence-checks/claims/verdicts/audits.jsonl`:是否存在、字节数、行数、坏行数 |
43
+ | `records` | 密封的 `records/*.rep.json` 数量、坏文件数、最新记录的 id/createdAt/evidence/claims/sealed |
44
+ | `hints[]` | 下一步该修什么(没有根、没有记录、记录未密封、journal 坏行、服务缺失) |
45
+
46
+ 它是**只读**的:不修复、不删除、不改写、不创建记录。journal 有坏行时状态是 `error`,因为由它推导出的每个计数都不可信;根不存在只是 `warn`(新 profile 本来就没有记录)。
47
+
48
+ ## 兼容性
49
+
50
+ | | |
51
+ |---|---|
52
+ | DeepSeek Harness | `dsh-v0.2.2-rc.4`(本机实测)—— peer 区间 `>=0.2.1-0 <0.3.0 \|\| >=0.2.2-0 <0.3.0` |
53
+ | Node | `^22.19.0 \|\| >=24.9.0`(实测 `24.22.1`),仅 ESM |
54
+ | Peers | `@deepseek-ai/cordis ^4.0.5-alpha.1`、`@deepseek-ai/dsh-tools`、`@deepseek-ai/schemastery ^3.18.5-alpha.1` |
55
+ | 运行时依赖 | 十二个科研插件(固定版本) |
56
+ | 存储 | `.research-rep`(与 `dsh-research-core` 默认一致) |
57
+
58
+ ## 配置
59
+
60
+ | 键 | 默认 | 含义 |
61
+ |---|---|---|
62
+ | `enabled` | `true` | `false` 不挂载 doctor 工具(其他行不变) |
63
+ | `root` | `.research-rep` | doctor 读取的 REP 根,相对 harness 工作目录解析 |
64
+ | `maxScanBytes` | `16777216` | 单文件扫描上限;更大的文件只计数、不解析 |
65
+
66
+ doctor 也接受单次调用的 `root` 覆盖。
67
+
68
+ ## 它不做什么
69
+
70
+ - **除了 doctor 没有自己的工具。** 证据、核验、报告工具都属于各自的插件。
71
+ - **不自动修复。** journal 坏了只报告,不重写。
72
+ - **不联网、不埋点。** doctor 只读本地文件与 `ctx.get`。
73
+ - **不偷偷安装。** bundle 就是普通的包依赖树,按普通插件卸载即可。
74
+
75
+ ## 开发
76
+
77
+ ```sh
78
+ pnpm install
79
+ pnpm run check:lockfile
80
+ pnpm typecheck
81
+ pnpm test
82
+ pnpm build
83
+ pnpm verify:package
84
+ ```
85
+
86
+ 锁文件按 `pnpm install --lockfile-only` 的原样提交(两段:pnpm 自身的管理文档 + 项目文档),本地 `pnpm install` 不会改写它;`pnpm run check:lockfile` 在它与 `package.json` 不一致或丢失该形式时失败。
87
+
88
+ ## 许可
89
+
90
+ Apache-2.0,见 [LICENSE](LICENSE)。
package/README.md CHANGED
@@ -1,3 +1,90 @@
1
- # Temporary Holding Version
1
+ # dsh-research-suite-plugin
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
+ **One command for the research family — plus a doctor that tells you whether the evidence store is healthy.**
4
+
5
+ *Installs the evidence, verification, systematic-review and report plugins as one bundle layer, and mounts `research_doctor`: a read-only check of the REP root, the mounted services, every journal and the latest sealed record.*
6
+
7
+ [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
8
+ [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24.9-brightgreen.svg)]()
9
+ [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
10
+
11
+ English · [简体中文](README-zh.md)
12
+
13
+ ---
14
+
15
+ ## Why a bundle
16
+
17
+ The research family is deliberately separate packages: `dsh-research-core`, `dsh-doc-anchor`, `dsh-cite-verify`, `dsh-claim-check`, `dsh-statcheck`, `dsh-retraction-watch`, `dsh-repro-audit`, `dsh-sr-ledger`, `dsh-meta-analysis`, `dsh-manuscript-check`, `dsh-research-report` and `dsh-library`. That is good for composition and bad for onboarding: a new profile needs twelve installs and a way to tell whether the rows actually mounted.
18
+
19
+ This package is the **bundle** for that set. One dependency tree, one `cordis.patch.yml`, one `research_doctor` row. It does not re-implement any tool.
20
+
21
+ ## Install
22
+
23
+ ```sh
24
+ dsh plugin --profile <name> add dsh-research-suite-plugin
25
+ dsh --profile <name> --dump-config | grep -E 'research|cite-verify|doc-anchor|statcheck|claim-check|sr-ledger|meta-analysis|manuscript|retraction|repro-audit|library'
26
+ ```
27
+
28
+ Then ask the agent:
29
+
30
+ ```text
31
+ Run research_doctor.
32
+ ```
33
+
34
+ A healthy profile reports `research_doctor: ok`, both services `on`, and the latest record as `(sealed)`.
35
+
36
+ ## What `research_doctor` checks
37
+
38
+ | Check | Meaning |
39
+ |---|---|
40
+ | `services.researchEvidence` | `ctx.researchEvidence` is mounted (core active) |
41
+ | `services.researchReport` | `ctx.researchReport` is mounted (`dsh-research-report` active) |
42
+ | `journals[]` | `snapshots/evidence/evidence-checks/claims/verdicts/audits.jsonl`: exists, bytes, lines, malformed |
43
+ | `records` | sealed `records/*.rep.json` count, malformed files, latest record id/createdAt/evidence/claims/sealed |
44
+ | `hints[]` | what to fix next (missing root, no record, unsealed record, malformed journal, missing service) |
45
+
46
+ It is **read-only**. It never repairs, deletes, edits or creates a record. A malformed journal makes the status `error` because every count derived from it would be unreliable; a missing store is only `warn` (a fresh profile has no records yet).
47
+
48
+ ## Compatibility
49
+
50
+ | | |
51
+ |---|---|
52
+ | DeepSeek Harness | `dsh-v0.2.2-rc.4` (verified on this machine) — peer line `>=0.2.1-0 <0.3.0 \|\| >=0.2.2-0 <0.3.0` |
53
+ | Node | `^22.19.0 \|\| >=24.9.0` (tested on `24.22.1`), ESM only |
54
+ | Peers | `@deepseek-ai/cordis ^4.0.5-alpha.1`, `@deepseek-ai/dsh-tools`, `@deepseek-ai/schemastery ^3.18.5-alpha.1` |
55
+ | Runtime dependencies | the twelve research plugins (pinned) |
56
+ | Store | `.research-rep` (same default as `dsh-research-core`) |
57
+
58
+ ## Configuration
59
+
60
+ | Key | Default | Meaning |
61
+ |---|---|---|
62
+ | `enabled` | `true` | `false` mounts no doctor tool (the other rows stay) |
63
+ | `root` | `.research-rep` | REP root the doctor reads, resolved against the harness working directory |
64
+ | `maxScanBytes` | `16777216` | per-journal/file scan cap; larger files are counted but not parsed |
65
+
66
+ The doctor also accepts a per-call `root` override.
67
+
68
+ ## What this package does not do
69
+
70
+ - **No tools of its own beyond the doctor.** All evidence/verification/report tools belong to their plugins.
71
+ - **No automatic repair.** A malformed journal is reported, never rewritten.
72
+ - **No telemetry, no network.** The doctor reads local files and `ctx.get`.
73
+ - **No hidden install.** The bundle is a normal package dependency tree; uninstall it like any other plugin.
74
+
75
+ ## Development
76
+
77
+ ```sh
78
+ pnpm install
79
+ pnpm run check:lockfile
80
+ pnpm typecheck
81
+ pnpm test
82
+ pnpm build
83
+ pnpm verify:package
84
+ ```
85
+
86
+ The lockfile is committed exactly as `pnpm install --lockfile-only` writes it (two documents: pnpm's own package-manager document, then the project document), so a local install does not rewrite it. `pnpm run check:lockfile` fails when the lockfile drifts from `package.json` or loses that form.
87
+
88
+ ## License
89
+
90
+ Apache-2.0. See [LICENSE](LICENSE).
package/SECURITY.md ADDED
@@ -0,0 +1,31 @@
1
+ # Security
2
+
3
+ ## Scope
4
+
5
+ `dsh-research-suite-plugin` is a bundle plus one read-only tool. It declares
6
+ the twelve research plugins as dependencies and mounts `research_doctor`; it
7
+ re-implements no tool.
8
+
9
+ - **Read-only doctor.** `research_doctor` reads the configured REP root, the
10
+ mounted services, the journal files and the latest sealed record. It writes
11
+ nothing and deletes nothing.
12
+ - **No network.** The package opens no sockets and reads no environment
13
+ secrets.
14
+ - **Bounded scanning.** Journal and record reads are capped (`maxBytes` /
15
+ scan limits), and a malformed journal is reported as an error instead of being
16
+ silently counted.
17
+ - **The tools stay in their own packages.** `cite_verify`, `claim_check`,
18
+ `lit_search`, `repro_audit`, `dmp`, … are provided by the dependency packages
19
+ and documented in their own SECURITY files. This package grants no additional
20
+ capability.
21
+
22
+ ## Supported versions
23
+
24
+ The latest published `0.1.x` release receives security fixes.
25
+
26
+ ## Reporting a vulnerability
27
+
28
+ Please use GitHub's private vulnerability reporting (Security → Advisories) on
29
+ <https://github.com/PerryLink/dsh-research-suite>, or open a minimal issue
30
+ asking for a private channel if advisories are unavailable. Do not include
31
+ credentials, personal data or unpublished manuscripts in a public issue.
@@ -0,0 +1,30 @@
1
+ # Third-party notices
2
+
3
+ ## Runtime code
4
+
5
+ This package bundles no third-party source code. It is a bundle: its runtime
6
+ dependencies are twelve PerryLink research plugins, all Apache-2.0 and all
7
+ published from the same family:
8
+
9
+ `@perrylink/dsh-claim-check`, `@perrylink/dsh-research-core`,
10
+ `dsh-cite-verify`, `dsh-doc-anchor`, `dsh-library`, `dsh-manuscript-check`,
11
+ `dsh-meta-analysis`, `dsh-repro-audit`, `dsh-research-report`,
12
+ `dsh-retraction-watch`, `dsh-sr-ledger`, `dsh-statcheck`.
13
+
14
+ Their only third-party runtime dependency is [`zod`](https://github.com/colinhacks/zod)
15
+ `4.4.3` (MIT), reached transitively through `dsh-library`. The rest of the
16
+ family declares no runtime dependencies.
17
+
18
+ `@deepseek-ai/cordis`, `@deepseek-ai/dsh-tools` and `@deepseek-ai/schemastery`
19
+ are peer dependencies provided by the host runtime; they are not bundled in
20
+ this package's tarball.
21
+
22
+ ## Development-only tooling
23
+
24
+ TypeScript, Vitest and `@types/node` are development dependencies. They are not
25
+ bundled and are not part of the published tarball.
26
+
27
+ ## License
28
+
29
+ `dsh-research-suite-plugin` is licensed under Apache-2.0. See
30
+ [LICENSE](LICENSE).
@@ -0,0 +1,34 @@
1
+ # dsh-research-suite bundle patch: one layer for the research family.
2
+ #
3
+ # The suite row only mounts `research_doctor`; every other row is a plugin this
4
+ # package depends on. Defaults are used so each plugin keeps its own store; the
5
+ # core default (`.research-rep`) is the root the doctor reads. Disable a row in
6
+ # the profile (rather than editing this file) when a project does not need that
7
+ # capability.
8
+ - insert:
9
+ - id: dsh-research-suite
10
+ name: 'dsh-research-suite-plugin'
11
+ - id: dsh-research-core
12
+ name: '@perrylink/dsh-research-core'
13
+ - id: dsh-doc-anchor
14
+ name: dsh-doc-anchor
15
+ - id: dsh-cite-verify
16
+ name: dsh-cite-verify
17
+ - id: dsh-claim-check
18
+ name: '@perrylink/dsh-claim-check'
19
+ - id: dsh-statcheck
20
+ name: dsh-statcheck
21
+ - id: dsh-retraction-watch
22
+ name: dsh-retraction-watch
23
+ - id: dsh-repro-audit
24
+ name: dsh-repro-audit
25
+ - id: dsh-sr-ledger
26
+ name: dsh-sr-ledger
27
+ - id: dsh-meta-analysis
28
+ name: dsh-meta-analysis
29
+ - id: dsh-manuscript-check
30
+ name: dsh-manuscript-check
31
+ - id: dsh-research-report
32
+ name: dsh-research-report
33
+ - id: dsh-library
34
+ name: dsh-library
@@ -0,0 +1,44 @@
1
+ # 90-second demo: from a document to a sealed record
2
+
3
+ This demo uses only synthetic text. It shows the smallest end-to-end path that
4
+ `research_doctor` can then verify.
5
+
6
+ 1. Install the suite (see the main README) and start a session in this
7
+ workspace.
8
+ 2. Anchor the sample document:
9
+
10
+ ```text
11
+ Use doc_anchor on examples/sample.md.
12
+ ```
13
+
14
+ Copy the returned `evidenceId`.
15
+ 3. Check one claim against that evidence:
16
+
17
+ ```text
18
+ Use claim_check with claim "The pilot enrolled 24 participants."
19
+ and the evidenceId from step 2.
20
+ ```
21
+
22
+ The verdict should be `supported`; the sentence is verbatim in the sample.
23
+ 4. Assemble a sealed report:
24
+
25
+ ```text
26
+ Use research_report with that evidenceId and the claim.
27
+ ```
28
+
29
+ Copy the `recordPath`.
30
+ 5. Verify and inspect:
31
+
32
+ ```sh
33
+ dsh-rep-verify <recordPath>
34
+ ```
35
+
36
+ ```text
37
+ Run research_doctor.
38
+ ```
39
+
40
+ A healthy result is `research_doctor: ok`, `researchEvidence=on`,
41
+ `researchReport=on`, and `latest <file> (sealed)`.
42
+
43
+ If the doctor says the root does not exist, the tools ran in a different
44
+ working directory: pass the absolute path as `root`.
@@ -0,0 +1,11 @@
1
+ # Synthetic pilot report
2
+
3
+ The pilot enrolled 24 participants.
4
+
5
+ The intervention reduced the mean error rate by 18% compared with the control.
6
+
7
+ No adverse events were reported during the six-week follow-up.
8
+
9
+ The dataset contains 24 rows and three columns.
10
+
11
+ The analysis used a two-sided t-test at alpha = 0.05.
package/package.json CHANGED
@@ -1,6 +1,93 @@
1
1
  {
2
2
  "name": "dsh-research-suite-plugin",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "0.1.4",
4
+ "description": "One-command research suite for DeepSeek Harness: installs the core evidence, verification, systematic-review and report plugins as one bundle layer, and adds a research_doctor health check for the REP store.",
5
+ "author": "PerryLink contributors",
6
+ "license": "Apache-2.0",
7
+ "repository": {
8
+ "type": "git",
9
+ "url": "git+https://github.com/PerryLink/dsh-research-suite.git"
10
+ },
11
+ "homepage": "https://github.com/PerryLink/dsh-research-suite#readme",
12
+ "bugs": {
13
+ "url": "https://github.com/PerryLink/dsh-research-suite/issues"
14
+ },
15
+ "type": "module",
16
+ "main": "./lib/index.js",
17
+ "types": "./lib/index.d.ts",
18
+ "exports": {
19
+ ".": {
20
+ "types": "./lib/index.d.ts",
21
+ "default": "./lib/index.js"
22
+ },
23
+ "./package.json": "./package.json"
24
+ },
25
+ "files": [
26
+ "lib",
27
+ "cordis.patch.yml",
28
+ "examples",
29
+ "CHANGELOG.md",
30
+ "README.md",
31
+ "README-zh.md",
32
+ "LICENSE",
33
+ "SECURITY.md",
34
+ "THIRD_PARTY_NOTICES.md"
35
+ ],
36
+ "sideEffects": false,
37
+ "dsh": {
38
+ "manifestVersion": 1,
39
+ "bundle": {
40
+ "patch": "./cordis.patch.yml"
41
+ }
42
+ },
43
+ "keywords": [
44
+ "dsh",
45
+ "dsh-plugin",
46
+ "dsh-bundle",
47
+ "deepseek-harness",
48
+ "research",
49
+ "evidence",
50
+ "reproducibility"
51
+ ],
52
+ "engines": {
53
+ "node": "^22.19.0 || >=24.9.0",
54
+ "dsh": ">=0.2.1-0 <0.3.0 || >=0.2.2-0 <0.3.0"
55
+ },
56
+ "packageManager": "pnpm@12.16.1",
57
+ "peerDependencies": {
58
+ "@deepseek-ai/cordis": "^4.0.5-alpha.1",
59
+ "@deepseek-ai/dsh-tools": ">=0.2.1-0 <0.3.0 || >=0.2.2-0 <0.3.0",
60
+ "@deepseek-ai/schemastery": "^3.18.5-alpha.1"
61
+ },
62
+ "dependencies": {
63
+ "@perrylink/dsh-claim-check": "0.1.2",
64
+ "@perrylink/dsh-research-core": "0.1.1",
65
+ "dsh-cite-verify": "0.2.0",
66
+ "dsh-doc-anchor": "0.2.0",
67
+ "dsh-library": "0.3.0",
68
+ "dsh-manuscript-check": "0.1.2",
69
+ "dsh-meta-analysis": "0.1.2",
70
+ "dsh-repro-audit": "0.1.3",
71
+ "dsh-research-report": "0.4.0",
72
+ "dsh-retraction-watch": "0.1.1",
73
+ "dsh-sr-ledger": "0.2.0",
74
+ "dsh-statcheck": "0.1.1"
75
+ },
76
+ "devDependencies": {
77
+ "@deepseek-ai/cordis": "^4.0.5-alpha.1",
78
+ "@deepseek-ai/dsh-tools": "0.2.2-rc.4",
79
+ "@deepseek-ai/schemastery": "^3.18.5-alpha.1",
80
+ "@types/node": "^24.13.3",
81
+ "typescript": "^5.9.0",
82
+ "vitest": "^3.2.4"
83
+ },
84
+ "scripts": {
85
+ "build": "tsc -p tsconfig.json",
86
+ "clean": "node -e \"require('node:fs').rmSync('lib',{recursive:true,force:true})\"",
87
+ "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json",
88
+ "test": "vitest run",
89
+ "check:lockfile": "node scripts/check-lockfile-drift.mjs",
90
+ "test:watch": "vitest",
91
+ "verify:package": "node scripts/verify-package.mjs"
92
+ }
93
+ }