dsh-check-pack 0.2.0 → 0.2.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/LICENSE CHANGED
@@ -2,14 +2,200 @@
2
2
  Version 2.0, January 2004
3
3
  http://www.apache.org/licenses/
4
4
 
5
- Licensed under the Apache License, Version 2.0 (the "License");
6
- you may not use this file except in compliance with the License.
7
- You may obtain a copy of the License at
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
8
6
 
9
- http://www.apache.org/licenses/LICENSE-2.0
7
+ 1. Definitions.
10
8
 
11
- Unless required by applicable law or agreed to in writing, software
12
- distributed under the License is distributed on an "AS IS" BASIS,
13
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14
- See the License for the specific language governing permissions and
15
- limitations under the License.
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 2026 PerryLink
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.en.md ADDED
@@ -0,0 +1,287 @@
1
+ <div align="center">
2
+
3
+ <picture>
4
+ <source media="(prefers-color-scheme: dark)" srcset="docs/assets/dsh-check-pack-hero-en-dark.webp">
5
+ <img src="docs/assets/dsh-check-pack-hero-en-light.webp" width="100%" alt="dsh-check-pack banner: left, the plugin name, two value lines and the footer; right, the one-line install command, three real members with their exact versions, and a deck of member cards collapsing into one bundle card listing package.json, cordis.patch.yml and checkers.json at 53 each, with empty capabilities and no runtime code; the verify seal sits at the right and the eight covered domains at the bottom">
6
+ </picture>
7
+
8
+ # dsh-check-pack
9
+
10
+ **Install all 53 PerryLink compliance checkers with one command — a single bundle layer inserts all 53 Cordis rows.**
11
+
12
+ The suite entry point for China-domain document checks (trade, customs, bids, HSE, medical, legal, government, manufacturing): every checker keeps its own npm name, rule pack, and version; this package only brings them in together.
13
+
14
+ Last verified on DeepSeek Harness `dsh-v0.2.3-alpha.1` (2026-11-22).
15
+
16
+ [Install](#three-step-setup) · [Configuration](#configuration) · [FAQ](#faq) · [简体中文](README.md) · [English](README.en.md) · [Español](README.es.md) · [Português](README.pt.md) · [हिन्दी](README.hi.md)
17
+
18
+ [![License](https://img.shields.io/badge/license-Apache--2.0-3366CC?style=flat-square&labelColor=2B3245)](LICENSE)
19
+ [![DSH](https://img.shields.io/badge/DSH-%E2%89%A50.2.3%20%3C0.3.0-4B67B4?style=flat-square&labelColor=2B3245)](#compatibility)
20
+ [![npm](https://img.shields.io/npm/v/dsh-check-pack?style=flat-square&labelColor=2B3245&color=CB3837)](https://www.npmjs.com/package/dsh-check-pack)
21
+ [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-check-pack/ci.yml?branch=main&label=CI&style=flat-square&labelColor=2B3245)](https://github.com/PerryLink/dsh-check-pack/actions/workflows/ci.yml)
22
+ [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-339933?style=flat-square&labelColor=2B3245)](#compatibility)
23
+
24
+ [![Stars](https://img.shields.io/github/stars/PerryLink/dsh-check-pack?style=flat-square&labelColor=2B3245)](https://github.com/PerryLink/dsh-check-pack/stargazers)
25
+ [![npm downloads](https://img.shields.io/npm/dm/dsh-check-pack?style=flat-square&labelColor=2B3245&color=CB3837)](https://www.npmjs.com/package/dsh-check-pack)
26
+ [![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-check-pack?metric=downloads)](https://dshfind.com/plugins/PerryLink/dsh-check-pack?ref=badge)
27
+ [![Gitee](https://img.shields.io/badge/Gitee-mirror-C71D23?style=flat-square&labelColor=2B3245&logo=gitee)](https://gitee.com/perrylink/dsh-check-pack)
28
+
29
+ ```sh
30
+ dsh plugin --profile <name> add dsh-check-pack
31
+ ```
32
+
33
+ </div>
34
+
35
+ <sub>Community plugin, not affiliated with DeepSeek. Canonical repository: <https://github.com/PerryLink/dsh-check-pack> (Gitee is a mirror).</sub>
36
+
37
+ ## What it is
38
+
39
+ `dsh-check-pack` is the suite entry point that installs **all 53 PerryLink compliance checkers** with one command. It contains no checking logic of its own: the bundled `cordis.patch.yml` is one bundle layer that `insert`s 53 Cordis rows at install time, wiring each checker into the active profile at the version pinned in `checkers.json`.
40
+
41
+ The dependency list is the member list — 53 `dsh-*` packages at exact versions. Each checker keeps its own npm name, rule pack, README, and version; upgrades and configuration happen on its side. This package was formerly the deprecated [`@perrylink/dsh-checkers`](https://www.npmjs.com/package/@perrylink/dsh-checkers); it is now named `dsh-check-pack`, so install it under the new name.
42
+
43
+ Coverage is China-domain documents: trade, customs, bids, HSE, medical, legal, government, manufacturing. Every checker only reports differences inside the material — **it never makes a legal, medical, or customs determination**. The conclusion stays with the reviewer.
44
+
45
+ <picture>
46
+ <source media="(prefers-color-scheme: dark)" srcset="docs/assets/dsh-check-pack-flow-v5-dark.svg">
47
+ <img src="docs/assets/dsh-check-pack-flow-v5-light.svg" width="100%" alt="dsh-check-pack structure: eight version-pinned members on the left converge into one bundle card — package.json dependencies, the 53 insert rows of cordis.patch.yml and the 53 id/name/version entries of checkers.json — with node verify.mjs gating that the three counts match and throwing otherwise; on the right the bundle patch expands into 53 insert rows of a Cordis profile; the dashed return says upstream releases do not drift into the published snapshot, so rebuild and republish; the footer lists the eight covered domains">
48
+ </picture>
49
+
50
+ ## Three-step setup
51
+
52
+ ![dsh-check-pack: real terminal run](docs/assets/dsh-check-pack-demo.gif)
53
+
54
+ *Animated replay of a real run in this repository (2026-11-21).*
55
+
56
+ 1. **Install** (pick one channel):
57
+
58
+ ```sh
59
+ # npm channel (published releases)
60
+ dsh plugin --profile web add dsh-check-pack
61
+ # git channel (latest main; equivalent to git+https://github.com/PerryLink/dsh-check-pack.git)
62
+ dsh plugin --profile web add github:PerryLink/dsh-check-pack
63
+ # tarball channel: npm pack in this repo, then
64
+ dsh plugin --profile web add ./dsh-check-pack-<version>.tgz
65
+ ```
66
+
67
+ > Per this repository's record: npm stages new versions for 2FA approval; if `npm view dsh-check-pack version` does not show the latest release, use the git channel first.
68
+
69
+ 2. **Minimal configuration**: none. The bundle patch inserts all 53 rows with each checker's defaults; to tune one checker, change its keys in its own README — this package has nothing to configure.
70
+
71
+ 3. **Verify it took effect**:
72
+
73
+ ```sh
74
+ dsh --profile web --dump-config | grep -A1 'id: dsh-aqua-input-check'
75
+ ```
76
+
77
+ Seeing any checker row from the suite means the bundle layer has expanded. You can also run the consistency gate in this repository:
78
+
79
+ ```sh
80
+ node verify.mjs
81
+ # => suite OK: 53 rows, 53 dependencies
82
+ ```
83
+
84
+ **Uninstall**: `dsh plugin --profile web remove dsh-check-pack` removes the suite row; checkers you installed individually still need their own `remove`.
85
+
86
+ ## Core capabilities
87
+
88
+ - **One command, 53 checkers** — no per-checker `add`: one `insert` in `cordis.patch.yml` brings all 53 rows in, so installing one package installs the whole suite.
89
+ - **Exact version pins** — all 53 dependencies in `package.json` are exact versions; `checkers.json` records the same `id` / `name` / `version` triples; `verify.mjs` keeps the three in agreement.
90
+ - **Entry point only, no adjudication** — this package has no checking code and never reads or writes business documents; rules, severities, and report wording belong to each checker and are unchanged here.
91
+ - **No capabilities, no registrations** — `dsh.capabilities` is an empty array: no tools, commands, services, events, or HTTP routes, only the inserted bundle rows.
92
+ - **Regenerable manifests** — `node build.mjs` can rebuild the dependencies, `cordis.patch.yml`, and `checkers.json` from `../../checkers` in the workspace; that directory is absent in the standalone repo, so regeneration is optional.
93
+ - **Nightly upstream health check** — `checkers-nightly.yml` clones all 53 checker repositories every day at 18:00 UTC and runs `pnpm run typecheck` plus `pnpm test`; `ci.yml` runs `node verify.mjs` and `npm pack --dry-run` on Node 22.
94
+
95
+ ## Configuration
96
+
97
+ This package registers no configuration keys and has no Schemastery `Config`: all it does is insert 53 rows whose `id` / `name` are the checker package names, with `config` left empty so each checker uses its defaults. To tune parameters, go to the relevant checker's README (for example `rulesFile`, `disabledRules`, `onlyRules`, and `timeoutMs` in [`dsh-aqua-input-check`](https://github.com/PerryLink/dsh-aqua-input-check)) — those keys belong to the checkers, not to this package.
98
+
99
+ This package's own manifest fields:
100
+
101
+ | Field | Value | Meaning |
102
+ |---|---|---|
103
+ | `dsh.manifestVersion` | `1` | bundle manifest version |
104
+ | `dsh.bundle.patch` | `./cordis.patch.yml` | bundle patch applied at install time |
105
+ | `dsh.capabilities` | `[]` | requests no host capabilities |
106
+ | `engines.dsh` | `>=0.2.3-0 <0.3.0` | runtime range |
107
+ | `engines.node` | `^22.19.0 \|\| >=24.0.0` | Node range |
108
+ | `dependencies` | 53 exact versions | suite members and pinned versions |
109
+
110
+ <details>
111
+ <summary>Full suite manifest (53 members, quoted verbatim from checkers.json)</summary>
112
+
113
+ | Package | Version |
114
+ |---|---|
115
+ | `dsh-aqua-input-check` | `0.2.31` |
116
+ | `dsh-archive-check` | `0.2.9` |
117
+ | `dsh-bid-ca-precheck` | `0.2.31` |
118
+ | `dsh-bid-qual-check` | `0.2.30` |
119
+ | `dsh-contract-stance` | `0.2.9` |
120
+ | `dsh-customs-doc-check` | `0.2.8` |
121
+ | `dsh-demurrage-ledger` | `0.2.9` |
122
+ | `dsh-drill-script-check` | `0.2.8` |
123
+ | `dsh-eia-guide-check` | `0.2.9` |
124
+ | `dsh-emergency-plan` | `0.2.8` |
125
+ | `dsh-essay-rubric-check` | `0.2.8` |
126
+ | `dsh-evidence-check` | `0.2.31` |
127
+ | `dsh-export-ctl-check` | `0.2.31` |
128
+ | `dsh-fmea-table-check` | `0.2.8` |
129
+ | `dsh-forecast-penalty` | `0.2.8` |
130
+ | `dsh-gongwen-flow-check` | `0.2.9` |
131
+ | `dsh-gongwen-word-check` | `0.2.30` |
132
+ | `dsh-guard-plan-qc` | `0.2.8` |
133
+ | `dsh-hazchem-check` | `0.2.31` |
134
+ | `dsh-hazplan-check` | `0.2.30` |
135
+ | `dsh-hidden-risk-map` | `0.2.8` |
136
+ | `dsh-hs-classify` | `0.2.30` |
137
+ | `dsh-icd-rule-check` | `0.2.30` |
138
+ | `dsh-lawcite-adapter` | `0.2.30` |
139
+ | `dsh-lc-doc-check` | `0.2.9` |
140
+ | `dsh-learning-gap-check` | `0.2.8` |
141
+ | `dsh-medrec-qc` | `0.2.31` |
142
+ | `dsh-nsfc-form-check` | `0.2.30` |
143
+ | `dsh-nurse-record-check` | `0.2.30` |
144
+ | `dsh-origin-rvc-check` | `0.2.9` |
145
+ | `dsh-ota-review-check` | `0.2.30` |
146
+ | `dsh-paper-doc-adapter` | `0.2.8` |
147
+ | `dsh-permit-report-check` | `0.2.30` |
148
+ | `dsh-pipeline-check` | `0.2.8` |
149
+ | `dsh-pleading-draft` | `0.2.30` |
150
+ | `dsh-policy-brief-draft` | `0.2.30` |
151
+ | `dsh-power-loss-split` | `0.2.9` |
152
+ | `dsh-power-ticket-check` | `0.2.9` |
153
+ | `dsh-ppap-check` | `0.2.8` |
154
+ | `dsh-protest-deadline` | `0.2.30` |
155
+ | `dsh-railway-window` | `0.2.8` |
156
+ | `dsh-repair-order-qc` | `0.2.30` |
157
+ | `dsh-review-reply-check` | `0.2.8` |
158
+ | `dsh-rulefile-check` | `0.2.8` |
159
+ | `dsh-safety-brief-check` | `0.2.9` |
160
+ | `dsh-site-log-check` | `0.2.31` |
161
+ | `dsh-soe-decision-check` | `0.2.33` |
162
+ | `dsh-soilwater-check` | `0.2.8` |
163
+ | `dsh-sop-sync-check` | `0.2.8` |
164
+ | `dsh-spc-gbt-adapter` | `0.2.8` |
165
+ | `dsh-tender-extract` | `0.2.31` |
166
+ | `dsh-tender-matrix` | `0.2.32` |
167
+ | `dsh-warranty-calc` | `0.2.30` |
168
+
169
+ </details>
170
+
171
+ ## FAQ
172
+
173
+ <details>
174
+ <summary>Do I still need to install the 53 checkers one by one?</summary>
175
+
176
+ No. All 53 packages are dependencies of `dsh-check-pack`, resolved at install time, and the bundle patch inserts the 53 Cordis rows in one go. You can still install a single checker separately — it keeps its own npm name and version, and one you installed separately still needs to be removed separately when you uninstall this package.
177
+
178
+ </details>
179
+
180
+ <details>
181
+ <summary>Why can't npm give me the latest version?</summary>
182
+
183
+ Per this repository's record, npm stages new versions for 2FA approval. Until that approval lands, use the git channel: `dsh plugin --profile web add github:PerryLink/dsh-check-pack`. The version currently on npm is `0.2.3`; check with `npm view dsh-check-pack version`.
184
+
185
+ </details>
186
+
187
+ <details>
188
+ <summary>Does uninstalling remove all 53 checkers?</summary>
189
+
190
+ `remove dsh-check-pack` removes the suite row; this package and the 53 checkers are independent npm packages. If you installed a checker separately, remove it separately; if a checker row remains after the suite row is gone, first check whether it is the one you installed yourself.
191
+
192
+ </details>
193
+
194
+ <details>
195
+ <summary>Do these checkers return a compliant / non-compliant verdict?</summary>
196
+
197
+ No. Each checker lists only the differences it can point to inside the material (which row, which column, what is missing, how to fill it), makes no legal, medical, or customs determination, and assigns no liability; the conclusion stays with the reviewer. This package only installs the checkers and does not change their report wording.
198
+
199
+ </details>
200
+
201
+ <details>
202
+ <summary>Can the 53 versions drift on their own?</summary>
203
+
204
+ No automatic drift from upstream. A published `dsh-check-pack` pins the 53 versions in `package.json`; `checkers.json` and `cordis.patch.yml` record the same set, and `verify.mjs` checks that the three agree (53 rows / 53 dependencies). After an upstream release, regenerating with `node build.mjs` and publishing this package is required to follow; `checkers-nightly.yml` verifies every night that the upstream repositories still pass typecheck and test.
205
+
206
+ </details>
207
+
208
+ ## Security boundaries
209
+
210
+ - **No adjudication.** This package and the checkers it installs only report differences: no legal, medical, or customs determination, and a report is not proof of compliance.
211
+ - **Bounded scope.** Only China-domain documents (trade, customs, bids, HSE, medical, legal, government, manufacturing); documents outside that scope are not promised.
212
+ - **This package never touches data.** It ships only a manifest, a bundle patch, and manifest files, with no runtime code: it reads no documents, makes no network calls, writes no files, and registers no tools or commands; `dsh.capabilities` is empty.
213
+ - **The entry point does not change member behavior.** Each checker owns its rules, severities, and disclaimers; installing this package neither relaxes nor tightens any rule.
214
+
215
+ ## Known limitations
216
+
217
+ - **The suite version is a release snapshot.** The 53 dependencies are pinned at release time; upstream fixes do not flow into a published package — rebuild and publish this package to follow.
218
+ - **npm releases go through 2FA staging.** Per this repository's record, a new version may sit in npm's 2FA approval; only the git channel gives you the latest main.
219
+ - **No configuration of its own.** You cannot toggle a checker or change a severity from here; configure it in that checker's README, or install only the checkers you need.
220
+ - **Rebuilding needs the workspace.** `build.mjs` reads `../../checkers`; a standalone GitHub clone lacks that directory, so `verify.mjs` checks the committed manifests by default and auto-rebuild only happens in the workspace (`CHECK_BUILD=1` and the directory present).
221
+ - **The upstream health check is asynchronous.** `checkers-nightly.yml` runs once a night and reports the upstream repositories' state that day; it does not change what a released package contains.
222
+ - **The old name is deprecated.** `@perrylink/dsh-checkers` is the former name; do not install it — use `dsh-check-pack` on npm.
223
+
224
+ ## Interoperability with other DSH plugins
225
+
226
+ - **Insert only, never overwrite.** Every row in `cordis.patch.yml` is an `insert`; it never overrides a built-in row's or another plugin's `config`. All 53 ids are `dsh-*` package names.
227
+ - **No surface registered.** This package has no runtime code: it provides no service key, registers no tool / command / client slot / `webServer` prefix, and mutates no global object.
228
+ - **Members stay independent.** The 53 checkers are independent npm packages that declare their own dependencies and capabilities; this package neither proxies their tools nor changes how they register.
229
+ - **Uninstall is local.** `remove dsh-check-pack` removes only the suite row and the package itself; it does not touch other plugin rows or delete anyone else's configuration.
230
+
231
+ ## Compatibility
232
+
233
+ | Surface | Status |
234
+ |---|---|
235
+ | Harness | DSH `>=0.2.3-0 <0.3.0` (`engines.dsh`); bundle manifest version `1` |
236
+ | Node | `^22.19.0 \|\| >=24.0.0` |
237
+ | Platforms | Anywhere DSH runs (no native code, no network requests) |
238
+ | Package name | `dsh-check-pack` on npm; the former `@perrylink/dsh-checkers` is deprecated |
239
+ | npm version | `0.2.3` |
240
+
241
+ ## Ecosystem & quality
242
+
243
+ - [Gitee mirror](https://gitee.com/perrylink/dsh-check-pack) (sync mirror; GitHub is canonical)
244
+ - [dshfind plugin page](https://dshfind.com/plugins/PerryLink/dsh-check-pack) (installs and ranking)
245
+ - [npm package page](https://www.npmjs.com/package/dsh-check-pack) (version and dependency tree)
246
+ - [CI workflow](https://github.com/PerryLink/dsh-check-pack/actions/workflows/ci.yml) (`node verify.mjs` + `npm pack --dry-run`)
247
+ - [checkers-nightly](https://github.com/PerryLink/dsh-check-pack/actions/workflows/checkers-nightly.yml) (per-upstream typecheck + test every night)
248
+ - [Ecosystem knowledge base](https://perrylink.github.io/dsh-plugin-guide/) — plugin development guide · plugin-selection data · maintenance criteria
249
+
250
+ ## Development
251
+
252
+ ```sh
253
+ node verify.mjs # 53 rows / 53 dependencies / version agreement; same as CI
254
+ node build.mjs # rebuild the three manifest files (workspace only: ../../checkers present)
255
+ npm pack --dry-run # inspect the published contents (CI runs this too)
256
+ python scripts/gen-readme-assets.py # regenerate the images (Python + Pillow)
257
+ ```
258
+
259
+ No build step, no runtime dependencies: the package is only a manifest, a patch, and manifest files, and `verify.mjs` / `build.mjs` use Node built-ins only. `build.mjs` reads the 53 checkers' `package.json` and `cordis.patch.yml` from `../../checkers`, then rewrites the `package.json` dependencies, `cordis.patch.yml`, and `checkers.json`; a standalone clone lacks that directory, so rebuilding is opt-in.
260
+
261
+ Layout:
262
+
263
+ | Path | Purpose |
264
+ |---|---|
265
+ | `package.json` | npm metadata + 53 exact dependencies + bundle manifest |
266
+ | `cordis.patch.yml` | the 53 rows inserted at install time (generated) |
267
+ | `checkers.json` | the 53 checkers' `id` / `name` / `version` list (generated) |
268
+ | `build.mjs` | rebuilds the three files above from `../../checkers` |
269
+ | `verify.mjs` | consistency gate: 53 / 53 / 53 + version agreement |
270
+ | `.github/workflows/ci.yml` | verify + pack dry-run on Node 22 |
271
+ | `.github/workflows/checkers-nightly.yml` | per-upstream typecheck + test every night |
272
+ | `scripts/gen-readme-assets.py` | programmatic light/dark flow diagram in `docs/assets/` |
273
+ | `docs/assets/` | README images |
274
+
275
+ Topics: `dsh-plugin`, `dsh-bundle`
276
+
277
+ ## Family & thanks
278
+
279
+ This project is part of the DeepSeek Harness plugin family from [PerryLink](https://github.com/PerryLink) (all Apache-2.0). If this suite is useful, **a star helps the next person find it** — nothing is gated behind it.
280
+
281
+ - [@PerryLink](https://github.com/PerryLink) — creator and maintainer: the 53-checker suite manifest, the bundle layer, the `build.mjs` / `verify.mjs` gates, the nightly upstream health check, and the five-language docs.
282
+
283
+ ## License
284
+
285
+ [LICENSE](LICENSE) (Apache License 2.0) © 2026 dsh-check-pack contributors
286
+
287
+ <p align="center"><sub>Apache-2.0 · Community plugin, not affiliated with DeepSeek.</sub></p>