dsh-doublecheck 0.9.8 → 0.9.9

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.
Files changed (9) hide show
  1. package/CHANGELOG.md +17 -0
  2. package/README.es.md +5 -4
  3. package/README.hi.md +5 -4
  4. package/README.md +5 -4
  5. package/README.pt.md +5 -4
  6. package/README.zh.md +5 -4
  7. package/lib/guard/index.d.ts +8 -0
  8. package/lib/guard/index.js +39 -20
  9. package/package.json +2 -1
package/CHANGELOG.md CHANGED
@@ -2,6 +2,23 @@
2
2
 
3
3
  All notable changes to dsh-doublecheck are recorded here, newest first.
4
4
 
5
+ ## [0.9.9] - 2026-09-09
6
+
7
+ ### Fixed
8
+
9
+ - Register the gate settings namespace as **`doublecheck-gate`**. The previous `doublecheck.gate` name violated the host's `NAMESPACE_PATTERN` (`/^[a-z][a-z0-9-]*$/`), so `ctx.settings.register` threw a `TypeError` (the pattern has rejected dots since the settings seam landed), the guard swallowed it into a warn, and the namespace never reached `ctx.settings.describe()` — no settings surface could see or edit the checklist. The namespace is now typed against the host `SettingsProvider`, so a dotted name also fails at compile time.
10
+ - Wire the registered namespace into the runtime: `apply` now reads the resolved `SettingsScope` once at load, so the user section overrides the composition `gate.*` values for the `/gate` panel and the gate-red notice (`applies: restart`). Writes pass through `validate: validateGateConfig`, so a duplicate checklist id is refused at update time and the last good value stays in place.
11
+ - Remove the `expose: true` registration option: the host has no such option and silently ignored it.
12
+
13
+ ### Changed
14
+
15
+ - Add `@deepseek-ai/dsh-settings` as a devDependency (type-only import) for the real settings contract in tests and the compile-time namespace guard; no runtime dependency change.
16
+ - Add `tests/settings.spec.ts`: the host rejects a dotted namespace with `/must match/`; `doublecheck-gate` is registered with `applies: 'restart'`, the composition base, and appears in `ctx.settings.describe()`; the row mounts without the "namespace skipped" warning; and a user section reaches the `/gate config` output. A pre-existing `doublecheck.gate` section (if any) was never read by any release and is now simply ignored.
17
+
18
+ ### Docs
19
+
20
+ - Five-language READMEs and `AGENTS.md`: the `doublecheck-gate` namespace name, the `ctx.settings.describe()` visibility scope (the package ships no client card, so the shipped Web GUI plugin page does not list it), and the user-section-overrides-composition behavior.
21
+
5
22
  ## [0.9.8] - 2026-09-09
6
23
 
7
24
  ### Fixed
package/README.es.md CHANGED
@@ -9,6 +9,7 @@
9
9
 
