dsh-doublecheck 0.9.2 → 0.9.3

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to dsh-doublecheck are recorded here, newest first.
 
+## [0.9.3] - 2026-09-02
+
+### Changed
+
+- Align the devDependency pins to the published dsh 0.1.2-alpha.5 line and re-verify the adaptation claims; no behavior change.
+
 ## [0.9.2] - 2026-09-01
 
 ### Changed

package/README.es.md

@@ -223,8 +223,8 @@ El CLI solo serializa el `GateState` ya asentado — nunca vuelve a ejecutar la
 
 ## Limitaciones conocidas
 
-- **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-alpha.3` 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.
-0.1.2-alpha.3 (adaptado el 2026-09-01): 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.
+- **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-alpha.5` 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.
+0.1.2-alpha.5 (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.
 - **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`.
 - **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.
 - **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.

package/README.hi.md

@@ -223,8 +223,8 @@ CLI केवल पहले से स्थापित `GateState` को
 
 ## ज्ञात सीमाएँ
 
-- **टिकाऊ लेखन।** `/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-alpha.3` केवल संग्रहीत-लॉग पठन संगतता के लिए फ़ील्ड बहाल करता है और अभी भी स्टैम्प नहीं कर सकता) पर लेखन छोड़ दिया जाता है और स्विच प्रक्रिया-स्थानीय रहता है।
-0.1.2-alpha.3 (2026-09-01 को अनुकूलित): सत्र लिफ़ाफ़ा अपना ignorable फ़ील्ड केवल संग्रहीत-लॉग पठन संगतता के लिए रखता है - Session.append अभी भी इसे स्टैम्प नहीं कर सकता, इसलिए गेट व्यवहार अपरिवर्तित है।
+- **टिकाऊ लेखन।** `/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-alpha.5` केवल संग्रहीत-लॉग पठन संगतता के लिए फ़ील्ड बहाल करता है और अभी भी स्टैम्प नहीं कर सकता) पर लेखन छोड़ दिया जाता है और स्विच प्रक्रिया-स्थानीय रहता है।
+0.1.2-alpha.5 (2026-09-02 को अनुकूलित): सत्र लिफ़ाफ़ा अपना ignorable फ़ील्ड केवल संग्रहीत-लॉग पठन संगतता के लिए रखता है - Session.append अभी भी इसे स्टैम्प नहीं कर सकता, इसलिए गेट व्यवहार अपरिवर्तित है।
 - **वैकल्पिक इंटरफ़ेस।** `doublecheck.gate` सेटिंग्स नेमस्पेस केवल तब पंजीकृत होता है जब सेटिंग्स सेवा माउंट हो; `/gate status` की प्लान-मोड पंक्ति वैकल्पिक `ctx.planMode` पढ़ती है (इसके बिना `unknown` दिखाती है); प्रतिकूल समीक्षा को `ctx.subagents` चाहिए; सत्यापन को `workflowEngine` चाहिए।
 - **स्थानीय अवनति।** जब dsh-auto-review अनुपस्थित हो या इस सत्र में उसके कोई निर्णय रिकॉर्ड न हों, तो `gate.review.engine: auto` स्थानीय समीक्षक पर घट जाता है — रिपोर्ट निर्णय गढ़ने के बजाय कारण बताती है।
 - **dsh-eval साक्ष्य फ़ाइल-आधारित है।** dsh-auto-review का मूल्यांकन इंजन (`dsh-eval`) अपने prompt-regression / stress / fairness परिणाम कार्यक्षेत्र रिपोर्ट फ़ाइल में लिखता है, सत्र लॉग में नहीं। `gate.tests.evalReports.enabled` उस फ़ाइल को मोड़ता है (डिफ़ॉल्ट रूप से बंद; अनुपस्थित होने पर छोड़ देता है) और मोड़ी गई गणनाएँ टिकाऊ `doublecheck/gate` रिकॉर्ड पर चलती हैं, ताकि तयशुदा रन फिर भी रीप्ले हो सके।

package/README.md

@@ -224,8 +224,8 @@ The CLI only serializes the already-settled `GateState` — it never re-runs the
 
 ## Known limitations
 
-- **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-alpha.3` restores the field for stored-log read compatibility only and still cannot stamp it), the writes are skipped and the switch stays process-local.
-0.1.2-alpha.3 (adapted 2026-09-01): 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.
+- **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-alpha.5` restores the field for stored-log read compatibility only and still cannot stamp it), the writes are skipped and the switch stays process-local.
+0.1.2-alpha.5 (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.
 - **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`.
 - **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.
 - **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.

