dsh-power-ticket-check 0.2.8 → 0.2.10

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [0.2.9] - 2026-10-18
+
+### Changed
+
+- Move `tsdown` and `typescript` from runtime dependencies to devDependencies; a published checker no longer pulls a build chain into the profile. Same rollout as the 0.2.11 pilot.
+
 ## [0.2.8] - 2026-10-18
 
 ### Changed

package/README-es.md

@@ -1,6 +1,14 @@
 # dsh-power-ticket-check — Verificación de la completitud del permiso de trabajo eléctrico y del orden de emisión, autorización y cierre
 
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
+```sh
+dsh plugin --profile <name> add dsh-power-ticket-check
+```
+
+
 [![DSH Market](https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed-en.svg)](https://dsh.market/)
+[![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-power-ticket-check?metric=downloads)](https://dshfind.com/en/plugins/PerryLink/dsh-power-ticket-check?ref=badge)
 
 `dsh-power-ticket-check` lee un **电力工作票** como un mapa plano de los nombres de columna del propio formulario a sus valores, junto con los roles que figuran en él, y comprueba lo que puede exigirse a un formulario: que estén rellenas todas las columnas de su `requiredFields` configurado, que el 工作票种类 figure entre los que declara su implantación, que 签发时间 → 许可时间 → 终结时间 formen una secuencia físicamente posible, que un 延期时间 desplace el final hacia adelante y no sea anterior a la autorización, que los roles configurados como exclusivos los desempeñen personas distintas, y que el texto de medidas de seguridad y de autorización contenga los cinco términos de 安全技术措施 y los tres de 许可手续 que el paquete busca. Las comprobaciones que no pudieron ejecutarse se listan en `skipped` con su motivo, en lugar de pasar en silencio.
 
@@ -13,14 +21,48 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 
 ## Cómo se ve la salida
 
-![Terminal demo of dsh-power-ticket-check: real output over its PT-003 fixture](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-hero.png)
+![Diagrama de flujo de dsh-power-ticket-check: documento → reglas → hallazgos.](docs/assets/dsh-power-ticket-check-flow.svg)
+
+*Resumen del flujo: documento → reglas → hallazgos. Los ejemplos siguientes usan la superficie de comandos real.*
 
-![Animated terminal demo of dsh-power-ticket-check](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-demo.gif)
 
 Salida real de este plugin sobre su propio fixture de prueba `PT-003` — no es un montaje. El paquete de reglas no inventa citas, así que cada hallazgo nombra la cláusula aplicada y advierte que su texto no se obtuvo.
 
 ## Qué responde
 
+### Ejemplos
+
+La tabla siguiente es el conjunto de ejemplos: la primera fila es el caso detallado y las demás son casos breves.
+
+
+#### Salida detallada
+
+**Herramienta** `power_ticket_check`
+
+**Entrada**
+
+~~~json
+{"工作票编号":"DL-2026-0001","工作票种类":"电气第一种工作票","安全措施":"应停电、验电、装设接地线。"}
+~~~
+ 
+**Salida**
+
+~~~json
+{
+  "id": "dsh-power-ticket-check.PT-006.104aebcf",
+  "ruleId": "PT-006",
+  "severity": "error",
+  "locator": {
+    "column": "安全措施"
+  },
+  "found": "安全措施文本中未出现 2 项：悬挂标示牌、装设遮栏",
+  "expected": "在电气设备上工作，应有停电、验电、装设接地线、悬挂标示牌和装设遮栏（围栏）等保证安全的技术措施",
+  "fix": "核对票面是否写全五项；本条只核对是否写到，不判断措施内容是否与现场相符"
+}
+~~~
+
+*Observado en `dsh-power-ticket-check/tests/fixtures/PT-006/PT-006-unsafe.json (cases.json expects 1×PT-006); executed parseMaterial+runCheck, checkedAt=2026-10-06T00:00:00.000Z`*
+
 | Usted pregunta | Qué responde |
 |---|---|
 | Tal como viene, aprueba todos los permisos que le paso, ¿por qué? | Porque `PT-001` se declara a sí misma en `skipped`, no como aprobado. Su lista `requiredFields` viene vacía, así que la regla no puede ejecutarse; rellénela con las columnas que exige su propio formulario. Aun configurada, `PT-001` comprueba que la columna esté rellena, no que el valor sea correcto, y su nivel es `info`. |
@@ -121,6 +163,10 @@ node ../scripts/sync-shared.mjs dsh-power-ticket-check
 
 El último comando copia el kit compartido de `../_shared` a `src/shared/`; vuelva a ejecutarlo tras cada cambio compartido.
 
+## PerryLink DSH Plugin Family
+
+Full family index: [choose a checker by material](https://perrylink.github.io/zh/checkers/choose/) and [all plugins](https://github.com/PerryLink). This repository is one of them.
+
 ## License
 
 [Apache License 2.0](LICENSE) © 2026 dsh-power-ticket-check contributors.

package/README-hi.md

@@ -1,6 +1,9 @@
 # dsh-power-ticket-check — विद्युत कार्य-अनुज्ञप्ति की पूर्णता तथा निर्गमन, अनुमति और समापन के क्रम की जाँच
 
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
 [![DSH Market](https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed-en.svg)](https://dsh.market/)
+[![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-power-ticket-check?metric=downloads)](https://dshfind.com/en/plugins/PerryLink/dsh-power-ticket-check?ref=badge)
 
 `dsh-power-ticket-check` एक **电力工作票** को उसके अपने कॉलम नामों से मानों तक के सपाट मैपिंग के रूप में पढ़ता है — साथ में उस पर अंकित भूमिकाएँ — और उस अनुज्ञप्ति की वह जाँच करता है जो एक फ़ॉर्म से अपेक्षित की जा सकती है: आपके कॉन्फ़िगर किए गए `requiredFields` के हर कॉलम में मान भरा हो, 工作票种类 आपकी संस्था द्वारा सूचीबद्ध किस्मों में से हो, 签发时间 → 许可时间 → 终结时间 का क्रम भौतिक रूप से संभव हो, 延期时间 अंत को आगे बढ़ाए और अनुमति से पहले न हो, जिन भूमिकाओं को आपने अलग-अलग रखने के लिए कॉन्फ़िगर किया है वे अलग-अलग व्यक्तियों के हों, तथा सुरक्षा-उपाय और अनुमति के पाठ में नियम-पैक द्वारा खोजे जाने वाले 安全技术措施 के पाँच और 许可手续 के तीन शब्द मौजूद हों। जो जाँचें चल नहीं सकीं, वे चुपचाप पास होने के बजाय कारण के साथ `skipped` में दर्ज होती हैं।
 
@@ -13,14 +16,48 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 
 ## आउटपुट कैसा दिखता है
 
-![Terminal demo of dsh-power-ticket-check: real output over its PT-003 fixture](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-hero.png)
+![dsh-power-ticket-check कार्यप्रवाह आरेख: दस्तावेज़ → नियम → निष्कर्ष।](docs/assets/dsh-power-ticket-check-flow.svg)
+
+*कार्यप्रवाह: दस्तावेज़ → नियम → निष्कर्ष। नीचे के उदाहरण वास्तविक कमांड सतह का उपयोग करते हैं।*
 
-![Animated terminal demo of dsh-power-ticket-check](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-demo.gif)
 
 इस प्लगइन का अपने ही `PT-003` टेस्ट फ़िक्स्चर पर वास्तविक आउटपुट — कोई नकली चित्र नहीं। नियम-पैक उद्धरण नहीं गढ़ता, इसलिए हर निष्कर्ष लागू किए गए खंड का नाम और यह भी बताता है कि उसका मूल पाठ इस बार प्राप्त नहीं हुआ।
 
 ## यह किन सवालों का जवाब देता है
 
+### उदाहरण
+
+नीचे दी गई तालिका उदाहरण-समुच्चय है: पहली पंक्ति विस्तृत केस है, बाकी संक्षिप्त केस हैं।
+
+
+#### विस्तृत आउटपुट
+
+**उपकरण** `power_ticket_check`
+
+**इनपुट**
+
+~~~json
+{"工作票编号":"DL-2026-0001","工作票种类":"电气第一种工作票","安全措施":"应停电、验电、装设接地线。"}
+~~~
+ 
+**आउटपुट**
+
+~~~json
+{
+  "id": "dsh-power-ticket-check.PT-006.104aebcf",
+  "ruleId": "PT-006",
+  "severity": "error",
+  "locator": {
+    "column": "安全措施"
+  },
+  "found": "安全措施文本中未出现 2 项：悬挂标示牌、装设遮栏",
+  "expected": "在电气设备上工作，应有停电、验电、装设接地线、悬挂标示牌和装设遮栏（围栏）等保证安全的技术措施",
+  "fix": "核对票面是否写全五项；本条只核对是否写到，不判断措施内容是否与现场相符"
+}
+~~~
+
+*स्रोत `dsh-power-ticket-check/tests/fixtures/PT-006/PT-006-unsafe.json (cases.json expects 1×PT-006); executed parseMaterial+runCheck, checkedAt=2026-10-06T00:00:00.000Z`*
+
 | आपका सवाल | इसका जवाब |
 |---|---|
 | जैसा यह आता है, मेरी हर अनुज्ञप्ति इसमें पास हो जाती है — क्यों? | क्योंकि `PT-001` स्वयं को पास के रूप में नहीं, `skipped` में दर्ज करता है। उसकी `requiredFields` सूची खाली आती है, इसलिए यह नियम चल ही नहीं सकता; उसमें अपने फ़ॉर्म के अनिवार्य कॉलम भरें। कॉन्फ़िगर होने पर भी `PT-001` यह देखता है कि कॉलम भरा है, यह नहीं कि उसमें लिखा मान सही है, और उसका स्तर `info` है। |
@@ -121,6 +158,10 @@ node ../scripts/sync-shared.mjs dsh-power-ticket-check
 
 अंतिम कमांड `../_shared` का साझा किट `src/shared/` में कॉपी करता है; हर साझा बदलाव के बाद इसे दोबारा चलाएँ।
 
+## PerryLink DSH Plugin Family
+
+Full family index: [choose a checker by material](https://perrylink.github.io/zh/checkers/choose/) and [all plugins](https://github.com/PerryLink). This repository is one of them.
+
 ## License
 
 [Apache License 2.0](LICENSE) © 2026 dsh-power-ticket-check contributors.

package/README-pt.md

@@ -1,6 +1,14 @@
 # dsh-power-ticket-check — Verificação da completude do permiso de trabalho elétrico e da ordem de emissão, autorização e encerramento
 
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
+```sh
+dsh plugin --profile <name> add dsh-power-ticket-check
+```
+
+
 [![DSH Market](https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed-en.svg)](https://dsh.market/)
+[![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-power-ticket-check?metric=downloads)](https://dshfind.com/en/plugins/PerryLink/dsh-power-ticket-check?ref=badge)
 
 `dsh-power-ticket-check` lê um **电力工作票** como um mapa plano dos nomes das colunas do próprio formulário para os respetivos valores, em conjunto com os papéis nele indicados, e verifica o que se pode exigir a um formulário: que todas as colunas do seu `requiredFields` configurado estejam preenchidas, que o 工作票种类 conste dos que a sua implantação declara, que 签发时间 → 许可时间 → 终结时间 formem uma sequência fisicamente possível, que um 延期时间 empurre o fim para a frente e não seja anterior à autorização, que os papéis configurados como exclusivos sejam desempenhados por pessoas diferentes, e que o texto das medidas de segurança e da autorização contenha os cinco termos de 安全技术措施 e os três de 许可手续 que o pacote procura. As verificações que não puderam ser executadas são listadas em `skipped` com o respetivo motivo, em vez de passarem em silêncio.
 
@@ -13,14 +21,48 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 
 ## Como é a saída
 
-![Terminal demo of dsh-power-ticket-check: real output over its PT-003 fixture](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-hero.png)
+![Diagrama de fluxo de dsh-power-ticket-check: documento → regras → achados.](docs/assets/dsh-power-ticket-check-flow.svg)
+
+*Visão geral do fluxo: documento → regras → achados. Os exemplos abaixo usam a superfície real de comandos.*
 
-![Animated terminal demo of dsh-power-ticket-check](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-demo.gif)
 
 Saída real deste plugin sobre o seu próprio fixture de teste `PT-003` — não é uma simulação. O pacote de regras não inventa citações, por isso cada achado nomeia a cláusula aplicada e avisa que o seu texto não foi obtido.
 
 ## O que ele responde
 
+### Exemplos
+
+A tabela abaixo é o conjunto de exemplos: a primeira linha é o caso detalhado e as demais são casos curtos.
+
+
+#### Saída detalhada
+
+**Ferramenta** `power_ticket_check`
+
+**Entrada**
+
+~~~json
+{"工作票编号":"DL-2026-0001","工作票种类":"电气第一种工作票","安全措施":"应停电、验电、装设接地线。"}
+~~~
+ 
+**Saída**
+
+~~~json
+{
+  "id": "dsh-power-ticket-check.PT-006.104aebcf",
+  "ruleId": "PT-006",
+  "severity": "error",
+  "locator": {
+    "column": "安全措施"
+  },
+  "found": "安全措施文本中未出现 2 项：悬挂标示牌、装设遮栏",
+  "expected": "在电气设备上工作，应有停电、验电、装设接地线、悬挂标示牌和装设遮栏（围栏）等保证安全的技术措施",
+  "fix": "核对票面是否写全五项；本条只核对是否写到，不判断措施内容是否与现场相符"
+}
+~~~
+
+*Observado em `dsh-power-ticket-check/tests/fixtures/PT-006/PT-006-unsafe.json (cases.json expects 1×PT-006); executed parseMaterial+runCheck, checkedAt=2026-10-06T00:00:00.000Z`*
+
 | Você pergunta | O que ele responde |
 |---|---|
 | Tal como vem, aprova todos os permís que lhe passo, por quê? | Porque `PT-001` declara-se a si mesma em `skipped`, e não como aprovada. A sua lista `requiredFields` vem vazia, pelo que a regra não pode ser executada; preencha-a com as colunas que o seu próprio formulário exige. Mesmo configurada, `PT-001` verifica que a coluna está preenchida, não que o valor esteja correto, e o seu nível é `info`. |
@@ -121,6 +163,10 @@ node ../scripts/sync-shared.mjs dsh-power-ticket-check
 
 O último comando copia o kit compartilhado de `../_shared` para `src/shared/`; execute-o novamente após cada alteração compartilhada.
 
+## PerryLink DSH Plugin Family
+
+Full family index: [choose a checker by material](https://perrylink.github.io/zh/checkers/choose/) and [all plugins](https://github.com/PerryLink). This repository is one of them.
+
 ## License
 
 [Apache License 2.0](LICENSE) © 2026 dsh-power-ticket-check contributors.

package/README-zh.md

@@ -1,6 +1,18 @@
 # dsh-power-ticket-check — 电力工作票要素齐备性与签发许可终结顺序核对
 
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
+<!-- topblock:v1 -->
+> **这是什么**　电力工作票要素核对。输出一份「哪一行、哪一栏、差什么」的清单。
+> **给谁用**　电力运维、工作票签发人；不用懂命令行。
+> **你交什么**　这项核对用到的原始材料（表格、清单或文书）；不改原件。Excel 可先转成 JSON/YAML，对话里也能代转。
+> **它不做什么**　不判合规、不认定责任、不替代审核人；只列材料内部能逐条指认的差异。
+> **怎么开始**　在 WorkBuddy / 扣子搜「安全合规核对包」（本检查是其中一项；上架以商城为准）；或命令行：
+> `dsh plugin --profile <name> add dsh-power-ticket-check`
+<!-- /topblock:v1 -->
+
 [![DSH Market](https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed-en.svg)](https://dsh.market/)
+[![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-power-ticket-check?metric=downloads)](https://dshfind.com/en/plugins/PerryLink/dsh-power-ticket-check?ref=badge)
 
 `dsh-power-ticket-check` 读取一份 **电力工作票**——以票面栏目名为键、栏目取值为值的平铺映射，外加票上列出的人员角色——按一张票面能被要求到的范围核对：本机构配置的 `requiredFields` 各栏是否都已填写、工作票种类是否在本机构列出的票种之内、签发时间 → 许可时间 → 终结时间 的顺序是否物理上成立、延期时间是否把结束时间向后推且不早于许可时间、本机构配置为须分设的角色是否由不同人员担任，以及安全措施与许可文本中是否出现规则库要求核对的安全技术措施五项与许可手续三项关键词。未能执行的检查逐条列在 `skipped` 并写明原因，而不是静默通过。
 
@@ -13,14 +25,48 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 
 ## 实际输出长什么样
 
-![Terminal demo of dsh-power-ticket-check: real output over its PT-003 fixture](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-hero.png)
+![dsh-power-ticket-check 工作流图：文档 → 规则包 → 核对结果。](docs/assets/dsh-power-ticket-check-flow.svg)
+
+*工作流概览：文档 → 规则包 → 核对结果。下面的示例使用实际命令面。*
 
-![Animated terminal demo of dsh-power-ticket-check](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-demo.gif)
 
 本插件对自己 `PT-003` 测试夹具的**真实输出**，不是示意图。规则库不伪造引文，因此每条发现都会同时写明所引条款，以及该条款原文本次未取得。
 
 ## 它回答什么问题
 
+### 示例
+
+下表是示例集：第一行是详细走查，其余行是简短案例。
+
+
+#### 详细输出
+
+**工具** `power_ticket_check`
+
+**输入**
+
+~~~json
+{"工作票编号":"DL-2026-0001","工作票种类":"电气第一种工作票","安全措施":"应停电、验电、装设接地线。"}
+~~~
+ 
+**输出**
+
+~~~json
+{
+  "id": "dsh-power-ticket-check.PT-006.104aebcf",
+  "ruleId": "PT-006",
+  "severity": "error",
+  "locator": {
+    "column": "安全措施"
+  },
+  "found": "安全措施文本中未出现 2 项：悬挂标示牌、装设遮栏",
+  "expected": "在电气设备上工作，应有停电、验电、装设接地线、悬挂标示牌和装设遮栏（围栏）等保证安全的技术措施",
+  "fix": "核对票面是否写全五项；本条只核对是否写到，不判断措施内容是否与现场相符"
+}
+~~~
+
+*来源 `dsh-power-ticket-check/tests/fixtures/PT-006/PT-006-unsafe.json (cases.json expects 1×PT-006); executed parseMaterial+runCheck, checkedAt=2026-10-06T00:00:00.000Z`*
+
 | 你会问 | 它怎么答 |
 |---|---|
 | 出厂状态下，随便一份工作票都能通过，为什么？ | 因为 `PT-001` 是以 `skipped` 自报，不是判定通过。它的 `requiredFields` 清单出厂为空，本条无法执行；请按本机构票面把必填栏目填进去。即便配置好后，`PT-001` 也只核对栏目是否填写，不判断填写内容是否正确，且严重级为 `info`。 |
@@ -36,35 +82,17 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 |---|---|---|
 | 《电力安全工作规程 发电厂和变电站电气部分》 | GB 26860—2011 | PT-001, PT-002, PT-003, PT-004, PT-005, PT-006, PT-007 |
 
-**Boundary:** this plugin checks one **电力工作票** for what a form can be held to — that the required
-boxes are filled, that 签发 / 许可 / 终结 happened in an order that is physically possible, that 延期
-moves the end forward, and that roles you require to be separate are held by different people. It does
-**not** judge whether the safety measures written on the ticket were adequate, **does not** say which
-kind of ticket a job needs, and **does not** verify that anyone's qualification is real.
+**边界（中文译文，以英文原文为准）：** 本插件按一张票面可以被要求到的范围核对一份 **电力工作票**——必填栏目是否填写，签发 / 许可 / 终结 的发生顺序是否物理上成立，延期是否把结束时间向后推，以及你要求分设的角色是否由不同人员担任。它**不**判断票面所写的安全措施是否充分，**不**指明某项作业需要哪一种工作票，也**不**核实任何人的资格是否真实。
 
-> ### ⚠️ Three things this plugin refuses to do, and the effect tier that fixes its severities
+> ### ⚠️ 本插件拒绝做的三件事，以及决定其严重级的效力层级（以英文原文为准）
 >
-> **1. It respects the standard's own effect tier.** GB 26860—2011's foreword says, verbatim,
-> 「本标准的第5章和7.3.4为推荐性，其余为强制性」 — **the work-ticket regime sits in the *recommendatory*
-> chapter 5.** So every rule resting on chapter 5 ships at `warn` or `info` and **nothing there can block a
-> workflow**. `PT-006` (the five safety technical measures, clause 6.1.1) is the **only** `error`, because
-> chapter 6 is mandatory. `PT-007` (the permit formalities, clause 5.5.1) is a `warn`; its note explains that
-> an institution which wants those formalities to block can raise it by editing the rule pack, with no code
-> change. A test asserts both directions: no chapter-5 rule is an `error`, and `PT-006` is the sole one.
+> **1. 它尊重标准自身的效力层级。** GB 26860—2011 的前言逐字写着：「本标准的第5章和7.3.4为推荐性，其余为强制性」——**工作票制度位于*推荐性*的第 5 章。** 因此凡以第 5 章为依据的规则，出厂均为 `warn` 或 `info`，**其中没有任何一条能阻断流程**。`PT-006`（安全技术措施五项，6.1.1 条）是**唯一**的 `error`，因为第 6 章是强制性的。`PT-007`（许可手续，5.5.1 条）是 `warn`；其 note 说明，希望这些手续能阻断流程的机构，可以修改规则库将其提高，无需改代码。有一项测试对两个方向都做了断言：没有任何第 5 章的规则是 `error`，且 `PT-006` 是唯一一条。
 >
-> **2. It does not adopt three claims that have no basis in the standards.** After reading GB 26860—2011
-> and GB 26859—2011 in full: there is **no** "第一种工作票应工作前一日送达" deadline anywhere; 5.3.12 and
-> 5.4.10 say only 「延期应办理手续」 with **no ceiling on duration or count**; and the statutory name is
-> **紧急抢修单** (5.2.4), not "事故应急抢修单". A test asserts the pack records all three.
+> **2. 它不采纳三项在标准中没有依据的说法。** 完整读过 GB 26860—2011 与 GB 26859—2011 之后：任何地方都**没有**「第一种工作票应工作前一日送达」这样的时限；5.3.12 与 5.4.10 只说「延期应办理手续」，**对延期时长与次数均无上限**；法定名称是**紧急抢修单**（5.2.4），而不是「事故应急抢修单」。有一项测试断言规则库记录了三者。
 >
-> **3. It does not treat the ticket layout as mandatory.** 5.1.2 says the ticket "**可**包含" those items,
-> and appendices A–D are marked **资料性附录** (informative) in the standard's contents. So `PT-001` ships
-> with an **empty** field list for you to fill from your own form, and reports at `info`.
+> **3. 它不把票面版式当作强制要求。** 5.1.2 说工作票「**可**包含」这些项目，而附录 A–D 在标准目录中标为**资料性附录**（informative）。因此 `PT-001` 出厂时字段清单为**空**，由你按本单位票面填写，并以 `info` 报告。
 >
-> Two more lists are yours: `PT-002`'s ticket kinds and `PT-005`'s exclusive role pairs. Both ship empty.
-> The plugin never judges whether the safety measures written on a ticket were adequate, which ticket
-> kind a job needs, or whether anyone's qualification is real — the standard sets out roles' **duties**
-> (5.4.1–5.4.5) and **no qualification conditions**.
+> 还有两份清单属于你：`PT-002` 的票种与 `PT-005` 的互斥角色对。两者出厂均为空。本插件从不判断票面所写的安全措施是否充分、某项作业需要哪一种工作票，也不判断任何人的资格是否真实——标准规定的是各角色的**职责**（5.4.1–5.4.5），**没有规定任何资格条件**。
 
 ## Compatibility
 
@@ -121,6 +149,10 @@ node ../scripts/sync-shared.mjs dsh-power-ticket-check
 
 第 4 项把 `../_shared` 的共享件同步进 `src/shared/`；每次改动共享件后都要重跑。
 
+## PerryLink DSH Plugin Family
+
+完整清单（62 个核查器 + 通用插件）见 [按材料选核查器](https://perrylink.github.io/zh/checkers/choose/)；本仓只是其中一个。
+
 ## License
 
 [Apache License 2.0](LICENSE) © 2026 dsh-power-ticket-check contributors.

package/README.md

@@ -1,6 +1,18 @@
 # dsh-power-ticket-check — Power work-ticket completeness and issue-permit-termination order check
 
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
+<!-- topblock:v1 -->
+> **What it is** — Power work-ticket completeness and issue-permit-termination order check. It returns a list of what is inconsistent, where, and what to fix.
+> **Who it is for** — power operations and permit issuers; no command line required.
+> **What you give it** — the source material the check works on (a table, register or document); the original is never modified. Excel can be converted to JSON/YAML first, in chat if the platform supports it.
+> **What it does not do** — no compliance verdict, no liability finding, no replacement for the reviewer; differences only.
+> **How to start** — search "Safety Compliance Suite" in WorkBuddy / Coze (this check is one part of it; availability as listed); or:
+> `dsh plugin --profile <name> add dsh-power-ticket-check`
+<!-- /topblock:v1 -->
+
 [![DSH Market](https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed-en.svg)](https://dsh.market/)
+[![dshfind](https://dshfind.com/api/badge/PerryLink/dsh-power-ticket-check?metric=downloads)](https://dshfind.com/en/plugins/PerryLink/dsh-power-ticket-check?ref=badge)
 
 `dsh-power-ticket-check` reads one **电力工作票** as a flat mapping of the ticket's own column names to their values, together with the roles named on it, and checks that ticket for what a form can be held to: that every column in your configured `requiredFields` is filled, that the 工作票种类 is one your deployment lists, that 签发时间 → 许可时间 → 终结时间 form a sequence that is physically possible, that a 延期时间 pushes the end forward and does not precede the permit, that roles you configured as exclusive are held by different people, and that the safety-measure and permit text carries the five 安全技术措施 terms and the three 许可手续 terms the pack looks for. Checks that could not run are listed in `skipped` with their reason rather than passing silently.
 
@@ -13,14 +25,46 @@ dsh --profile <name> --dump-config | grep 'dsh-power-ticket-check'
 
 ## What it looks like
 
-![Terminal demo of dsh-power-ticket-check: real output over its PT-003 fixture](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-hero.png)
+![Workflow diagram for dsh-power-ticket-check: document → rule pack → findings.](docs/assets/dsh-power-ticket-check-flow.svg)
+
+*Workflow overview: document → rule pack → findings. The examples below use the real command surface.*
 
-![Animated terminal demo of dsh-power-ticket-check](https://raw.githubusercontent.com/PerryLink/dsh-power-ticket-check/main/docs/assets/dsh-power-ticket-check-demo.gif)
 
-Real output from this plugin over its own `PT-003` test fixture — not a mock-up. The rule pack ships no invented quotations, so a finding names both the clause it applied and the fact that the clause text was not obtained.
 
 ## What it answers
 
+### Examples
+
+The table below is the example set: the first row is the detailed walkthrough, the remaining rows are short cases.
+
+#### Detailed output
+
+**Tool** `power_ticket_check`
+
+**Input**
+
+~~~json
+{"工作票编号":"DL-2026-0001","工作票种类":"电气第一种工作票","安全措施":"应停电、验电、装设接地线。"}
+~~~
+ 
+**Output**
+
+~~~json
+{
+  "id": "dsh-power-ticket-check.PT-006.104aebcf",
+  "ruleId": "PT-006",
+  "severity": "error",
+  "locator": {
+    "column": "安全措施"
+  },
+  "found": "安全措施文本中未出现 2 项：悬挂标示牌、装设遮栏",
+  "expected": "在电气设备上工作，应有停电、验电、装设接地线、悬挂标示牌和装设遮栏（围栏）等保证安全的技术措施",
+  "fix": "核对票面是否写全五项；本条只核对是否写到，不判断措施内容是否与现场相符"
+}
+~~~
+
+*Observed from `dsh-power-ticket-check/tests/fixtures/PT-006/PT-006-unsafe.json (cases.json expects 1×PT-006); executed parseMaterial+runCheck, checkedAt=2026-10-06T00:00:00.000Z`*
+
 | You ask | What it answers |
 |---|---|
 | Out of the box it passes every ticket I run through it — why? | Because `PT-001` reports itself in `skipped`, not as a pass. Its `requiredFields` list ships empty, so the rule cannot run; fill it with the columns your own form requires. Even when configured, `PT-001` checks that a column is filled, not that the value in it is correct, and it sits at `info`. |
@@ -196,6 +240,10 @@ pnpm run build       # tsdown -> lib/index.mjs + lib/index.d.mts
 node ../scripts/sync-shared.mjs dsh-power-ticket-check   # refresh src/shared from ../_shared
 ```
 
+## PerryLink DSH Plugin Family
+
+Full family index: [choose a checker by material](https://perrylink.github.io/zh/checkers/choose/) and [all plugins](https://github.com/PerryLink). This repository is one of them.
+
 ## License
 
 [Apache License 2.0](LICENSE) © 2026 dsh-power-ticket-check contributors.

package/lib/index.d.mts

@@ -1,12 +1,11 @@
 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 {
+export interface Config {
   /** Rule-pack path relative to the plugin package root. */
   rulesFile: string;
   /** Rule ids disabled for this deployment. */
@@ -18,13 +17,11 @@ interface Config {
   /** Tool timeout budget in milliseconds. */
   timeoutMs: number;
 }
-declare const Config: Schema<Config>;
-//#endregion
-//#region src/index.d.ts
-declare const name = "dsh-power-ticket-check";
-declare const inject: string[];
+export declare const Config: Schema<Config>;
+export declare const name = "dsh-power-ticket-check";
+export declare const inject: string[];
 /** Tool id exposed to the model, and the row id in `cordis.patch.yml`. */
-declare const TOOL_NAME = "power_ticket_check";
+export declare const TOOL_NAME = "power_ticket_check";
 /**
  * Locate a package-owned file such as the rule pack.
  *
@@ -36,7 +33,7 @@ declare const TOOL_NAME = "power_ticket_check";
  * @returns the resolved absolute path.
  * @throws Error naming every location tried, when the file is absent.
  */
-declare function resolvePackageFile(relative: string): string;
+export declare function resolvePackageFile(relative: string): string;
 /**
  * Register the checker tool.
  *
@@ -47,6 +44,4 @@ declare function resolvePackageFile(relative: string): string;
  * @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 };
+export declare function apply(ctx: Context, config: Config): () => void;

package/lib/index.mjs

@@ -3,7 +3,7 @@ import { existsSync } from "node:fs";
 import { dirname, isAbsolute, resolve } from "node:path";
 import { defineTool } from "@deepseek-ai/dsh-tools";
 import Schema from "@deepseek-ai/schemastery";
-//#region src/config.ts
+// src/config.ts
 const Config = Schema.object({
 	rulesFile: Schema.string().default("rules/power-ticket-check.yaml").description("规则库文件路径（相对插件包根目录）。替换该文件即可切换规则集版本。"),
 	disabledRules: Schema.array(Schema.string()).default([]).description("要停用的规则 id 列表；停用的规则会出现在报告的 skipped 中。"),
@@ -11,8 +11,7 @@ const Config = Schema.object({
 	skipNotes: Schema.string().default("").description("附加到每条 skipped 说明后的备注，例如标注本机构实施细则。"),
 	timeoutMs: Schema.number().default(12e4).description("工具协作式超时预算（毫秒）。")
 });
-//#endregion
-//#region src/shared/rules.ts
+// src/shared/rules.ts
 /**
 * Compose the one-line `basis` string rendered into reports.
 * @param basis - the rule's normative basis.
@@ -42,8 +41,7 @@ function disabledAsSkipped(ruleset, disabledIds, reason) {
 		reason
 	}));
 }
-//#endregion
-//#region src/shared/yaml.ts
+// src/shared/yaml.ts
 /**
 * Minimal, dependency-free YAML reader for rule packs and check material.
 *
@@ -396,6 +394,10 @@ var Reader = class {
 			if (!isSequenceItem(line.text)) break;
 			this.index += 1;
 			const rest = line.text === "-" ? "" : line.text.slice(2).trim();
+			if (rest.startsWith("{") || rest.startsWith("[")) {
+				items.push(parseScalar(rest, line.num));
+				continue;
+			}
 			if ((rest === "" ? -1 : findKeySeparator(rest)) >= 0) {
 				items.push(this.readMapping(indent + 2, {
 					text: rest,
@@ -475,8 +477,7 @@ function requireString(source, key, where) {
 	if (typeof value !== "string" || value.trim() === "") throw new YamlSubsetError(`${where}: missing required string field "${key}"`);
 	return value;
 }
-//#endregion
-//#region src/shared/ruleset.ts
+// src/shared/ruleset.ts
 /**
 * Rule-pack loading and validation.
 *
@@ -606,8 +607,7 @@ function paramStrings(rule, key, fallback) {
 	if (!Array.isArray(value) || value.some((entry) => typeof entry !== "string")) throw new YamlSubsetError(`rule ${rule.id}: params.${key} must be a list of strings`);
 	return value;
 }
-//#endregion
-//#region src/shared/report.ts
+// src/shared/report.ts
 /** Locator fields that participate in the stable issue id, in fixed order. */
 const LOCATOR_ID_KEYS = [
 	"file",
@@ -683,8 +683,7 @@ function sortValue(value) {
 	}
 	return target;
 }
-//#endregion
-//#region src/shared/datetime.ts
+// src/shared/datetime.ts
 const DATE_PATTERN = /^(\d{4})[-/.](\d{1,2})[-/.](\d{1,2})$/;
 const TIME_PATTERN = /^(\d{1,2}):(\d{2})(?::(\d{2}))?$/;
 function pad(value, width = 2) {
@@ -744,8 +743,7 @@ function dayNumber(date) {
 function instant$1(wall) {
 	return dayNumber(wall.date) * 1440 + wall.minutes;
 }
-//#endregion
-//#region src/check.ts
+// src/check.ts
 /**
 * Pure check core: `(input, ruleset, options) => Report`.
 *
@@ -1050,8 +1048,7 @@ function runCheck(input, ruleset, options) {
 		skipped
 	});
 }
-//#endregion
-//#region src/model.ts
+// src/model.ts
 /** Columns recognised as a named role, in priority order. */
 const ROLE_COLUMNS = [
 	"工作票签发人",
@@ -1062,8 +1059,7 @@ const ROLE_COLUMNS = [
 	"值班负责人",
 	"调度许可人"
 ];
-//#endregion
-//#region src/parse.ts
+// src/parse.ts
 /**
 * Reader for the power work ticket.
 *
@@ -1210,12 +1206,10 @@ function parseMaterial(source, target) {
 	if (input.roles.length === 0) warnings.push("材料中没有可识别的人员角色列，人员相关检查将无法执行");
 	return input;
 }
-//#endregion
-//#region src/shared/wording.ts
+// src/shared/wording.ts
 /** Footer appended to every rendered report. */
 const DISCLAIMER = "免责声明：本报告由程序按声明的规则集自动生成，仅列出与所引条款之间的字面差异，供人工复核线索使用；不构成对任何事实、行为或文件的定性意见，也不替代主管人员、评审专家或监管机构的判断。规则集的时效性与适用范围以引用文件的最新有效版本为准。";
-//#endregion
-//#region src/view.ts
+// src/view.ts
 /**
 * Model-facing projection of a {@link Report}.
 *
@@ -1295,8 +1289,7 @@ function buildView(report) {
 		reportJson: canonicalJson(report)
 	};
 }
-//#endregion
-//#region src/shared/memo.ts
+// src/shared/memo.ts
 /**
 * Memoized loading of package-owned rule packs.
 *
@@ -1319,8 +1312,7 @@ function loadRulesetFile(path) {
 	pending.catch(() => cache.delete(path));
 	return pending;
 }
-//#endregion
-//#region src/index.ts
+// src/index.ts
 const name = "dsh-power-ticket-check";
 const inject = ["tools"];
 /** Tool id exposed to the model, and the row id in `cordis.patch.yml`. */
@@ -1457,5 +1449,4 @@ function apply(ctx, config) {
 		}
 	}));
 }
-//#endregion
 export { Config, TOOL_NAME, apply, inject, name, resolvePackageFile };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-power-ticket-check",
-  "version": "0.2.8",
+  "version": "0.2.10",
   "description": "电力工作票要素齐备性与签发许可顺序核对（依据现行电力安全工作规程，仅提示差异，不作出定性结论）",
   "type": "module",
   "main": "lib/index.mjs",
@@ -78,16 +78,15 @@
     "@deepseek-ai/schemastery": "^3.18.2"
   },
   "devDependencies": {
-    "@deepseek-ai/cordis": "4.0.5-alpha.1",
-    "@deepseek-ai/dsh-package-manifest": "0.2.1-rc.2",
+    "@deepseek-ai/cordis": "4.0.5",
+    "@deepseek-ai/dsh-package-manifest": "0.2.1-rc.3",
     "@deepseek-ai/dsh-tools": "0.2.1-rc.2",
-    "@deepseek-ai/schemastery": "3.18.5-alpha.1",
+    "@deepseek-ai/schemastery": "3.18.5",
     "@types/node": "^22.20.1",
     "vitest": "^3.2.7",
-    "@deepseek-ai/dsh-working-directory": "0.2.1-rc.2"
-  },
-  "dependencies": {
-    "tsdown": "^0.22.14",
+    "@deepseek-ai/dsh-working-directory": "0.2.1-rc.2",
+    "tsdown": "^0.23.1",
     "typescript": "^5.9.3"
-  }
+  },
+  "dependencies": {}
 }