10
10
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
11
11
  [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
12
+ [![dsh-doctor](https://raw.githubusercontent.com/PerryLink/dsh-plugin-doctor/main/badges/PerryLink__dsh-doublecheck.svg)](https://github.com/PerryLink/dsh-plugin-doctor#verified-徽章)
12
13
  [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
13
14
  [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-doublecheck/ci.yml?branch=main&label=CI)](https://github.com/PerryLink/dsh-doublecheck/actions)
14
15
  [![Version](https://img.shields.io/github/v/tag/PerryLink/dsh-doublecheck?label=version)](https://github.com/PerryLink/dsh-doublecheck/releases)
@@ -35,7 +36,7 @@
35
36
  `dsh-doublecheck` instala dos filas de plugin que leen y aplican desde el mismo registro de sesión durable:
36
37
 
37
38
  1. **`doublecheck-grill`** — el horno de requisitos: la skill empaquetada `grill-requirements` más las herramientas orientadas al modelo `doublecheck_skills`, `doublecheck_spec` y `doublecheck_report`, y el flujo de verificación por dimensión.
38
- 2. **`doublecheck-guard`** — el guard de disciplina: la puerta grill, las puertas de evidencia rojo/verde, la revisión adversarial, los comandos `/doublecheck` y `/gate`, el espacio de ajustes `doublecheck.gate` y la puerta de entrega de cuatro fases.
39
+ 2. **`doublecheck-guard`** — el guard de disciplina: la puerta grill, las puertas de evidencia rojo/verde, la revisión adversarial, los comandos `/doublecheck` y `/gate`, el espacio de ajustes `doublecheck-gate` y la puerta de entrega de cuatro fases.
39
40
 
40
41
  Juntos imponen el **bucle de disciplina** — *grill → design → red → green → review → verify*:
41
42
 
@@ -137,7 +138,7 @@ La mala configuración falla en voz alta al cargar: regex inválidas, listas de
137
138
  | `/doublecheck status\|report\|on\|off` | comando | Interruptor, módulos, intensidad, hechos de etapa, informe plegado y la sobrescritura durable on/off. |
138
139
  | `/gate status\|run\|config` | comando | Progreso de la lista en vivo, el informe entregable/rehacer asentado y la configuración efectiva. |
139
140
  | `grill-requirements`, `red-green-tdd`, `delivery-review`, `delivery-proof` | skill | Skills de disciplina empaquetadas que cubren las seis etapas del bucle. |
140
- | `doublecheck.gate` | espacio de ajustes | La lista enchufable, expuesta a UIs con ajustes (`expose: true`, `applies: restart`). |
141
+ | `doublecheck-gate` | espacio de ajustes | La lista enchufable: la sección del usuario sobrescribe los valores `gate.*` de la composición y se lee una vez al cargar (`applies: restart`), visible vía `ctx.settings.describe()`. |
141
142
  | `strict.patch.yml` | capa superpuesta | Cada puerta activa con intensidad `block` más el requisito de cobertura, en una capa de parche. |
142
143
  | `dsh-doublecheck/invariant` | fila acompañante | Informa contradicciones de ruta de escritura propias del paquete a través del registro `invariants` del host. |
143
144
 
@@ -225,8 +226,8 @@ El CLI solo serializa el `GateState` ya asentado — nunca vuelve a ejecutar la
225
226
 
226
227
  - **Escrituras durables.** `/doublecheck on\|off` → `doublecheck/state` y `/gate run` → `doublecheck/gate` necesitan la superficie de append `ignorable` del host (post-rc.6 hasta `0.1.1-rc.2`). En hosts sin esa superficie (rc.6/rc.8 y `0.1.2-alpha.1`, que eliminó el sobre — `0.1.2-rc.1` restaura el campo solo para compatibilidad de lectura de logs almacenados y aún no puede estamparlo), las escrituras se omiten y el interruptor queda en proceso.
227
228
  0.1.2-rc.1 (adaptado el 2026-09-02): el sobre de sesión conserva su campo ignorable solo para compatibilidad de lectura de logs almacenados - Session.append aún no puede estamparlo, por lo que el comportamiento de la puerta no cambia.
228
- 0.1.5-alpha.1 (adaptado el 2026-09-09): el formato de sesión V3 renombra el evento durable de subenvío `tool/code-dispatch` a `tool/ptc-dispatch` (carga útil sin cambios; ambas etiquetas se pliegan de forma idéntica). Session.append sigue sin canal `ignorable`, así que las escrituras durables se omiten y el interruptor permanece en proceso - comportamiento sin cambios. El espacio de ajustes `doublecheck.gate` sigue siendo una interfaz débil (véase Limitaciones conocidas).
229
- - **Interfaces opcionales.** El espacio de ajustes `doublecheck.gate` se registra solo cuando el servicio de ajustes está montado; la línea de modo plan de `/gate status` lee el `ctx.planMode` opcional (muestra `unknown` sin él); la revisión adversarial necesita `ctx.subagents`; la verificación necesita `workflowEngine`.
229
+ 0.1.5-alpha.1 (adaptado el 2026-09-09): el formato de sesión V3 renombra el evento durable de subenvío `tool/code-dispatch` a `tool/ptc-dispatch` (carga útil sin cambios; ambas etiquetas se pliegan de forma idéntica). Session.append sigue sin canal `ignorable`, así que las escrituras durables se omiten y el interruptor permanece en proceso - comportamiento sin cambios. El espacio de ajustes `doublecheck-gate` es una interfaz débil, resuelta al cargar (véase Limitaciones conocidas).
230
+ - **Interfaces opcionales.** El espacio de ajustes `doublecheck-gate` se registra solo cuando el servicio de ajustes está montado; entonces aparece en `ctx.settings.describe()` y su sección del usuario sobrescribe los valores `gate.*` de la composición en la siguiente carga (el paquete no incluye tarjeta de cliente, así que la página de plugins de la Web GUI no lo lista); la línea de modo plan de `/gate status` lee el `ctx.planMode` opcional (muestra `unknown` sin él); la revisión adversarial necesita `ctx.subagents`; la verificación necesita `workflowEngine`.
230
231
  - **Degradación local.** `gate.review.engine: auto` degrada al revisor local cuando dsh-auto-review está ausente o no tiene registros de veredicto en esta sesión — el informe nombra la razón en lugar de inventar un veredicto.
231
232
  - **La evidencia dsh-eval se basa en archivos.** El motor de evaluación de dsh-auto-review (`dsh-eval`) escribe sus resultados de regresión de prompt / estrés / equidad en un archivo de informe del espacio de trabajo, no en el registro de sesión. `gate.tests.evalReports.enabled` pliega ese archivo (desactivado por defecto; salta cuando está ausente) y los recuentos pliegados viajan en el registro duradero `doublecheck/gate` para que una ejecución asentada siga siendo reproducible.
232
233
 
package/README.hi.md CHANGED
@@ -9,6 +9,7 @@
9
9
 
10
10
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
11
11
  [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
12
+ [![dsh-doctor](https://raw.githubusercontent.com/PerryLink/dsh-plugin-doctor/main/badges/PerryLink__dsh-doublecheck.svg)](https://github.com/PerryLink/dsh-plugin-doctor#verified-徽章)
12
13
  [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
13
14
  [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-doublecheck/ci.yml?branch=main&label=CI)](https://github.com/PerryLink/dsh-doublecheck/actions)
14
15
  [![Version](https://img.shields.io/github/v/tag/PerryLink/dsh-doublecheck?label=version)](https://github.com/PerryLink/dsh-doublecheck/releases)
@@ -35,7 +36,7 @@
35
36
  `dsh-doublecheck` दो plugin पंक्तियाँ स्थापित करता है जो एक ही टिकाऊ सत्र लॉग से पढ़ती और लागू करती हैं:
36
37
 
37
38
  1. **`doublecheck-grill`** — आवश्यकताओं की भट्टी: बंडल की गई `grill-requirements` skill, साथ ही मॉडल-मुखी `doublecheck_skills`, `doublecheck_spec` और `doublecheck_report` उपकरण, तथा प्रति-आयाम सत्यापन वर्कफ़्लो।
38
- 2. **`doublecheck-guard`** — अनुशासन guard: grill द्वार, लाल/हरा साक्ष्य द्वार, प्रतिकूल समीक्षा, `/doublecheck` और `/gate` कमांड, `doublecheck.gate` सेटिंग्स नेमस्पेस, तथा चार-चरण डिलीवरी द्वार।
39
+ 2. **`doublecheck-guard`** — अनुशासन guard: grill द्वार, लाल/हरा साक्ष्य द्वार, प्रतिकूल समीक्षा, `/doublecheck` और `/gate` कमांड, `doublecheck-gate` सेटिंग्स नेमस्पेस, तथा चार-चरण डिलीवरी द्वार।
39
40
 
40
41
  दोनों मिलकर **अनुशासन लूप** लागू करते हैं — *grill → design → red → green → review → verify*:
41
42
 
@@ -137,7 +138,7 @@ dsh --profile web --dump-config | grep -E -A3 'id: doublecheck-(grill|guard)'
137
138
  | `/doublecheck status\|report\|on\|off` | कमांड | स्विच, मॉड्यूल, तीव्रता, चरण तथ्य, मुड़ी हुई रिपोर्ट, और टिकाऊ on/off ओवरराइड। |
138
139
  | `/gate status\|run\|config` | कमांड | लाइव सूची प्रगति, तय deliverable/rework रिपोर्ट, और प्रभावी कॉन्फ़िग। |
139
140
  | `grill-requirements`, `red-green-tdd`, `delivery-review`, `delivery-proof` | skill | सभी छह लूप चरणों को कवर करने वाली बंडल अनुशासन skills। |
140
- | `doublecheck.gate` | सेटिंग्स नेमस्पेस | प्लग करने योग्य सूची, सेटिंग्स-सक्षम UI को उजागर (`expose: true`, `applies: restart`)। |
141
+ | `doublecheck-gate` | सेटिंग्स नेमस्पेस | प्लग करने योग्य सूची: उपयोगकर्ता अनुभाग composition के `gate.*` मानों को ओवरराइड करता है और लोड पर एक बार पढ़ा जाता है (`applies: restart`), `ctx.settings.describe()` से दृश्य। |
141
142
  | `strict.patch.yml` | ओवरले | `block` तीव्रता पर हर द्वार चालू और कवरेज आवश्यकता, एक पैच परत में। |
142
143
  | `dsh-doublecheck/invariant` | सहयोगी पंक्ति | host `invariants` रजिस्ट्री के माध्यम से पैकेज-स्वामित्व वाले लेखन-पथ विरोधाभासों की रिपोर्ट करता है। |
143
144
 
@@ -225,8 +226,8 @@ CLI केवल पहले से स्थापित `GateState` को
225
226
 
226
227
  - **टिकाऊ लेखन।** `/doublecheck on\|off` → `doublecheck/state` और `/gate run` → `doublecheck/gate` को host की `ignorable` append सतह (rc.6 के बाद से `0.1.1-rc.2` तक) चाहिए। उस सतह के बिना hosts (rc.6/rc.8 और `0.1.2-alpha.1`, जिसने envelope हटा दिया — `0.1.2-rc.1` केवल संग्रहीत-लॉग पठन संगतता के लिए फ़ील्ड बहाल करता है और अभी भी स्टैम्प नहीं कर सकता) पर लेखन छोड़ दिया जाता है और स्विच प्रक्रिया-स्थानीय रहता है।
227
228
  0.1.2-rc.1 (2026-09-02 को अनुकूलित): सत्र लिफ़ाफ़ा अपना ignorable फ़ील्ड केवल संग्रहीत-लॉग पठन संगतता के लिए रखता है - Session.append अभी भी इसे स्टैम्प नहीं कर सकता, इसलिए गेट व्यवहार अपरिवर्तित है।
228
- 0.1.5-alpha.1 (2026-09-09 को अनुकूलित): सत्र प्रारूप V3 टिकाऊ उप-प्रेषण इवेंट `tool/code-dispatch` का नाम `tool/ptc-dispatch` करता है (पेलोड अपरिवर्तित; दोनों लेबल समान रूप से फ़ोल्ड होते हैं)। Session.append में अभी भी `ignorable` चैनल नहीं है, इसलिए टिकाऊ लेखन छोड़े जाते हैं और स्विच प्रक्रिया-स्थानीय रहता है - व्यवहार अपरिवर्तित। `doublecheck.gate` सेटिंग्स नेमस्पेस अभी भी एक कमज़ोर इंटरफ़ेस है (ज्ञात सीमाएँ देखें)।
229
- - **वैकल्पिक इंटरफ़ेस।** `doublecheck.gate` सेटिंग्स नेमस्पेस केवल तब पंजीकृत होता है जब सेटिंग्स सेवा माउंट हो; `/gate status` की प्लान-मोड पंक्ति वैकल्पिक `ctx.planMode` पढ़ती है (इसके बिना `unknown` दिखाती है); प्रतिकूल समीक्षा को `ctx.subagents` चाहिए; सत्यापन को `workflowEngine` चाहिए।
229
+ 0.1.5-alpha.1 (2026-09-09 को अनुकूलित): सत्र प्रारूप V3 टिकाऊ उप-प्रेषण इवेंट `tool/code-dispatch` का नाम `tool/ptc-dispatch` करता है (पेलोड अपरिवर्तित; दोनों लेबल समान रूप से फ़ोल्ड होते हैं)। Session.append में अभी भी `ignorable` चैनल नहीं है, इसलिए टिकाऊ लेखन छोड़े जाते हैं और स्विच प्रक्रिया-स्थानीय रहता है - व्यवहार अपरिवर्तित। `doublecheck-gate` सेटिंग्स नेमस्पेस एक कमज़ोर इंटरफ़ेस है, जो लोड पर हल होता है (ज्ञात सीमाएँ देखें)।
230
+ - **वैकल्पिक इंटरफ़ेस।** `doublecheck-gate` सेटिंग्स नेमस्पेस केवल तब पंजीकृत होता है जब सेटिंग्स सेवा माउंट हो; तब यह `ctx.settings.describe()` में दिखता है और इसका उपयोगकर्ता अनुभाग अगले लोड पर composition के `gate.*` मानों को ओवरराइड करता है (पैकेज में कोई client कार्ड नहीं है, इसलिए Web GUI का plugin पृष्ठ इसे सूचीबद्ध नहीं करता); `/gate status` की प्लान-मोड पंक्ति वैकल्पिक `ctx.planMode` पढ़ती है (इसके बिना `unknown` दिखाती है); प्रतिकूल समीक्षा को `ctx.subagents` चाहिए; सत्यापन को `workflowEngine` चाहिए।
230
231
  - **स्थानीय अवनति।** जब dsh-auto-review अनुपस्थित हो या इस सत्र में उसके कोई निर्णय रिकॉर्ड न हों, तो `gate.review.engine: auto` स्थानीय समीक्षक पर घट जाता है — रिपोर्ट निर्णय गढ़ने के बजाय कारण बताती है।
231
232
  - **dsh-eval साक्ष्य फ़ाइल-आधारित है।** dsh-auto-review का मूल्यांकन इंजन (`dsh-eval`) अपने prompt-regression / stress / fairness परिणाम कार्यक्षेत्र रिपोर्ट फ़ाइल में लिखता है, सत्र लॉग में नहीं। `gate.tests.evalReports.enabled` उस फ़ाइल को मोड़ता है (डिफ़ॉल्ट रूप से बंद; अनुपस्थित होने पर छोड़ देता है) और मोड़ी गई गणनाएँ टिकाऊ `doublecheck/gate` रिकॉर्ड पर चलती हैं, ताकि तयशुदा रन फिर भी रीप्ले हो सके।
232
233
 
package/README.md CHANGED
@@ -10,6 +10,7 @@
10
10
 
11
11
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
12
12
  [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
13
+ [![dsh-doctor](https://raw.githubusercontent.com/PerryLink/dsh-plugin-doctor/main/badges/PerryLink__dsh-doublecheck.svg)](https://github.com/PerryLink/dsh-plugin-doctor#verified-徽章)
13
14
  [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
14
15
  [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-doublecheck/ci.yml?branch=main&label=CI)](https://github.com/PerryLink/dsh-doublecheck/actions)
15
16
  [![Version](https://img.shields.io/github/v/tag/PerryLink/dsh-doublecheck?label=version)](https://github.com/PerryLink/dsh-doublecheck/releases)
@@ -36,7 +37,7 @@
36
37
  `dsh-doublecheck` installs two plugin rows that read and enforce from the same durable session log:
37
38
 
38
39
  1. **`doublecheck-grill`** — the requirements furnace: the bundled `grill-requirements` skill plus the model-facing `doublecheck_skills`, `doublecheck_spec`, and `doublecheck_report` tools and the per-dimension verification workflow.
39
- 2. **`doublecheck-guard`** — the discipline guard: the grill gate, the red/green evidence gates, the adversary review, the `/doublecheck` and `/gate` commands, the `doublecheck.gate` settings namespace, and the four-phase delivery gate.
40
+ 2. **`doublecheck-guard`** — the discipline guard: the grill gate, the red/green evidence gates, the adversary review, the `/doublecheck` and `/gate` commands, the `doublecheck-gate` settings namespace, and the four-phase delivery gate.
40
41
 
41
42
  Together they enforce the **discipline loop** — *grill → design → red → green → review → verify*:
42
43
 
@@ -138,7 +139,7 @@ Misconfiguration fails loud at load: invalid regexes, empty or duplicated name l
138
139
  | `/doublecheck status\|report\|on\|off` | command | Switch, modules, intensity, stage facts, folded report, and the durable on/off override. |
139
140
  | `/gate status\|run\|config` | command | Live checklist progress, the settled deliverable/rework report, and the effective config. |
140
141
  | `grill-requirements`, `red-green-tdd`, `delivery-review`, `delivery-proof` | skill | Bundled discipline skills covering all six loop stages. |
141
- | `doublecheck.gate` | settings namespace | The pluggable checklist, exposed to settings-capable UIs (`expose: true`, `applies: restart`). |
142
+ | `doublecheck-gate` | settings namespace | The pluggable checklist: the user section overrides the composition `gate.*` values and is read once at load (`applies: restart`), visible through `ctx.settings.describe()`. |
142
143
  | `strict.patch.yml` | overlay | Every gate on at `block` intensity plus the coverage requirement, in one patch layer. |
143
144
  | `dsh-doublecheck/invariant` | companion row | Reports package-owned write-path contradictions through the host `invariants` registry. |
144
145
 
@@ -226,8 +227,8 @@ The CLI only serializes the already-settled `GateState` — it never re-runs the
226
227
 
227
228
  - **Durable writes.** `/doublecheck on\|off` → `doublecheck/state` and `/gate run` → `doublecheck/gate` ride the host's `ignorable` append surface (post-rc.6 through `0.1.1-rc.2`). On hosts without that surface (rc.6/rc.8, and `0.1.2-alpha.1`, which removed the envelope — `0.1.2-rc.1` restores the field for stored-log read compatibility only and still cannot stamp it), the writes are skipped and the switch stays process-local.
228
229
  0.1.2-rc.1 (adapted 2026-09-02): the session envelope keeps its ignorable field for stored-log read compatibility only - Session.append still cannot stamp it, so audit-gate behavior is unchanged.
229
- 0.1.5-alpha.1 (adapted 2026-09-09): session format V3 renames the durable sub-dispatch event `tool/code-dispatch` to `tool/ptc-dispatch` (payload unchanged; both labels fold identically). Session.append still exposes no `ignorable` channel, so durable writes stay skipped and the switch stays process-local - behavior unchanged. The `doublecheck.gate` settings namespace remains a weak seam (see Known limitations).
230
- - **Optional seams.** The `doublecheck.gate` settings namespace registers only when the settings service is mounted; the `/gate status` plan-mode line reads the optional `ctx.planMode` (shows `unknown` without it); the adversary review needs `ctx.subagents`; verification needs `workflowEngine`.
230
+ 0.1.5-alpha.1 (adapted 2026-09-09): session format V3 renames the durable sub-dispatch event `tool/code-dispatch` to `tool/ptc-dispatch` (payload unchanged; both labels fold identically). Session.append still exposes no `ignorable` channel, so durable writes stay skipped and the switch stays process-local - behavior unchanged. The `doublecheck-gate` settings namespace is a weak seam resolved at load (see Known limitations).
231
+ - **Optional seams.** The `doublecheck-gate` settings namespace registers only when the settings service is mounted; it then appears in `ctx.settings.describe()`, and its user section overrides the composition `gate.*` values on the next load. The package ships no client card, so the shipped Web GUI plugin page does not list it. The `/gate status` plan-mode line reads the optional `ctx.planMode` (shows `unknown` without it); the adversary review needs `ctx.subagents`; verification needs `workflowEngine`.
231
232
  - **Local degrade.** `gate.review.engine: auto` degrades to the local reviewer when dsh-auto-review is absent or has no verdict records this session — the report names the reason instead of inventing a verdict.
232
233
  - **dsh-eval evidence is file-based.** The dsh-auto-review eval engine (`dsh-eval`) writes its prompt-regression / stress / fairness results to a workspace report file, not the session log. `gate.tests.evalReports.enabled` folds that file (off by default; skips when absent) and the folded counts ride the durable `doublecheck/gate` record so a settled run still replays.
233
234
 
package/README.pt.md CHANGED
@@ -9,6 +9,7 @@
9
9
 
10
10
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
11
11
  [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
12
+ [![dsh-doctor](https://raw.githubusercontent.com/PerryLink/dsh-plugin-doctor/main/badges/PerryLink__dsh-doublecheck.svg)](https://github.com/PerryLink/dsh-plugin-doctor#verified-徽章)
12
13
  [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
13
14
  [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-doublecheck/ci.yml?branch=main&label=CI)](https://github.com/PerryLink/dsh-doublecheck/actions)
14
15
  [![Version](https://img.shields.io/github/v/tag/PerryLink/dsh-doublecheck?label=version)](https://github.com/PerryLink/dsh-doublecheck/releases)
@@ -35,7 +36,7 @@
35
36
  `dsh-doublecheck` instala duas linhas de plugin que leem e aplicam a partir do mesmo registro de sessão durável:
36
37
 
37
38
  1. **`doublecheck-grill`** — o forno de requisitos: a skill empacotada `grill-requirements` mais as ferramentas voltadas ao modelo `doublecheck_skills`, `doublecheck_spec` e `doublecheck_report`, e o fluxo de verificação por dimensão.
38
- 2. **`doublecheck-guard`** — o guard de disciplina: o portão grill, os portões de evidência vermelho/verde, a revisão adversarial, os comandos `/doublecheck` e `/gate`, o namespace de configurações `doublecheck.gate` e o portão de entrega de quatro fases.
39
+ 2. **`doublecheck-guard`** — o guard de disciplina: o portão grill, os portões de evidência vermelho/verde, a revisão adversarial, os comandos `/doublecheck` e `/gate`, o namespace de configurações `doublecheck-gate` e o portão de entrega de quatro fases.
39
40
 
40
41
  Juntos impõem o **ciclo de disciplina** — *grill → design → red → green → review → verify*:
41
42
 
@@ -137,7 +138,7 @@ A má configuração falha em voz alta ao carregar: regex inválidas, listas de
137
138
  | `/doublecheck status\|report\|on\|off` | comando | Interruptor, módulos, intensidade, fatos de etapa, relatório dobrado e a sobrescrita durável on/off. |
138
139
  | `/gate status\|run\|config` | comando | Progresso da lista em tempo real, o relatório entregável/retrabalho assentado e a configuração efetiva. |
139
140
  | `grill-requirements`, `red-green-tdd`, `delivery-review`, `delivery-proof` | skill | Skills de disciplina empacotadas que cobrem as seis etapas do ciclo. |
140
- | `doublecheck.gate` | namespace de configurações | A lista plugável, exposta a UIs com configurações (`expose: true`, `applies: restart`). |
141
+ | `doublecheck-gate` | namespace de configurações | A lista plugável: a seção do usuário substitui os valores `gate.*` da composição e é lida uma vez ao carregar (`applies: restart`), visível via `ctx.settings.describe()`. |
141
142
  | `strict.patch.yml` | camada de sobreposição | Cada portão ativo com intensidade `block` mais o requisito de cobertura, em uma camada de patch. |
142
143
  | `dsh-doublecheck/invariant` | linha acompanhante | Reporta contradições de caminho de escrita próprias do pacote por meio do registro `invariants` do host. |
143
144
 
@@ -225,8 +226,8 @@ O CLI apenas serializa o `GateState` já assentado — nunca reexecuta a porta d
225
226
 
226
227
  - **Escritas duráveis.** `/doublecheck on\|off` → `doublecheck/state` e `/gate run` → `doublecheck/gate` precisam da superfície de append `ignorable` do host (pós-rc.6 até `0.1.1-rc.2`). Em hosts sem essa superfície (rc.6/rc.8 e `0.1.2-alpha.1`, que removeu o envelope — `0.1.2-rc.1` restaura o campo apenas para compatibilidade de leitura de logs armazenados e ainda não consegue estampá-lo), as escritas são omitidas e o interruptor permanece em processo.
227
228
  0.1.2-rc.1 (adaptado em 2026-09-02): o envelope de sessão mantém seu campo ignorable apenas para compatibilidade de leitura de logs armazenados - o Session.append ainda não consegue estampá-lo, então o comportamento da porta não muda.
228
- 0.1.5-alpha.1 (adaptado em 2026-09-09): o formato de sessão V3 renomeia o evento durável de subenvio `tool/code-dispatch` para `tool/ptc-dispatch` (carga útil inalterada; os dois rótulos são dobrados de forma idêntica). O Session.append continua sem canal `ignorable`, então as escritas duráveis são omitidas e o interruptor permanece em processo - comportamento inalterado. O namespace de configurações `doublecheck.gate` continua sendo uma interface fraca (ver Limitações conhecidas).
229
- - **Interfaces opcionais.** O namespace de configurações `doublecheck.gate` é registrado apenas quando o serviço de configurações está montado; a linha de modo plano de `/gate status` lê o `ctx.planMode` opcional (mostra `unknown` sem ele); a revisão adversarial precisa de `ctx.subagents`; a verificação precisa de `workflowEngine`.
229
+ 0.1.5-alpha.1 (adaptado em 2026-09-09): o formato de sessão V3 renomeia o evento durável de subenvio `tool/code-dispatch` para `tool/ptc-dispatch` (carga útil inalterada; os dois rótulos são dobrados de forma idêntica). O Session.append continua sem canal `ignorable`, então as escritas duráveis são omitidas e o interruptor permanece em processo - comportamento inalterado. O namespace de configurações `doublecheck-gate` é uma interface fraca, resolvida ao carregar (ver Limitações conhecidas).
230
+ - **Interfaces opcionais.** O namespace de configurações `doublecheck-gate` é registrado apenas quando o serviço de configurações está montado; então aparece em `ctx.settings.describe()` e sua seção do usuário substitui os valores `gate.*` da composição no próximo carregamento (o pacote não inclui cartão de cliente, então a página de plugins da Web GUI não o lista); a linha de modo plano de `/gate status` lê o `ctx.planMode` opcional (mostra `unknown` sem ele); a revisão adversarial precisa de `ctx.subagents`; a verificação precisa de `workflowEngine`.
230
231
  - **Degradação local.** `gate.review.engine: auto` degrada para o revisor local quando o dsh-auto-review está ausente ou não tem registros de veredicto nesta sessão — o relatório nomeia a razão em vez de inventar um veredicto.
231
232
  - **A evidência dsh-eval é baseada em arquivos.** O motor de avaliação do dsh-auto-review (`dsh-eval`) grava seus resultados de regressão de prompt / estresse / equidade em um arquivo de relatório do espaço de trabalho, não no registro de sessão. `gate.tests.evalReports.enabled` dobra esse arquivo (desativado por padrão; pula quando ausente) e as contagens dobradas viajam no registro durável `doublecheck/gate` para que uma execução assentada ainda seja reproduzível.
232
233
 
package/README.zh.md CHANGED
@@ -9,6 +9,7 @@
9
9
 
10
10
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
11
11
  [![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
12
+ [![dsh-doctor](https://raw.githubusercontent.com/PerryLink/dsh-plugin-doctor/main/badges/PerryLink__dsh-doublecheck.svg)](https://github.com/PerryLink/dsh-plugin-doctor#verified-徽章)
12
13
  [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
13
14
  [![CI](https://img.shields.io/github/actions/workflow/status/PerryLink/dsh-doublecheck/ci.yml?branch=main&label=CI)](https://github.com/PerryLink/dsh-doublecheck/actions)
14
15
  [![Version](https://img.shields.io/github/v/tag/PerryLink/dsh-doublecheck?label=version)](https://github.com/PerryLink/dsh-doublecheck/releases)
@@ -35,7 +36,7 @@
35
36
  `dsh-doublecheck` 安装两个插件行，它们读取并执行同一份持久会话日志：
36
37
 
37
38
  1. **`doublecheck-grill`** —— 需求熔炉：内置的 `grill-requirements` 技能，加上面向模型的 `doublecheck_skills`、`doublecheck_spec`、`doublecheck_report` 工具，以及按维度执行的验证工作流。
38
- 2. **`doublecheck-guard`** —— 纪律守卫：grill 门禁、红/绿证据门禁、对抗式评审、`/doublecheck` 与 `/gate` 命令、`doublecheck.gate` 设置命名空间，以及四阶段交付门禁。
39
+ 2. **`doublecheck-guard`** —— 纪律守卫：grill 门禁、红/绿证据门禁、对抗式评审、`/doublecheck` 与 `/gate` 命令、`doublecheck-gate` 设置命名空间，以及四阶段交付门禁。
39
40
 
40
41
  两者共同执行**纪律闭环** —— *grill → design → red → green → review → verify*：
41
42
 
@@ -137,7 +138,7 @@ dsh --profile web --dump-config | grep -E -A3 'id: doublecheck-(grill|guard)'
137
138
  | `/doublecheck status\|report\|on\|off` | 命令 | 开关、模块、强度、阶段事实、折叠报告，以及持久的开/关覆盖。 |
138
139
  | `/gate status\|run\|config` | 命令 | 实时清单进度、已确定的可交付/返工报告，以及生效配置。 |
139
140
  | `grill-requirements`、`red-green-tdd`、`delivery-review`、`delivery-proof` | 技能 | 覆盖全部六个闭环阶段的内置纪律技能。 |
140
- | `doublecheck.gate` | 设置命名空间 | 可插拔清单，暴露给支持设置的 UI（`expose: true`、`applies: restart`）。 |
141
+ | `doublecheck-gate` | 设置命名空间 | 可插拔清单：用户段覆盖 composition 的 `gate.*` 值，在加载时读取一次（`applies: restart`），经 `ctx.settings.describe()` 可见。 |
141
142
  | `strict.patch.yml` | 覆盖层 | 一个补丁层内以 `block` 强度开启每个门禁并启用覆盖率要求。 |
142
143
  | `dsh-doublecheck/invariant` | 伴生行 | 通过宿主 `invariants` 注册表报告包自有写路径矛盾。 |
143
144
 
@@ -225,8 +226,8 @@ CLI 只序列化已定的 `GateState` —— 它从不重新运行四阶段门
225
226
 
226
227
  - **持久写入。** `/doublecheck on\|off` → `doublecheck/state` 与 `/gate run` → `doublecheck/gate` 需要宿主的 `ignorable` 追加接口（rc.6 之后至 `0.1.1-rc.2`）。在无此接口的宿主上（rc.6/rc.8，以及移除该信封的 `0.1.2-alpha.1`——`0.1.2-rc.1` 仅恢复存量日志读取兼容字段、仍无法盖章），写入被跳过、开关保持进程内状态。
227
228
  0.1.2-rc.1（2026-09-02 已适配）：会话信封保留 ignorable 字段但仅用于存量日志读取兼容——Session.append 仍无法盖章，门控行为不变。
228
- 0.1.5-alpha.1（2026-09-09 已适配）：会话格式 V3 把持久子调用事件 `tool/code-dispatch` 改名为 `tool/ptc-dispatch`（载荷不变；两个标签折叠结果一致）。Session.append 仍无 `ignorable` 写入通道，写入继续跳过、开关保持进程内——行为不变。`doublecheck.gate` 设置命名空间仍是弱接口（见「已知限制」）。
229
- - **可选接口。** `doublecheck.gate` 设置命名空间仅在挂载设置服务时注册；`/gate status` 的计划模式行读取可选的 `ctx.planMode`（没有则显示 `unknown`）；对抗式评审需要 `ctx.subagents`；验证需要 `workflowEngine`。
229
+ 0.1.5-alpha.1（2026-09-09 已适配）：会话格式 V3 把持久子调用事件 `tool/code-dispatch` 改名为 `tool/ptc-dispatch`（载荷不变；两个标签折叠结果一致）。Session.append 仍无 `ignorable` 写入通道，写入继续跳过、开关保持进程内——行为不变。`doublecheck-gate` 设置命名空间是弱接口，在加载时解析（见「已知限制」）。
230
+ - **可选接口。** `doublecheck-gate` 设置命名空间仅在挂载设置服务时注册；注册后出现在 `ctx.settings.describe()` 中，其用户段在下次加载时覆盖 composition 的 `gate.*` 值；本包不带 client 卡片，故 Web GUI 插件页不会单列它。`/gate status` 的计划模式行读取可选的 `ctx.planMode`（没有则显示 `unknown`）；对抗式评审需要 `ctx.subagents`；验证需要 `workflowEngine`。
230
231
  - **本地降级。** 当 dsh-auto-review 缺失或本会话没有裁决记录时，`gate.review.engine: auto` 会降级到本地评审者——报告会写明原因，而不是捏造裁决。
231
232
  - **dsh-eval 证据基于文件。** dsh-auto-review 评测引擎（`dsh-eval`）把其 prompt 回归 / 压测 / 公平性结果写入工作区报告文件，而非会话日志。`gate.tests.evalReports.enabled` 折叠该文件（默认关闭；缺失时跳过），折叠出的计数随持久 `doublecheck/gate` 记录保存，使已定的运行仍可重放。
232
233
 
package/lib/guard/index.d.ts CHANGED
@@ -36,6 +36,14 @@ import { type GateConfig } from './gate.js';
36
36
  import { type GateVerdict } from '../domain/gate.js';
37
37
  export declare const name = "doublecheck-guard";
38
38
  export declare const inject: string[];
39
+ /**
40
+ * The gate's settings namespace. Hyphenated on purpose: the host's
41
+ * `NAMESPACE_PATTERN` (`/^[a-z][a-z0-9-]*$/`) rejects a dot with a
42
+ * `TypeError`, and a rejected registration never reaches
43
+ * `ctx.settings.describe()`, so no settings surface can see it. v0.9.8 and
44
+ * earlier registered `doublecheck.gate`, which never took effect anywhere.
45
+ */
46
+ export declare const GATE_SETTINGS_NS = "doublecheck-gate";
39
47
  /**
40
48
  * Guard configuration. `intensity` is shared by all three gates; `modules`
41
49
  * selects them. The `adversary` module (v0.3) dispatches a forked critic
package/lib/guard/index.js CHANGED
@@ -42,6 +42,14 @@ import { installInvariant, PACKAGE_NAME } from "../invariant.js";
42
42
  import { doublecheckHandler, hostStampsIgnorable } from "./command.js";
43
43
  export const name = 'doublecheck-guard';
44
44
  export const inject = ['commands'];
45
+ /**
46
+ * The gate's settings namespace. Hyphenated on purpose: the host's
47
+ * `NAMESPACE_PATTERN` (`/^[a-z][a-z0-9-]*$/`) rejects a dot with a
48
+ * `TypeError`, and a rejected registration never reaches
49
+ * `ctx.settings.describe()`, so no settings surface can see it. v0.9.8 and
50
+ * earlier registered `doublecheck.gate`, which never took effect anywhere.
51
+ */
52
+ export const GATE_SETTINGS_NS = 'doublecheck-gate';
45
53
  export const Config = z.object({
46
54
  intensity: z.union(['remind', 'warn', 'block']).default('remind'),
47
55
  modules: z.object({
@@ -73,6 +81,33 @@ export function apply(ctx, config) {
73
81
  assertPositiveInteger('vagueTaskMaxChars', config.vagueTaskMaxChars);
74
82
  assertGuardTools(config.guardTools);
75
83
  validateGateConfig(config.gate);
84
+ // The effective gate config: the user's stored `doublecheck-gate` section
85
+ // overrides this row's composition entry, which overrides the Schema
86
+ // defaults (the settings service resolves exactly that order). The service
87
+ // is a weak seam — without it, or when the stored section is unusable, the
88
+ // composition entry stands and the reason is logged. `applies: 'restart'`
89
+ // is deliberate: `gate.enabled` decides whether the turn-stopping notice is
90
+ // installed at load, so a live swap could not honor it; the resolved value
91
+ // is therefore read once here and an edit takes effect on the next load.
92
+ const settings = ctx.get('settings');
93
+ let gateConfig = config.gate;
94
+ if (settings !== undefined) {
95
+ try {
96
+ const resolved = settings.register(GATE_SETTINGS_NS, GateConfigSchema, {
97
+ base: config.gate,
98
+ applies: 'restart',
99
+ validate: validateGateConfig,
100
+ }).get();
101
+ // The host validates the resolved section at registration, so this only
102
+ // fires on a host that ignores the `validate` option; degrade rather
103
+ // than fail the whole row over a settings typo.
104
+ validateGateConfig(resolved);
105
+ gateConfig = resolved;
106
+ }
107
+ catch (error) {
108
+ ctx.logger.warn(`dsh-doublecheck: gate settings namespace skipped, using the composition entry: ${String(error)}`);
109
+ }
110
+ }
76
111
  if (config.modules.adversary) {
77
112
  assertBoundedInteger('adversaryMaxFindings', config.adversaryMaxFindings, 20);
78
113
  assertPositiveInteger('adversaryTimeoutMs', config.adversaryTimeoutMs);
@@ -262,35 +297,19 @@ export function apply(ctx, config) {
262
297
  description: 'run the delivery quality gate and report the deliverable/rework decision',
263
298
  input: { hint: 'status|run|config' },
264
299
  handler: gateHandler({
265
- config: config.gate,
300
+ config: gateConfig,
266
301
  detection,
267
302
  prose,
268
- runGate: (agent, signal) => runGate(ctx, config.gate, detection, agent, signal, config.language),
269
- settleGate: (state, agent, signal) => settleGate(ctx, config.gate, state, agent, signal, hostStampsIgnorable()),
303
+ runGate: (agent, signal) => runGate(ctx, gateConfig, detection, agent, signal, config.language),
304
+ settleGate: (state, agent, signal) => settleGate(ctx, gateConfig, state, agent, signal, hostStampsIgnorable()),
270
305
  stampsIgnorable: hostStampsIgnorable,
271
306
  planMode: ctx.get('planMode'),
272
307
  }),
273
308
  });
274
- // The gate settings namespace: the pluggable checklist becomes editable
275
- // through the harness settings surface when one is mounted (weak seam —
276
- // a profile without the settings service simply has no settings page).
277
- const settings = ctx.get('settings');
278
- if (settings !== undefined) {
279
- try {
280
- settings.register('doublecheck.gate', GateConfigSchema, {
281
- base: config.gate,
282
- applies: 'restart',
283
- expose: true,
284
- });
285
- }
286
- catch (error) {
287
- ctx.logger.warn(`dsh-doublecheck: gate settings namespace skipped: ${String(error)}`);
288
- }
289
- }
290
309
  // The gate-red turn notice: once per session, a settled rework verdict
291
310
  // suggests re-opening the work in plan mode. Installed even when every
292
311
  // discipline module is off — the gate panel is advisory, not a gate.
293
- if (config.gate.enabled) {
312
+ if (gateConfig.enabled) {
294
313
  ctx.on('agent/turn-stopping', async ({ agent }) => {
295
314
  if (!doublecheckEnabled(agent.session))
296
315
  return;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-doublecheck",
3
- "version": "0.9.8",
3
+ "version": "0.9.9",
4
4
  "description": "Delivery quality gate for DeepSeek Harness: grill the requirements, test the implementation, prove the delivery, and gate the handoff with a deliverable/rework decision.",
5
5
  "packageManager": "pnpm@11.7.0",
6
6
  "repository": {
@@ -151,6 +151,7 @@
151
151
  "@deepseek-ai/dsh-llm": "0.1.5-alpha.1",
152
152
  "@deepseek-ai/dsh-session": "0.1.5-alpha.1",
153
153
  "@deepseek-ai/dsh-session-projection": "0.1.5-alpha.1",
154
+ "@deepseek-ai/dsh-settings": "0.1.5-alpha.1",
154
155
  "@deepseek-ai/dsh-skill": "0.1.5-alpha.1",
155
156
  "@deepseek-ai/dsh-subagent": "0.1.5-alpha.1",
156
157
  "@deepseek-ai/dsh-system-prompt": "0.1.5-alpha.1",