package/README.pt.md

@@ -223,8 +223,8 @@ O CLI apenas serializa o `GateState` já assentado — nunca reexecuta a porta d
 
 ## Limitações conhecidas
 
-- **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-alpha.3` 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.
-0.1.2-alpha.3 (adaptado em 2026-09-01): 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.
+- **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-alpha.5` 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.
+0.1.2-alpha.5 (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.
 - **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`.
 - **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.
 - **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.

package/README.zh.md

@@ -223,8 +223,8 @@ CLI 只序列化已定的 `GateState` —— 它从不重新运行四阶段门
 
 ## 已知限制
 
-- **持久写入。** `/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-alpha.3` 仅恢复存量日志读取兼容字段、仍无法盖章），写入被跳过、开关保持进程内状态。
-0.1.2-alpha.3（2026-09-01 已适配）：会话信封保留 ignorable 字段但仅用于存量日志读取兼容——Session.append 仍无法盖章，门控行为不变。
+- **持久写入。** `/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-alpha.5` 仅恢复存量日志读取兼容字段、仍无法盖章），写入被跳过、开关保持进程内状态。
+0.1.2-alpha.5（2026-09-02 已适配）：会话信封保留 ignorable 字段但仅用于存量日志读取兼容——Session.append 仍无法盖章，门控行为不变。
 - **可选接口。** `doublecheck.gate` 设置命名空间仅在挂载设置服务时注册；`/gate status` 的计划模式行读取可选的 `ctx.planMode`（没有则显示 `unknown`）；对抗式评审需要 `ctx.subagents`；验证需要 `workflowEngine`。
 - **本地降级。** 当 dsh-auto-review 缺失或本会话没有裁决记录时，`gate.review.engine: auto` 会降级到本地评审者——报告会写明原因，而不是捏造裁决。
 - **dsh-eval 证据基于文件。** dsh-auto-review 评测引擎（`dsh-eval`）把其 prompt 回归 / 压测 / 公平性结果写入工作区报告文件，而非会话日志。`gate.tests.evalReports.enabled` 折叠该文件（默认关闭；缺失时跳过），折叠出的计数随持久 `doublecheck/gate` 记录保存，使已定的运行仍可重放。

package/lib/grill/index.js

@@ -19,6 +19,7 @@ import { DEFAULT_MUTATION_TOOLS, DEFAULT_TEST_COMMAND_PATTERNS, DEFAULT_TEST_FIL
 import { SPEC_TOOL_NAME } from "../domain/stages.js";
 import { buildVerifyScript, deriveReportVerdict, foldReportFacts, renderReportMarkdown, VERIFY_META, } from "../domain/report.js";
 import { SPEC_FIELD_NAMES, VERIFY_DIMENSIONS } from "../domain/vocabulary.js";
+import { sessionEvents } from "../session-events.js";
 import { BundledSkillProvider, PROVIDER_NAME } from "./provider.js";
 export const name = 'doublecheck-grill';
 export const inject = ['skills', 'tools'];
@@ -362,7 +363,7 @@ export function apply(ctx, config) {
             const session = exec.agent?.session;
             const facts = session === undefined
                 ? { spec: null, testRuns: { failed: 0, passed: 0 }, timeline: [], edits: 0, review: null }
-                : foldReportFacts(session.events, reportDetection);
+                : foldReportFacts(sessionEvents(session), reportDetection);
             const verify = args.verify ?? config.reportVerify;
             const verification = verify
                 ? await runVerifyWorkflow(ctx, config, facts.spec, exec)

package/lib/guard/command.js

@@ -15,6 +15,7 @@
  */
 import { createUserMessage } from '@deepseek-ai/dsh-llm';
 import { Session, SessionId } from '@deepseek-ai/dsh-session';
+import { sessionEvents } from "../session-events.js";
 import { deriveReportVerdict, foldReportFacts, renderReportMarkdown } from "../domain/report.js";
 import { PROSE } from "./prose.js";
 /**
@@ -106,7 +107,7 @@ export function doublecheckHandler(deps) {
             };
         }
         if (input === 'report') {
-            const facts = foldReportFacts(session.events, detection);
+            const facts = foldReportFacts(sessionEvents(session), detection);
             const report = {
                 ...facts,
                 verdict: deriveReportVerdict(facts, null),

package/lib/guard/gate.js

@@ -24,6 +24,7 @@
  * @module dsh-doublecheck/guard/gate
  */
 import { createUserMessage } from '@deepseek-ai/dsh-llm';
+import { sessionEvents } from "../session-events.js";
 import z from '@deepseek-ai/schemastery';
 import { attachEvalChecks, countRedChecks, DEFAULT_COVERAGE_PATTERN, DEFAULT_EVAL_REPORTS_CONFIG, DEFAULT_GATE_QUESTIONS, deriveGateVerdict, evaluateConsistency, evaluateRequirements, evaluateReview, evaluateTests, foldAutoReviewEvidence, foldRequirementsEvidence, foldTestEvidence, GATE_FINDINGS_SCHEMA, parseEvalReport, renderGateReportJson, renderGateReportMarkdown, renderPhaseMarkdown, skippedPhase, } from "../domain/gate.js";
 import { sortFindings } from "./review.js";
@@ -295,7 +296,7 @@ function autoReviewInstalled(ctx, agent) {
             // Fall through to the durable-event probe.
         }
     }
-    return agent.session.events.some(event => event.type.startsWith('autoReview/'));
+    return sessionEvents(agent.session).some(event => event.type.startsWith('autoReview/'));
 }
 /**
  * Run the full delivery gate over the agent's session and settle the state.
@@ -310,7 +311,7 @@ function autoReviewInstalled(ctx, agent) {
  * @returns the settled gate state.
  */
 export async function runGate(ctx, config, detection, agent, signal, language) {
-    const events = agent.session.events;
+    const events = sessionEvents(agent.session);
     const coverageRegex = new RegExp(config.tests.coveragePattern, 'i');
     const requirements = config.requirements.enabled
         ? evaluateRequirements(foldRequirementsEvidence(events, config.requirements.interrogateTool), { checklist: config.requirements.checklist, minConfirmed: config.requirements.minConfirmed })
@@ -511,7 +512,7 @@ export function gateHandler(deps) {
         if (input !== 'status' && input !== '') {
             return { kind: 'error', text: prose.gateCommandUnknown(invocation.rawInput.trim()) };
         }
-        const events = session.events;
+        const events = sessionEvents(session);
         const coverageRegex = new RegExp(config.tests.coveragePattern, 'i');
         const requirements = config.requirements.enabled
             ? evaluateRequirements(foldRequirementsEvidence(events, config.requirements.interrogateTool), { checklist: config.requirements.checklist, minConfirmed: config.requirements.minConfirmed })

package/lib/guard/index.js

@@ -27,6 +27,7 @@
  * @module dsh-doublecheck/guard
  */
 import { createUserMessage } from '@deepseek-ai/dsh-llm';
+import { sessionEvents } from "../session-events.js";
 import z from '@deepseek-ai/schemastery';
 import { DEFAULT_MUTATION_TOOLS, DEFAULT_TEST_COMMAND_PATTERNS, DEFAULT_TEST_FILE_PATTERNS, DEFAULT_TEST_TOOL_NAMES, compileDetection, isTestFilePath, mutationTargetPath, parseRawArguments, } from "../domain/evidence.js";
 import { emptyDisciplineState, foldDisciplineRange } from "../domain/stages.js";
@@ -197,12 +198,12 @@ export function apply(ctx, config) {
     }
     /**
      * Fold the session log to its current guard facts. The log is append-only
-     * and `session.events` is an immutable snapshot replaced on each append, so
+     * and the event snapshot is an immutable array replaced on each append, so
      * a resumed fold reuses the already-folded prefix: a per-call read costs
      * O(new events) instead of rescanning the whole log.
      */
     function snapshotOf(session) {
-        const events = session.events;
+        const events = sessionEvents(session);
         const cached = snapshots.get(session);
         if (cached !== undefined) {
             if (cached.events === events && events.length === cached.scanned)

package/lib/invariant.js

@@ -25,6 +25,7 @@
 import { SPEC_FIELD_NAMES } from "./domain/vocabulary.js";
 import { deriveReportVerdict, foldReportFacts } from "./domain/report.js";
 import { deriveGateVerdict, GATE_PHASES } from "./domain/gate.js";
+import { sessionEvents } from "./session-events.js";
 /** Full npm package name owning the reported failures. */
 export const PACKAGE_NAME = 'dsh-doublecheck';
 /** Cordis companion plugin name. */
@@ -49,7 +50,7 @@ export function installInvariant(facts) {
             }
         });
         ctx.on('doublecheck/report', (payload) => {
-            const folded = foldReportFacts(payload.session.events, facts.detection());
+            const folded = foldReportFacts(sessionEvents(payload.session), facts.detection());
             if (payload.verification === null) {
                 const rederived = deriveReportVerdict(folded, null);
                 if (rederived !== payload.verdict) {

package/lib/session-events.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Session event access shared by the guard, grill, and invariant rows.
+ * 0.1.2-alpha.5 renamed the `Session.events` getter to `snapshotEvents()`
+ * while the peer floor (>=0.1.0-rc.8) still exposes `.events`; the runtime
+ * probe below keeps both harness lines working without tightening peers.
+ * @module dsh-doublecheck/session-events
+ */
+import type { Session, SessionEvent } from '@deepseek-ai/dsh-session';
+/** A session-like that only needs to expose the events the folds read. */
+export type SessionEventsSource = Session | {
+    events?: readonly SessionEvent[];
+};
+/**
+ * The current event snapshot of one session, whichever harness line owns it.
+ * @param session - the host Session (or a fixture-shaped session in tests).
+ * @returns a frozen full log snapshot on alpha.5+, the `.events` array earlier.
+ */
+export declare function sessionEvents(session: SessionEventsSource | null | undefined): readonly SessionEvent[];

package/lib/session-events.js

@@ -0,0 +1,19 @@
+/**
+ * Session event access shared by the guard, grill, and invariant rows.
+ * 0.1.2-alpha.5 renamed the `Session.events` getter to `snapshotEvents()`
+ * while the peer floor (>=0.1.0-rc.8) still exposes `.events`; the runtime
+ * probe below keeps both harness lines working without tightening peers.
+ * @module dsh-doublecheck/session-events
+ */
+/**
+ * The current event snapshot of one session, whichever harness line owns it.
+ * @param session - the host Session (or a fixture-shaped session in tests).
+ * @returns a frozen full log snapshot on alpha.5+, the `.events` array earlier.
+ */
+export function sessionEvents(session) {
+    if (session === null || session === undefined)
+        return [];
+    if (typeof session.snapshotEvents === 'function')
+        return session.snapshotEvents();
+    return session.events ?? [];
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-doublecheck",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "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.",
   "packageManager": "pnpm@11.7.0",
   "repository": {
@@ -111,7 +111,7 @@
     ],
     "compatibility": {
       "dshVersions": [
-        "0.1.2-alpha.3"
+        "0.1.2-alpha.5"
       ]
     },
     "capability": {
@@ -131,7 +131,7 @@
     "@deepseek-ai/cordis": "^4.0.2",
     "@deepseek-ai/dsh-agent": ">=0.1.0-rc.8 <0.2.0",
     "@deepseek-ai/dsh-commands": ">=0.1.0-rc.8 <0.2.0",
-    "@deepseek-ai/dsh-invariants": "^0.1.1-rc.2",
+    "@deepseek-ai/dsh-invariants": ">=0.1.0-rc.8 <0.2.0",
     "@deepseek-ai/dsh-llm": ">=0.1.0-rc.8 <0.2.0",
     "@deepseek-ai/dsh-session": ">=0.1.0-rc.8 <0.2.0",
     "@deepseek-ai/dsh-session-projection": ">=0.1.1-rc.2 <0.2.0",
@@ -146,17 +146,17 @@
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.2",
     "@deepseek-ai/cordis-plugin-loader": "1.0.2",
-    "@deepseek-ai/dsh-agent": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-commands": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-fs": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-llm": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-session": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-session-projection": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-skill": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-subagent": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-system-prompt": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-tools": "0.1.2-alpha.3",
-    "@deepseek-ai/dsh-workflow": "0.1.2-alpha.3",
+    "@deepseek-ai/dsh-agent": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-commands": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-fs": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-llm": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-session": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-session-projection": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-skill": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-subagent": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-system-prompt": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-tools": "0.1.2-alpha.5",
+    "@deepseek-ai/dsh-workflow": "0.1.2-alpha.5",
     "@deepseek-ai/schemastery": "^3.18.2",
     "@eslint/js": "^9.30.0",
     "@types/node": "^22.15.0",