dsh-drill-script-check 0.0.0-stage → 0.2.0

package/LICENSE

@@ -0,0 +1,15 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+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-es.md

@@ -0,0 +1,92 @@
+# dsh-drill-script-check
+
+**Boundary:** this plugin checks an **应急演练脚本** for completeness and arithmetic — that each step names its
+phase and script content, that it names a commander, that the response level comes from your vocabulary, that a
+step with an action lists the resources it needs, that the step durations total the drill's planned duration, that
+key checkpoints state their judgement condition, that step numbers are unique, and that the script names its drill
+and organiser. It does **not** decide whether a drill was realistic or effective, whether the response level was
+right, whether the actions were correct, or whether the drill met its objectives.
+
+> ### ⚠️ Read this before trusting a citation in the report
+>
+> **Every `excerpt` in this plugin's rule pack says, in so many words, that the clause text was not
+> obtained.** The regime lives in AQ/T 9007—2019, 《生产安全事故应急条例》(国务院令第708号) and each
+> institution's emergency plans. The verification pass could not retrieve verbatim clause text, so rather than
+> paraphrase a quotation the pack states the gap in the `excerpt` field itself and puts the honest reasoning in
+> `note`. Every rule is therefore `warn` or `info`, and a test asserts that no rule claims a quotation it does
+> not have. **When the texts are in hand, replace each `excerpt` with the real clause and raise `kind` to
+> `direct`.**
+>
+> **No response-level scale is built in.** Levels differ between plan systems — general / larger / major /
+> especially major, or a unit's own Ⅰ–Ⅳ — so `DR-003` reports itself in `skipped` until you configure your
+> vocabulary, and it never judges which level an event should trigger. That is the incident commander's call.
+>
+> The resource rule fires only when a script action is present, so a step that is purely informational is not
+> asked for equipment. And the duration total is read from the header, where a drill's planned length normally
+> lives.
+
+## Compatibility
+
+| Superficie | Estado |
+|---|---|
+| Harness | Rango de peers `>=0.1.2-rc.1 <0.2.0 \|\| >=0.2.0-0 <0.3.0` — verificado para aceptar tanto `0.2.0-rc.2` como `0.2.1-alpha.1`. **No se declara `engines.dsh`**: no tiene lector y no puede rechazar ningún host |
+| Node | `^22.19.0 || >=24.0.0` |
+| Plataformas | Todas (ESM puro; sin código nativo, sin red, sin llamada al modelo) |
+| Modo de herramienta | Funciona en `native`, `ptc` y `both`; para un directorio completo use `ptc` |
+
+## What it does
+
+La tabla de reglas, los campos y el comportamiento detallado están en [README.md](README.md#what-it-does) (versión principal en inglés). El plugin sólo enumera divergencias literales frente a las cláusulas citadas e indica en `skipped` cada comprobación que no pudo ejecutarse.
+
+## Install
+
+```sh
+dsh plugin --profile <name> add dsh-drill-script-check
+dsh --profile <name> --dump-config | grep 'dsh-drill-script-check'
+```
+
+## Configuration
+
+Todos los parámetros ajustables viven en el esquema Schemastery de `src/config.ts`, por lo que se cambian desde `cordis.yml` sin tocar el código; los umbrales por regla están en el paquete de reglas bajo `rules/`.
+
+| Clave | Tipo | Predeterminado | Descripción |
+|---|---|---|---|
+| `rulesFile` | string | `rules/drill-script-check.yaml` | Ruta del paquete de reglas, relativa a la raíz del paquete |
+| `disabledRules` | string[] | `[]` | Ids de reglas que se dejan de ejecutar; cada una aparece en `skipped` |
+| `onlyRules` | string[] | `[]` | Ejecutar solo estas reglas; vacío ejecuta todas |
+| `skipNotes` | string | `""` | Nota añadida a cada motivo de `skipped` |
+| `timeoutMs` | number | `120000` | Presupuesto de tiempo de espera cooperativo de la herramienta |
+
+## Material format
+
+Acepta JSON o YAML. El ejemplo completo de campos está en [README.md](README.md#material-format) (versión principal en inglés). Los campos son opcionales en la capa de lectura y los valida el motor, de modo que una exportación parcial produce hallazgos sobre lo que falta en lugar de un fallo.
+
+## Rule sources
+
+Los datos de las reglas están separados del código: cada regla lleva documento, número, cláusula en la numeración propia de la fuente, extracto literal y URL de origen. El cargador impone que el extracto sea una cita real de al menos ocho caracteres y que una comprobación basada sólo en un principio general (`kind: derived-from-principle`, tope `warn`) o en una política local (`kind: institutional-configuration`, tope `info`) nunca se declare `error`.
+
+Los límites verificados y las conclusiones deliberadamente **no** afirmadas están en [README.md](README.md#rule-sources) (versión principal en inglés) y en `rules/evidence/`.
+
+## Troubleshooting
+
+- **El plugin se instala pero la herramienta no aparece**: compruebe que `main` resuelve a `lib/index.mjs` y que `pnpm run build` lo generó.
+- **`dsh plugin add` rechaza el paquete**: la faixa de peers cubre `0.1.x` y `0.2.x`; fuera de ella, conceda una exención explícita con `dsh plugin --profile <name> allow-version <pkg@ver> --dsh-version <runtime> --accept-risk`.
+- **Una regla no se ejecutó**: lea el arreglo `skipped`.
+- **`check` informa `manifest-peers` como fallo**: es un problema conocido de `dsh-plugin-dev`; el runtime aplica la compatibilidad al instalar.
+- **Los horarios parecen desplazados**: toda la aritmética es de hora local sobre las cadenas entregadas.
+
+## Development
+
+```sh
+pnpm install
+pnpm run typecheck
+pnpm test
+pnpm run build
+node ../scripts/sync-shared.mjs dsh-drill-script-check
+```
+
+El último comando copia el kit compartido de `../_shared` a `src/shared/`; vuelva a ejecutarlo tras cada cambio compartido.
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 dsh-drill-script-check contributors.

package/README-hi.md

@@ -0,0 +1,92 @@
+# dsh-drill-script-check
+
+**Boundary:** this plugin checks an **应急演练脚本** for completeness and arithmetic — that each step names its
+phase and script content, that it names a commander, that the response level comes from your vocabulary, that a
+step with an action lists the resources it needs, that the step durations total the drill's planned duration, that
+key checkpoints state their judgement condition, that step numbers are unique, and that the script names its drill
+and organiser. It does **not** decide whether a drill was realistic or effective, whether the response level was
+right, whether the actions were correct, or whether the drill met its objectives.
+
+> ### ⚠️ Read this before trusting a citation in the report
+>
+> **Every `excerpt` in this plugin's rule pack says, in so many words, that the clause text was not
+> obtained.** The regime lives in AQ/T 9007—2019, 《生产安全事故应急条例》(国务院令第708号) and each
+> institution's emergency plans. The verification pass could not retrieve verbatim clause text, so rather than
+> paraphrase a quotation the pack states the gap in the `excerpt` field itself and puts the honest reasoning in
+> `note`. Every rule is therefore `warn` or `info`, and a test asserts that no rule claims a quotation it does
+> not have. **When the texts are in hand, replace each `excerpt` with the real clause and raise `kind` to
+> `direct`.**
+>
+> **No response-level scale is built in.** Levels differ between plan systems — general / larger / major /
+> especially major, or a unit's own Ⅰ–Ⅳ — so `DR-003` reports itself in `skipped` until you configure your
+> vocabulary, and it never judges which level an event should trigger. That is the incident commander's call.
+>
+> The resource rule fires only when a script action is present, so a step that is purely informational is not
+> asked for equipment. And the duration total is read from the header, where a drill's planned length normally
+> lives.
+
+## Compatibility
+
+| सतह | स्थिति |
+|---|---|
+| Harness | peer रेंज `>=0.1.2-rc.1 <0.2.0 \|\| >=0.2.0-0 <0.3.0` — `0.2.0-rc.2` और `0.2.1-alpha.1` दोनों को स्वीकार करने के लिए सत्यापित। **`engines.dsh` जानबूझकर घोषित नहीं**: इसका कोई पाठक नहीं और यह किसी होस्ट को अस्वीकार नहीं कर सकता |
+| Node | `^22.19.0 || >=24.0.0` |
+| प्लेटफ़ॉर्म | सभी (शुद्ध ESM; कोई नेटिव कोड नहीं, कोई नेटवर्क नहीं, कोई मॉडल कॉल नहीं) |
+| टूल मोड | `native`, `ptc` और `both` में काम करता है; पूरे फ़ोल्डर के लिए `ptc` चुनें |
+
+## What it does
+
+नियम-सूची, फ़ील्ड और विस्तृत व्यवहार [README.md](README.md#what-it-does) (अंग्रेज़ी मुख्य संस्करण) में हैं। यह प्लगइन केवल उद्धृत धाराओं के सामने शाब्दिक अंतर सूचीबद्ध करता है और हर न चल पाई जाँच को `skipped` में बताता है।
+
+## Install
+
+```sh
+dsh plugin --profile <name> add dsh-drill-script-check
+dsh --profile <name> --dump-config | grep 'dsh-drill-script-check'
+```
+
+## Configuration
+
+सभी समायोज्य पैरामीटर `src/config.ts` की Schemastery स्कीमा में हैं, इसलिए कोड बदले बिना `cordis.yml` से बदले जा सकते हैं; प्रति-नियम सीमाएँ `rules/` के नियम-पैक में हैं।
+
+| कुंजी | प्रकार | डिफ़ॉल्ट | विवरण |
+|---|---|---|---|
+| `rulesFile` | string | `rules/drill-script-check.yaml` | नियम-पैक का पथ, पैकेज रूट के सापेक्ष |
+| `disabledRules` | string[] | `[]` | बंद करने वाले नियम id; प्रत्येक `skipped` में दिखता है |
+| `onlyRules` | string[] | `[]` | केवल ये नियम चलाएँ; खाली होने पर सभी नियम चलते हैं |
+| `skipNotes` | string | `""` | हर `skipped` कारण के आगे जोड़ी जाने वाली टिप्पणी |
+| `timeoutMs` | number | `120000` | उपकरण का सहकारी समय-सीमा बजट |
+
+## Material format
+
+JSON या YAML स्वीकार्य है। पूरा फ़ील्ड उदाहरण [README.md](README.md#material-format) (अंग्रेज़ी मुख्य संस्करण) में है। पढ़ने की परत में फ़ील्ड वैकल्पिक हैं और जाँच इंजन उन्हें सत्यापित करता है, इसलिए आंशिक निर्यात पर क्रैश के बजाय "अनुपस्थित" श्रेणी के निष्कर्ष मिलते हैं।
+
+## Rule sources
+
+नियम-डेटा कोड से अलग है: प्रत्येक नियम में दस्तावेज़, संख्या, स्रोत की अपनी क्रमांकन-प्रणाली के अनुसार धारा, शब्दशः उद्धरण और स्रोत URL होता है। लोडर लागू करता है कि उद्धरण कम से कम आठ अक्षरों का वास्तविक उद्धरण हो, और जिस जाँच का आधार केवल सामान्य सिद्धांत (`kind: derived-from-principle`, अधिकतम `warn`) या स्थानीय नीति (`kind: institutional-configuration`, अधिकतम `info`) हो, उसे कभी `error` घोषित न किया जाए।
+
+सत्यापित सीमाएँ और जान-बूझकर **न** कहे गए निष्कर्ष [README.md](README.md#rule-sources) (अंग्रेज़ी मुख्य संस्करण) और `rules/evidence/` में हैं।
+
+## Troubleshooting
+
+- **प्लगइन इंस्टॉल हो गया पर टूल दिखता नहीं**: जाँचें कि `main` `lib/index.mjs` पर जाता है और `pnpm run build` ने उसे बनाया है।
+- **`dsh plugin add` असंगत बताकर मना करता है**: peer range `0.1.x` और `0.2.x` दोनों को कवर करती है; बाहर होने पर स्पष्ट छूट दें: `dsh plugin --profile <name> allow-version <pkg@ver> --dsh-version <runtime> --accept-risk`।
+- **कोई नियम नहीं चला**: `skipped` सरणी देखें।
+- **`check` में `manifest-peers` विफल दिखता है**: यह `dsh-plugin-dev` की ज्ञात अपस्ट्रीम समस्या है; रनटाइम इंस्टॉल के समय अनुकूलता लागू करता है।
+- **समय खिसका हुआ लगता है**: सारी गणना दिए गए स्ट्रिंग पर वॉल-क्लॉक है।
+
+## Development
+
+```sh
+pnpm install
+pnpm run typecheck
+pnpm test
+pnpm run build
+node ../scripts/sync-shared.mjs dsh-drill-script-check
+```
+
+अंतिम कमांड `../_shared` का साझा किट `src/shared/` में कॉपी करता है; हर साझा बदलाव के बाद इसे दोबारा चलाएँ।
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 dsh-drill-script-check contributors.

package/README-pt.md

@@ -0,0 +1,92 @@
+# dsh-drill-script-check
+
+**Boundary:** this plugin checks an **应急演练脚本** for completeness and arithmetic — that each step names its
+phase and script content, that it names a commander, that the response level comes from your vocabulary, that a
+step with an action lists the resources it needs, that the step durations total the drill's planned duration, that
+key checkpoints state their judgement condition, that step numbers are unique, and that the script names its drill
+and organiser. It does **not** decide whether a drill was realistic or effective, whether the response level was
+right, whether the actions were correct, or whether the drill met its objectives.
+
+> ### ⚠️ Read this before trusting a citation in the report
+>
+> **Every `excerpt` in this plugin's rule pack says, in so many words, that the clause text was not
+> obtained.** The regime lives in AQ/T 9007—2019, 《生产安全事故应急条例》(国务院令第708号) and each
+> institution's emergency plans. The verification pass could not retrieve verbatim clause text, so rather than
+> paraphrase a quotation the pack states the gap in the `excerpt` field itself and puts the honest reasoning in
+> `note`. Every rule is therefore `warn` or `info`, and a test asserts that no rule claims a quotation it does
+> not have. **When the texts are in hand, replace each `excerpt` with the real clause and raise `kind` to
+> `direct`.**
+>
+> **No response-level scale is built in.** Levels differ between plan systems — general / larger / major /
+> especially major, or a unit's own Ⅰ–Ⅳ — so `DR-003` reports itself in `skipped` until you configure your
+> vocabulary, and it never judges which level an event should trigger. That is the incident commander's call.
+>
+> The resource rule fires only when a script action is present, so a step that is purely informational is not
+> asked for equipment. And the duration total is read from the header, where a drill's planned length normally
+> lives.
+
+## Compatibility
+
+| Superfície | Estado |
+|---|---|
+| Harness | Faixa de peers `>=0.1.2-rc.1 <0.2.0 \|\| >=0.2.0-0 <0.3.0` — verificada para aceitar tanto `0.2.0-rc.2` quanto `0.2.1-alpha.1`. **`engines.dsh` não é declarado**: não tem leitor e não pode recusar nenhum host |
+| Node | `^22.19.0 || >=24.0.0` |
+| Plataformas | Todas (ESM puro; sem código nativo, sem rede, sem chamada ao modelo) |
+| Modo de ferramenta | Funciona em `native`, `ptc` e `both`; para um diretório inteiro use `ptc` |
+
+## What it does
+
+A tabela de regras, os campos e o comportamento detalhado estão em [README.md](README.md#what-it-does) (versão principal em inglês). O plugin apenas lista divergências literais frente às cláusulas citadas e indica em `skipped` cada verificação que não pôde ser executada.
+
+## Install
+
+```sh
+dsh plugin --profile <name> add dsh-drill-script-check
+dsh --profile <name> --dump-config | grep 'dsh-drill-script-check'
+```
+
+## Configuration
+
+Todos os parâmetros ajustáveis ficam no esquema Schemastery de `src/config.ts`, portanto mudam pelo `cordis.yml` sem editar código; os limites por regra ficam no pacote de regras sob `rules/`.
+
+| Chave | Tipo | Padrão | Descrição |
+|---|---|---|---|
+| `rulesFile` | string | `rules/drill-script-check.yaml` | Caminho do pacote de regras, relativo à raiz do pacote |
+| `disabledRules` | string[] | `[]` | Ids de regras a desativar; cada uma aparece em `skipped` |
+| `onlyRules` | string[] | `[]` | Executar apenas estas regras; vazio executa todas |
+| `skipNotes` | string | `""` | Nota acrescentada a cada motivo de `skipped` |
+| `timeoutMs` | number | `120000` | Orçamento de tempo limite cooperativo da ferramenta |
+
+## Material format
+
+Aceita JSON ou YAML. O exemplo completo de campos está em [README.md](README.md#material-format) (versão principal em inglês). Os campos são opcionais na camada de leitura e validados pelo motor, de modo que uma exportação parcial gera achados sobre o que falta em vez de falhar.
+
+## Rule sources
+
+Os dados das regras ficam separados do código: cada regra traz documento, número, cláusula na numeração própria da fonte, trecho literal e URL de origem. O carregador impõe que o trecho seja citação real de pelo menos oito caracteres e que uma verificação baseada apenas em princípio geral (`kind: derived-from-principle`, teto `warn`) ou em política local (`kind: institutional-configuration`, teto `info`) nunca seja declarada `error`.
+
+Os limites verificados e as conclusões deliberadamente **não** afirmadas estão em [README.md](README.md#rule-sources) (versão principal em inglês) e em `rules/evidence/`.
+
+## Troubleshooting
+
+- **O plugin instala mas a ferramenta não aparece**: confirme que `main` resolve para `lib/index.mjs` e que `pnpm run build` o gerou.
+- **`dsh plugin add` recusa o pacote**: a faixa de peers cobre `0.1.x` e `0.2.x`; fora dela, conceda isenção explícita com `dsh plugin --profile <name> allow-version <pkg@ver> --dsh-version <runtime> --accept-risk`.
+- **Uma regra não executou**: leia o arranjo `skipped`.
+- **`check` informa `manifest-peers` como falha**: problema conhecido do `dsh-plugin-dev`; o runtime aplica a compatibilidade na instalação.
+- **Os horários parecem deslocados**: toda a aritmética é de hora local sobre as cadeias fornecidas.
+
+## Development
+
+```sh
+pnpm install
+pnpm run typecheck
+pnpm test
+pnpm run build
+node ../scripts/sync-shared.mjs dsh-drill-script-check
+```
+
+O último comando copia o kit compartilhado de `../_shared` para `src/shared/`; execute-o novamente após cada alteração compartilhada.
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 dsh-drill-script-check contributors.

package/README-zh.md

@@ -0,0 +1,92 @@
+# dsh-drill-script-check
+
+**Boundary:** this plugin checks an **应急演练脚本** for completeness and arithmetic — that each step names its
+phase and script content, that it names a commander, that the response level comes from your vocabulary, that a
+step with an action lists the resources it needs, that the step durations total the drill's planned duration, that
+key checkpoints state their judgement condition, that step numbers are unique, and that the script names its drill
+and organiser. It does **not** decide whether a drill was realistic or effective, whether the response level was
+right, whether the actions were correct, or whether the drill met its objectives.
+
+> ### ⚠️ Read this before trusting a citation in the report
+>
+> **Every `excerpt` in this plugin's rule pack says, in so many words, that the clause text was not
+> obtained.** The regime lives in AQ/T 9007—2019, 《生产安全事故应急条例》(国务院令第708号) and each
+> institution's emergency plans. The verification pass could not retrieve verbatim clause text, so rather than
+> paraphrase a quotation the pack states the gap in the `excerpt` field itself and puts the honest reasoning in
+> `note`. Every rule is therefore `warn` or `info`, and a test asserts that no rule claims a quotation it does
+> not have. **When the texts are in hand, replace each `excerpt` with the real clause and raise `kind` to
+> `direct`.**
+>
+> **No response-level scale is built in.** Levels differ between plan systems — general / larger / major /
+> especially major, or a unit's own Ⅰ–Ⅳ — so `DR-003` reports itself in `skipped` until you configure your
+> vocabulary, and it never judges which level an event should trigger. That is the incident commander's call.
+>
+> The resource rule fires only when a script action is present, so a step that is purely informational is not
+> asked for equipment. And the duration total is read from the header, where a drill's planned length normally
+> lives.
+
+## Compatibility
+
+| 项目 | 状态 |
+|---|---|
+| Harness | 对等版本范围 `>=0.1.2-rc.1 <0.2.0 \|\| >=0.2.0-0 <0.3.0` —— 已实测同时接受 `0.2.0-rc.2` 与 `0.2.1-alpha.1`。**刻意不声明 `engines.dsh`**：它没有任何读取者，也无法拒装任何宿主 |
+| Node | `^22.19.0 || >=24.0.0` |
+| 平台 | 全平台（纯 ESM；无原生代码、无联网、不调用模型） |
+| 工具模式 | `native` / `ptc` / `both` 均可；批量校验整个目录时建议 `ptc`，schema 成本只付一次 |
+
+## What it does
+
+规则表、字段说明与行为细节见 [README.md](README.md#what-it-does)（英文主版本）。本插件只列出材料与所引条款之间的字面差异，并对无法执行的检查在 `skipped` 中逐项说明。
+
+## Install
+
+```sh
+dsh plugin --profile <name> add dsh-drill-script-check
+dsh --profile <name> --dump-config | grep 'dsh-drill-script-check'
+```
+
+## Configuration
+
+全部可调参数都在 `src/config.ts` 的 Schemastery schema 中，只改 `cordis.yml` 即可生效，无需改代码；逐条阈值在 `rules/` 下的规则库文件里。
+
+| 键 | 类型 | 默认值 | 说明 |
+|---|---|---|---|
+| `rulesFile` | string | `rules/drill-script-check.yaml` | 规则库文件路径，相对插件包根目录 |
+| `disabledRules` | string[] | `[]` | 要停用的规则 id 列表；每条都会出现在 `skipped` 中 |
+| `onlyRules` | string[] | `[]` | 只执行这些规则 id；留空表示执行全部规则 |
+| `skipNotes` | string | `""` | 附加到每条 `skipped` 说明后的备注 |
+| `timeoutMs` | number | `120000` | 工具协作式超时预算（毫秒） |
+
+## Material format
+
+支持 JSON 与 YAML。完整字段示例见 [README.md](README.md#material-format)（英文主版本）。字段在读取层是可选的，由检查引擎校验，因此部分导出的材料会产生"缺项"类差异，而不是让程序崩溃。
+
+## Rule sources
+
+规则数据与代码分离，每条规则都带文件名、文号、按原文自身编号体系的条款号、逐字摘录与来源地址。加载期强制：摘录必须是真实引文且不少于八个字符；依据仅为原则性条款（`kind: derived-from-principle`，严重级上限 `warn`）或本机构配置（`kind: institutional-configuration`，上限 `info`）的检查不得标为 `error`。夸大依据的规则库会在加载期失败，而不会产出一份看起来很有底气的报告。
+
+核验中确认的边界与"刻意没有作出的结论"见 [README.md](README.md#rule-sources)（英文主版本）与随包的 `rules/evidence/` 目录。
+
+## Troubleshooting
+
+- **插件装上了但工具不出现**：确认 `main` 指向 `lib/index.mjs` 且 `pnpm run build` 已生成该文件；`main` 写错会让加载器静默跳过该条目。
+- **`dsh plugin add` 报版本不兼容**：peer 范围覆盖 `0.1.x` 与 `0.2.x`；若运行时在其之外，可显式豁免：`dsh plugin --profile <name> allow-version <包名@版本> --dsh-version <runtime> --accept-risk`
+- **某条规则没有执行**：查看 `skipped` 数组，其中写明了规则 id 与原因。
+- **`check` 报 `manifest-peers` 失败**：静态检查器比对的是一份早于 0.2 世代的硬编码 peer 范围；安装期的 peer 校验以运行时为准。这是 `dsh-plugin-dev` 的已知上游问题。
+- **时间看起来偏移**：全部计算都是对输入字符串做墙上时钟运算，不做时区换算。
+
+## Development
+
+```sh
+pnpm install
+pnpm run typecheck
+pnpm test
+pnpm run build
+node ../scripts/sync-shared.mjs dsh-drill-script-check
+```
+
+第 4 项把 `../_shared` 的共享件同步进 `src/shared/`；每次改动共享件后都要重跑。
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 dsh-drill-script-check contributors.

package/README.md

@@ -1,3 +1,137 @@
-# Temporary Holding Version
+# dsh-drill-script-check
 
-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.
+**Boundary:** this plugin checks an **应急演练脚本** for completeness and arithmetic — that each step names its
+phase and script content, that it names a commander, that the response level comes from your vocabulary, that a
+step with an action lists the resources it needs, that the step durations total the drill's planned duration, that
+key checkpoints state their judgement condition, that step numbers are unique, and that the script names its drill
+and organiser. It does **not** decide whether a drill was realistic or effective, whether the response level was
+right, whether the actions were correct, or whether the drill met its objectives.
+
+> ### ⚠️ Read this before trusting a citation in the report
+>
+> **Every `excerpt` in this plugin's rule pack says, in so many words, that the clause text was not
+> obtained.** The regime lives in AQ/T 9007—2019, 《生产安全事故应急条例》(国务院令第708号) and each
+> institution's emergency plans. The verification pass could not retrieve verbatim clause text, so rather than
+> paraphrase a quotation the pack states the gap in the `excerpt` field itself and puts the honest reasoning in
+> `note`. Every rule is therefore `warn` or `info`, and a test asserts that no rule claims a quotation it does
+> not have. **When the texts are in hand, replace each `excerpt` with the real clause and raise `kind` to
+> `direct`.**
+>
+> **No response-level scale is built in.** Levels differ between plan systems — general / larger / major /
+> especially major, or a unit's own Ⅰ–Ⅳ — so `DR-003` reports itself in `skipped` until you configure your
+> vocabulary, and it never judges which level an event should trigger. That is the incident commander's call.
+>
+> The resource rule fires only when a script action is present, so a step that is purely informational is not
+> asked for equipment. And the duration total is read from the header, where a drill's planned length normally
+> lives.
+
+## Compatibility
+
+| Surface | Status |
+|---|---|
+| Harness | Peer range `>=0.1.2-rc.1 <0.2.0 \|\| >=0.2.0-0 <0.3.0` — verified to accept both `0.2.0-rc.2` and `0.2.1-alpha.1`. `engines.dsh` is deliberately not declared: it has no reader and cannot reject a host |
+| Node | `^22.19.0 || >=24.0.0` |
+| Platforms | All (plain ESM; no native code, no network, no model call) |
+| Tool mode | Works in `native`, `ptc` and `both`; for a full script use `ptc` |
+
+## What it does
+
+Registers the `drill_script_check` tool. It reads one drill script — the drill header plus one row per step —
+applies a versioned rule pack, and returns a report.
+
+| Rule | Check | Severity | Basis kind |
+|---|---|---|---|
+| `DR-001` | the phase and script content are recorded | warn | principle |
+| `DR-002` | a commander is named | warn | principle |
+| `DR-003` | the response level comes from your vocabulary (off by default) | info | local |
+| `DR-004` | a step with an action lists its resources | warn | principle |
+| `DR-005` | step durations total the planned duration | warn | principle |
+| `DR-006` | a checkpoint states its judgement condition | warn | principle |
+| `DR-007` | step numbers are unique | warn | principle |
+| `DR-008` | the script names its drill and organiser | warn | principle |
+
+## Install
+
+```sh
+dsh plugin --profile <name> add dsh-drill-script-check
+dsh --profile <name> --dump-config | grep 'dsh-drill-script-check'
+```
+
+## Configuration
+
+| Key | Type | Default | Description |
+|---|---|---|---|
+| `rulesFile` | string | `rules/drill-script-check.yaml` | Rule-pack path, relative to the package root |
+| `disabledRules` | string[] | `[]` | Rule ids to stop running; each appears in `skipped` |
+| `onlyRules` | string[] | `[]` | Run only these rule ids; empty runs every rule |
+| `skipNotes` | string | `""` | Note appended to every `skipped` reason |
+| `timeoutMs` | number | `120000` | Cooperative tool timeout budget |
+
+Rule-level parameters worth knowing:
+
+- `DR-003` `values` — your response levels, e.g. `[Ⅰ级, Ⅱ级, Ⅲ级, Ⅳ级]`. Empty means no check.
+- `DR-005` `field` / `headerField` / `tolerance` — the duration column and the header total it must match.
+- `DR-004` `conditionField` / `requiredFields` — what triggers the resource requirement.
+
+## Material format
+
+The tool accepts JSON or YAML:
+
+```yaml
+drillName: 某某装置泄漏事故应急演练
+drillType: 综合演练
+organizer: 某某公司应急管理部
+plannedAt: 2026-06-10
+totalDurationMin: '15'
+rows:
+  - { 序号: '1', 演练阶段: 预警与信息报告,
+      脚本内容: 值班员发现泄漏报警，电话报告应急指挥部,
+      指挥人: 张指挥, 参演人员: 值班员、调度员,
+      所需资源: 对讲机 4 台、气体检测仪 2 台, 计划时长: '15',
+      响应级别: Ⅲ级, 关键节点: 指挥部确认接报并启动响应（判定条件：指挥人下达启动指令） }
+```
+
+Column names are matched case-insensitively and ignoring spaces, underscores and hyphens; the script's own column
+names are kept, so a finding names the column it read. The duration total may live in the header.
+
+## Rule sources
+
+Rule data lives in `rules/drill-script-check.yaml`. The pack's header states the citation gap in full, and each
+rule's `note` repeats the part that matters for that rule. The load-time guard that normally enforces "an excerpt
+must be a real quotation of at least eight characters" cannot tell a quotation from a description — so this pack
+leans on the header, the per-rule notes and a test that asserts every `excerpt` admits the gap.
+
+## Troubleshooting
+
+- **`DR-003` never runs.** Its vocabulary is empty; fill it with the levels your emergency plans use.
+- **`DR-005` reports itself as skipped.** The header carries no planned duration, or no step records one.
+- **`DR-005` fires although the script looks right.** The step durations disagree with the header total — usually
+  a missing step or a mistyped figure.
+- **`DR-004` fires on a step I consider informational.** The step has script content, so the rule wants its
+  resources named. If the step genuinely needs none, say so in the cell rather than leaving it blank.
+- **`DR-007` fires on two steps of one phase.** Give each step its own number.
+- **The plugin installs but the tool never appears.** Check that `main` resolves to `lib/index.mjs` and
+  that `pnpm run build` produced it; a wrong `main` makes the loader skip the entry silently.
+- **`dsh plugin add` refuses the package as incompatible.** The peer range covers `0.1.x` and `0.2.x`; if
+  your runtime sits outside it, grant an explicit exemption:
+  `dsh plugin --profile <name> allow-version dsh-drill-script-check@0.1.0 --dsh-version <runtime> --accept-risk`
+- **`check` reports `manifest-peers` as failed.** The static checker compares against a hard-coded peer
+  range that predates the 0.2 line. The runtime enforces peer compatibility at install time, so the
+  declared range is the correct one; this is a known upstream issue in `dsh-plugin-dev`.
+
+## Development
+
+```sh
+pnpm install
+pnpm run typecheck   # tsc --noEmit
+pnpm test            # vitest, the shared table-plugin suite plus paired fixtures
+pnpm run build       # tsdown -> lib/index.mjs + lib/index.d.mts
+node ../scripts/sync-shared.mjs dsh-drill-script-check   # refresh src/shared from ../_shared
+```
+
+The plugin is **data-only**: `src/model.ts` declares the table shape, the shared kit supplies the reader and the
+check engine, and the rule pack declares every check.
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 dsh-drill-script-check contributors.

package/cordis.patch.yml

@@ -0,0 +1,8 @@
+# dsh-drill-script-check bundle layer: register this plugin as a bundle row.
+# This file is the `dsh.bundle.patch` layer (see package.json#dsh.bundle.patch).
+# Layer semantics: a YAML array of row verbs; `insert` adds plugin rows to the
+# composed config. A row's `id` must be unique within the layer stack; `name`
+# resolves the plugin module through the installed package (package.json#main).
+- insert:
+    - id: dsh-drill-script-check
+      name: dsh-drill-script-check

package/icon.svg

@@ -0,0 +1,6 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" role="img" aria-label="Drill script check">
+  <rect width="64" height="64" rx="12" fill="#0f766e"/>
+  <path d="M16 20h32M16 32h22M16 44h26" stroke="#ffffff" stroke-width="4" stroke-linecap="round"/>
+  <circle cx="50" cy="46" r="9" fill="#ffffff"/>
+  <path d="M46 46l3 3 5-6" stroke="#0f766e" stroke-width="3" stroke-linecap="round" stroke-linejoin="round" fill="none"/>
+</svg>

package/lib/index.d.mts

@@ -0,0 +1,52 @@
+import Schema from "@deepseek-ai/schemastery";
+import { Context } from "@deepseek-ai/cordis";
+//#region src/config.d.ts
+/**
+ * Every tunable lives here so an operator can change behaviour from
+ * `cordis.yml` without editing code (the family's "no hard-coded tunables"
+ * redline). The rule pack itself is data as well and can be pointed elsewhere.
+ */
+interface Config {
+  /** Rule-pack path relative to the plugin package root. */
+  rulesFile: string;
+  /** Rule ids disabled for this deployment. */
+  disabledRules: string[];
+  /** When non-empty, only these rule ids run. */
+  onlyRules: string[];
+  /** Extra note appended to every `skipped` reason. */
+  skipNotes: string;
+  /** Tool timeout budget in milliseconds. */
+  timeoutMs: number;
+}
+declare const Config: Schema<Config>;
+//#endregion
+//#region src/index.d.ts
+declare const name = "dsh-drill-script-check";
+declare const inject: string[];
+/** Tool id exposed to the model, and the row id in `cordis.patch.yml`. */
+declare const TOOL_NAME = "drill_script_check";
+/**
+ * Locate a package-owned file such as the rule pack.
+ *
+ * Resolution order: absolute path, then every ancestor of the module directory,
+ * then the process working directory. A wrong silent fallback would build a
+ * report from the wrong rule pack, so a miss throws with the paths tried.
+ *
+ * @param relative - configured path, relative to the plugin package root.
+ * @returns the resolved absolute path.
+ * @throws Error naming every location tried, when the file is absent.
+ */
+declare function resolvePackageFile(relative: string): string;
+/**
+ * Register the checker tool.
+ *
+ * Registration is an effect: `ctx.tools.register` returns the disposer that
+ * removes the tool when this plugin unloads, which is what keeps the plugin
+ * hot-reloadable.
+ *
+ * @param ctx - plugin context, with `tools` already available.
+ * @param config - validated configuration.
+ */
+declare function apply(ctx: Context, config: Config): () => void;
+//#endregion
+export { Config, TOOL_NAME, apply, inject, name, resolvePackageFile };