dsh-session-sync 0.2.17 → 0.2.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -1
- package/README-es.md +4 -3
- package/README-hi.md +4 -3
- package/README-pt.md +4 -3
- package/README-zh.md +4 -3
- package/README.md +4 -3
- package/package.json +15 -15
package/CHANGELOG.md
CHANGED
|
@@ -5,7 +5,19 @@ All notable changes to this project are documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
-
## [
|
|
8
|
+
## [0.2.19] - 2026-09-24
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- Host pins move to `0.1.7-rc.1`; re-verified against that host line. Every `@deepseek-ai/dsh-*` dev/test dependency now pins `0.1.7-rc.1`, the `pnpm-lock.yaml` graph is regenerated, `dshWorkshop.compatibility.dshVersions` appends `0.1.7-rc.1`, the monthly Compat workflow and the CI probe install the `0.1.7-rc.1` host, and the compatibility baseline in every README records `dsh-v0.1.7-rc.1`. The declared host ranges (`engines.dsh` and the `peerDependencies` union) are deliberately **unchanged** — they already admit `0.1.7-rc.1`, and a range is what the manifest accepts, not what has been tested.
|
|
12
|
+
|
|
13
|
+
## [0.2.18] - 2026-09-23
|
|
14
|
+
|
|
15
|
+
### Changed
|
|
16
|
+
|
|
17
|
+
- **Re-verified against the `0.1.7-alpha.2` host; the `@deepseek-ai/dsh-*` host pins move to `0.1.7-alpha.2`.** The `alpha.2` wave removes nothing this plugin consumes: the published type surface of every host package it resolves is either byte-identical to `0.1.7-alpha.1` (`@deepseek-ai/cordis` `4.0.3`≡`4.0.4`, `@deepseek-ai/schemastery` `3.18.3`≡`3.18.4`) or strictly additive (`ToolDefinition.projectContent?`, `ClientModuleLoader.importError()`, six added `dsh-client-locale` keys). The wave's only removals are internals no plugin in this family references — `dsh-subprocess-local` privates and its non-entry `bindManagedProcess`, `dsh-client-web` `assertEntriesActive`, `dsh-app-boot`'s `unhandledRejection` event, `dsh-client-ui-plugin-manager` `apply()`, a refined `dsh-client-ui-primitives` `CodeBlock` signature, and the `diff.files.one`/`diff.files.other` locale key pair. Both rulers therefore stay green on the moved pin: `typecheck` against the checkout, `typecheck:ci` against the published `0.1.7-alpha.2` faces.
|
|
18
|
+
- The declared host range is deliberately **unchanged**. It already admits `0.1.7-alpha.2` (`0.1.7-alpha.2` satisfies the `>=0.1.7-0 <0.2.0` clause), and the family convention keeps peer ranges wider than the verified line rather than narrowing them to it; a range is what the manifest accepts, not what has been tested.
|
|
19
|
+
- Repo documentation (`AGENTS.md`), the workspace graph pin (`pnpm-workspace.yaml`) and the published-line workflow pins move with the manifest, so no file still claims the previous line.
|
|
20
|
+
|
|
9
21
|
|
|
10
22
|
## [0.2.17] - 2026-09-22
|
|
11
23
|
|
package/README-es.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-session-sync/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
20
|
+
[](https://dshfind.com/es/plugins/PerryLink/dsh-session-sync?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Superficie | Estado |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (tag de GitHub, verificado el 2026-09-24: cadena completa de puertas contra los peers `0.1.7-rc.1` fijados). Línea de dependencias npm `0.1.7-rc.1`, peers `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0`. (adaptado el 2026-09-24): el aviso de fork por conflicto lleva el source kind propio del plugin (producer-owned) - el harness retiró el kind compartido `plugin` y lo rechaza al releer. |
|
|
32
33
|
| Node | `^22.19.0 \|\| >=24.0.0` |
|
|
33
34
|
| Plataformas | Cualquier lugar donde `git` y DSH se ejecuten (espejo basado en git; sin código específico de plataforma) |
|
|
34
35
|
| Modelo | Los modelos solo texto funcionan plenamente; no se requiere visión ni capacidad extra |
|
|
@@ -175,7 +176,7 @@ Línea base: con `backend: git` (el predeterminado), los bytes de sesión se alm
|
|
|
175
176
|
|
|
176
177
|
- **El cifrado es opcional.** `backend: encrypted` añade una capa age (ver «Cifrado y modelo de amenazas» arriba); si falta `age` o las claves, cae a texto plano con una advertencia explícita. Con `backend: git` (el predeterminado), los bytes de sesión se almacenan sin cifrar en **tu** remoto git — usa un repositorio privado.
|
|
177
178
|
- **Se requiere git.** El plugin necesita el ejecutable `git` y el servicio `subprocess`; sin ellos, las operaciones de sincronización fallan con un motivo claro (los perfiles siguen arrancando).
|
|
178
|
-
- **Eventos de sesión en `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.
|
|
179
|
+
- **Eventos de sesión en `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.2`.** El harness aún no registra los tipos `sync/*`, por lo que los anexos al registro de sesión se omiten (las sesiones siguen cargando); el plugin los habilita automáticamente una vez que un host registra los tipos o expone el envoltorio `ignorable` en `Session.append`.
|
|
179
180
|
- **`approval` entre turnos.** `/sync` se ejecuta entre turnos, donde el canal `approval` no tiene un turno abierto al que adjuntarse; usa `confirmVia: userQuestions` para la sincronización por comando, o impulsa la sincronización mediante las herramientas dentro de un turno. La comprobación de turno abierto lee la proyección de sesión `turnBoundary` del host: una composición sin `@deepseek-ai/dsh-session-projection` no puede verificar el estado del turno y falla en cerrado con ese motivo.
|
|
180
181
|
- **Los artefactos privados del host no se sincronizan.** `session.lock` (el arriendo de sesión del harness) y los archivos de staging `session.migration.*.tmp` nunca se reflejan ni se eliminan: son estado de ejecución, no contenido sincronizable. Los registros de sesión (`session.jsonl`, `session.v[1-9]*.jsonl[.zstd]`) siguen siendo la carga útil reflejada.
|
|
181
182
|
|
|
@@ -183,7 +184,7 @@ Línea base: con `backend: git` (el predeterminado), los bytes de sesión se alm
|
|
|
183
184
|
|
|
184
185
|
```sh
|
|
185
186
|
pnpm install # node ^22.19 || >=24
|
|
186
|
-
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs contra los peers 0.1.7-alpha.
|
|
187
|
+
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs contra los peers 0.1.7-alpha.2 publicados
|
|
187
188
|
pnpm test # node --test (13 archivos de test; la suite git del motor se omite sin git)
|
|
188
189
|
pnpm run verify:self-contained # las specs de dependencias resuelven desde el registro
|
|
189
190
|
pnpm run verify:artifacts # archivos publicados presentes + index.mjs importable
|
package/README-hi.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-session-sync/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
20
|
+
[](https://dshfind.com/hi/plugins/PerryLink/dsh-session-sync?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| सतह | स्थिति |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (GitHub टैग, 2026-09-24 को सत्यापित: पिन किए गए `0.1.7-rc.1` peers के विरुद्ध पूर्ण गेट श्रृंखला)। npm निर्भरता-लाइन `0.1.7-rc.1`, peers `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0`। (2026-09-24 को अनुकूलित): टकराव फ़ोर्क सूचना प्लगइन का अपना producer-owned source kind रखती है - हार्नेस ने साझा `plugin` kind सेवानिवृत्त कर दिया है और पुनः-पठन पर उसे अस्वीकार करता है। |
|
|
32
33
|
| Node | `^22.19.0 \|\| >=24.0.0` |
|
|
33
34
|
| प्लेटफ़ॉर्म | जहाँ भी `git` और DSH चलते हैं (git-आधारित मिरर; कोई प्लेटफ़ॉर्म-विशिष्ट कोड नहीं) |
|
|
34
35
|
| मॉडल | केवल-टेक्स्ट मॉडल पूर्ण रूप से समर्थित; विज़न या अतिरिक्त क्षमता की आवश्यकता नहीं |
|
|
@@ -175,7 +176,7 @@ dsh --profile web --dump-config | grep -A2 'id: session-sync'
|
|
|
175
176
|
|
|
176
177
|
- **एन्क्रिप्शन वैकल्पिक है।** `backend: encrypted` एक age परत जोड़ता है (ऊपर «एन्क्रिप्शन और ख़तरा मॉडल» देखें); `age` या कुंजियाँ गायब होने पर यह स्पष्ट चेतावनी के साथ सादे-पाठ पर गिर जाता है। `backend: git` (डिफ़ॉल्ट) के साथ सत्र बाइट्स **आपके** git रिमोट में अनएन्क्रिप्टेड रहते हैं — एक निजी रिपॉज़िटरी का उपयोग करें।
|
|
177
178
|
- **git आवश्यक।** प्लगइन को `git` एक्ज़ीक्यूटेबल और `subprocess` सेवा चाहिए; उनके बिना, सिंक ऑपरेशन स्पष्ट कारण से असफल होते हैं (प्रोफ़ाइलें बूट होती रहती हैं)।
|
|
178
|
-
- **`0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.
|
|
179
|
+
- **`0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.2` पर सत्र ईवेंट।** हार्नेस अभी `sync/*` प्रकार पंजीकृत नहीं करता, इसलिए सत्र-लॉग जोड़ छोड़ दिए जाते हैं (सत्र लोड होते रहते हैं); प्लगइन उन्हें स्वतः सक्षम करता है जब कोई होस्ट प्रकार पंजीकृत करता है या `Session.append` पर `ignorable` लिफ़ाफ़ा उजागर करता है।
|
|
179
180
|
- **टर्न के बीच `approval`।** `/sync` टर्न के बीच चलता है, जहाँ `approval` चैनल के पास जोड़ने के लिए कोई खुला टर्न नहीं होता; कमांड-संचालित सिंक के लिए `confirmVia: userQuestions` का उपयोग करें, या टर्न के अंदर टूल द्वारा सिंक चलाएँ। खुले टर्न की जाँच होस्ट के `turnBoundary` सत्र प्रोजेक्शन से होती है: `@deepseek-ai/dsh-session-projection` के बिना संयोजन टर्न स्थिति सत्यापित नहीं कर सकता और उसी कारण के साथ फ़ेल-क्लोज़्ड रहता है।
|
|
180
181
|
- **होस्ट-निजी आर्टिफ़ैक्ट सिंक नहीं होते।** `session.lock` (हार्नेस सत्र लीज़) और `session.migration.*.tmp` स्टेजिंग फ़ाइलें कभी मिरर या हटाई नहीं जातीं — ये रनटाइम स्थिति हैं, सिंक-योग्य सामग्री नहीं। सत्र लॉग (`session.jsonl`, `session.v[1-9]*.jsonl[.zstd]`) ही मिरर की जाने वाली पेलोड रहते हैं।
|
|
181
182
|
|
|
@@ -183,7 +184,7 @@ dsh --profile web --dump-config | grep -A2 'id: session-sync'
|
|
|
183
184
|
|
|
184
185
|
```sh
|
|
185
186
|
pnpm install # node ^22.19 || >=24
|
|
186
|
-
pnpm run typecheck && pnpm run typecheck:ci # प्रकाशित 0.1.7-alpha.
|
|
187
|
+
pnpm run typecheck && pnpm run typecheck:ci # प्रकाशित 0.1.7-alpha.2 peers के विरुद्ध tsc --checkJs
|
|
187
188
|
pnpm test # node --test (13 टेस्ट फ़ाइलें; git इंजन सुइट बिना git के छोड़ी जाती है)
|
|
188
189
|
pnpm run verify:self-contained # निर्भरता spec रजिस्ट्री से हल होती हैं
|
|
189
190
|
pnpm run verify:artifacts # प्रकाशित फ़ाइलें उपस्थित + index.mjs import योग्य
|
package/README-pt.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-session-sync/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
20
|
+
[](https://dshfind.com/pt/plugins/PerryLink/dsh-session-sync?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Superfície | Status |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (tag do GitHub, verificado em 2026-09-24: cadeia completa de portas contra os peers `0.1.7-rc.1` fixados). Linha de dependências npm `0.1.7-rc.1`, peers `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0`. (adaptado em 2026-09-24): o aviso de fork por conflito carrega o source kind próprio do plugin (producer-owned) - o harness aposentou o kind compartilhado `plugin` e o recusa na releitura. |
|
|
32
33
|
| Node | `^22.19.0 \|\| >=24.0.0` |
|
|
33
34
|
| Plataformas | Qualquer lugar onde `git` e o DSH rodem (espelho baseado em git; sem código específico de plataforma) |
|
|
34
35
|
| Modelo | Modelos somente texto são totalmente suportados; sem necessidade de visão ou capacidade extra |
|
|
@@ -175,7 +176,7 @@ Linha de base: com `backend: git` (o padrão), os bytes de sessão são armazena
|
|
|
175
176
|
|
|
176
177
|
- **A criptografia é opcional.** `backend: encrypted` adiciona uma camada age (veja «Criptografia e modelo de ameaças» acima); se o `age` ou as chaves estiverem ausentes, ele cai para texto simples com um aviso explícito. Com `backend: git` (o padrão), os bytes da sessão são armazenados sem criptografia no **seu** remoto git — use um repositório privado.
|
|
177
178
|
- **git é necessário.** O plugin precisa do executável `git` e do serviço `subprocess`; sem eles, as operações de sincronização falham com um motivo claro (os perfis continuam iniciando).
|
|
178
|
-
- **Eventos de sessão no `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.
|
|
179
|
+
- **Eventos de sessão no `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.2`.** O harness ainda não registra os tipos `sync/*`, então os anexos ao registro de sessão são omitidos (as sessões continuam carregando); o plugin os habilita automaticamente quando um host registra os tipos ou expõe o envoltório `ignorable` em `Session.append`.
|
|
179
180
|
- **`approval` entre turnos.** `/sync` roda entre turnos, onde o canal `approval` não tem um turno aberto para se anexar; use `confirmVia: userQuestions` para sincronização por comando, ou conduza a sincronização pelas ferramentas dentro de um turno. A verificação de turno aberto lê a projeção de sessão `turnBoundary` do host: uma composição sem `@deepseek-ai/dsh-session-projection` não consegue verificar o estado do turno e falha fechada com esse motivo.
|
|
180
181
|
- **Artefatos privados do host não são sincronizados.** `session.lock` (a lease de sessão do harness) e os arquivos de staging `session.migration.*.tmp` nunca são espelhados nem excluídos: são estado de execução, não conteúdo sincronizável. Os logs de sessão (`session.jsonl`, `session.v[1-9]*.jsonl[.zstd]`) continuam sendo a carga útil espelhada.
|
|
181
182
|
|
|
@@ -183,7 +184,7 @@ Linha de base: com `backend: git` (o padrão), os bytes de sessão são armazena
|
|
|
183
184
|
|
|
184
185
|
```sh
|
|
185
186
|
pnpm install # node ^22.19 || >=24
|
|
186
|
-
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs contra os peers 0.1.7-alpha.
|
|
187
|
+
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs contra os peers 0.1.7-alpha.2 publicados
|
|
187
188
|
pnpm test # node --test (13 arquivos de teste; a suíte git do motor é omitida sem git)
|
|
188
189
|
pnpm run verify:self-contained # as specs de dependência resolvem do registro
|
|
189
190
|
pnpm run verify:artifacts # arquivos publicados presentes + index.mjs importável
|
package/README-zh.md
CHANGED
|
@@ -19,6 +19,7 @@
|
|
|
19
19
|
[](https://github.com/PerryLink/dsh-session-sync/releases)
|
|
20
20
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
21
21
|
[](https://www.npmjs.com/package/dsh-session-sync)
|
|
22
|
+
[](https://dshfind.com/zh/plugins/PerryLink/dsh-session-sync?ref=badge)
|
|
22
23
|
|
|
23
24
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
24
25
|
|
|
@@ -30,7 +31,7 @@
|
|
|
30
31
|
|
|
31
32
|
| 项目 | 状态 |
|
|
32
33
|
|---|---|
|
|
33
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
34
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1`(GitHub tag,2026-09-24 已核验:完整门控链,针对钉住的 `0.1.7-rc.1` peers)。npm 依赖线 `0.1.7-rc.1`,peers `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0`。(2026-09-24 已适配):冲突 fork 通知携带插件自有的 producer-owned 消息 source kind——宿主已退役共享的 `plugin` kind,读回时一律拒收。 |
|
|
34
35
|
| Node | `^22.19.0 \|\| >=24.0.0` |
|
|
35
36
|
| 平台 | 任何能运行 `git` 和 DSH 的环境(基于 git 镜像;无平台特定代码) |
|
|
36
37
|
| 模型 | 纯文本模型即可完整支持;无需视觉或额外模型能力 |
|
|
@@ -177,7 +178,7 @@ dsh --profile web --dump-config | grep -A2 'id: session-sync'
|
|
|
177
178
|
|
|
178
179
|
- **加密可选。** `backend: encrypted` 增加一层 age 加密(见上文「加密与威胁模型」);`age` 或密钥缺失时它会显式告警并降级为明文。`backend: git`(默认)下,会话字节以未加密形式存放在**你的** git 远端 —— 请使用私有仓库。
|
|
179
180
|
- **依赖 git。** 插件需要 `git` 可执行文件与 `subprocess` 服务;没有它们时同步操作会给出明确原因失败(profile 仍可启动)。
|
|
180
|
-
- **`0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.
|
|
181
|
+
- **`0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.2` 上的会话事件。** harness 尚未收录 `sync/*` 事件类型,因此会话日志追加被跳过(会话仍可加载);宿主收录类型或 `Session.append` 暴露 `ignorable` 信封后插件会自动开启。
|
|
181
182
|
- **轮次间的 `approval`。** `/sync` 在轮次之间运行,`approval` 通道没有开放轮次可挂靠;请对命令式同步使用 `confirmVia: userQuestions`,或在轮次内经工具驱动同步。开放轮次判定读宿主 `turnBoundary` 会话投影:未组合 `@deepseek-ai/dsh-session-projection` 时无法核实轮次状态,按失败关闭并给出该原因。
|
|
182
183
|
- **宿主私有产物不进同步。** `session.lock`(宿主会话租约)与 `session.migration.*.tmp`(迁移暂存)永不镜像、永不删除——它们是运行时状态而非可同步内容;会话日志(`session.jsonl`、`session.v[1-9]*.jsonl[.zstd]`)仍是镜像载荷。
|
|
183
184
|
|
|
@@ -185,7 +186,7 @@ dsh --profile web --dump-config | grep -A2 'id: session-sync'
|
|
|
185
186
|
|
|
186
187
|
```sh
|
|
187
188
|
pnpm install # node ^22.19 || >=24
|
|
188
|
-
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs,针对已发布的 0.1.7-alpha.
|
|
189
|
+
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs,针对已发布的 0.1.7-alpha.2 peers
|
|
189
190
|
pnpm test # node --test(13 个测试文件;git 引擎套件在无 git 时跳过)
|
|
190
191
|
pnpm run verify:self-contained # 依赖 spec 可从 registry 解析
|
|
191
192
|
pnpm run verify:artifacts # 发布文件齐全 + index.mjs 可 import
|
package/README.md
CHANGED
|
@@ -3,6 +3,7 @@
|
|
|
3
3
|
# 🔄 dsh-session-sync
|
|
4
4
|
- **1024 store channel**: `npm i -g dsh1024` once, then `dsh1024 plugin --profile web add dsh-session-sync` (counts toward the [deepseek1024.com](https://deepseek1024.com) install ranking).
|
|
5
5
|
[](https://gitee.com/perrylink/dsh-session-sync)
|
|
6
|
+
[](https://dshfind.com/plugins/PerryLink/dsh-session-sync?ref=badge)
|
|
6
7
|
[](https://api.securityscorecards.dev/projects/github.com/PerryLink/dsh-session-sync)
|
|
7
8
|
|
|
8
9
|
**Cross-device session sync for DeepSeek Harness — a dedicated git mirror of your session store.**
|
|
@@ -31,7 +32,7 @@
|
|
|
31
32
|
|
|
32
33
|
| Surface | Status |
|
|
33
34
|
|---|---|
|
|
34
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
35
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (GitHub tag, verified 2026-09-24: full gate chain against the pinned `0.1.7-rc.1` peers). npm dependency line `0.1.7-rc.1`, peers `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0`. (adapted 2026-09-24): the conflict fork notice carries the plugin's own producer-owned message source kind - the harness retired the shared `plugin` kind and refuses it on read-back. |
|
|
35
36
|
| Node | `^22.19.0 \|\| >=24.0.0` |
|
|
36
37
|
| Platforms | Anywhere `git` and DSH run (git-based mirror; no platform-specific code) |
|
|
37
38
|
| Model | Text-only models fully supported; no vision or extra model capability required |
|
|
@@ -180,7 +181,7 @@ Baseline: with `backend: git` (the default), session bytes are stored unencrypte
|
|
|
180
181
|
- **git required.** The plugin needs the `git` executable and the `subprocess` service; without them, sync operations fail with a clear reason (profiles keep booting).
|
|
181
182
|
- **age is optional, external.** Encryption depends on the `age` binary on `PATH` (or `ageBin`). No `age` → plaintext fallback with a warning; a passphrase-protected identity cannot be used (decryption would block on a TTY prompt, so it fails closed).
|
|
182
183
|
- **One repoDir per backend.** Switching between `git` and `encrypted` on the same `repoDir` is not supported; use a fresh worktree per backend.
|
|
183
|
-
- **Session events on `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.
|
|
184
|
+
- **Session events on `0.1.0-rc.6`/`0.1.0-rc.8`/`0.1.1-rc.2`/`0.1.2-alpha.2`/`0.1.2-alpha.3`/`0.1.2-rc.1`/`0.1.7-alpha.2`.** The harness does not record `sync/*` event types, so the session-log appends are skipped (sessions keep loading); the plugin enables them automatically once a host records the types or exposes the `ignorable` envelope on `Session.append`.
|
|
184
185
|
- **`approval` between turns.** `/sync` runs between turns, where the `approval` channel has no open turn to attach to; use `confirmVia: userQuestions` for command-driven sync, or drive sync through the tools inside a turn. The open-turn check reads the host `turnBoundary` session projection: a composition without `@deepseek-ai/dsh-session-projection` cannot verify the turn state and fails closed with that reason.
|
|
185
186
|
- **Host-private artifacts stay host-private.** `session.lock` (the harness session lease) and `session.migration.*.tmp` staging files are never mirrored or deleted — they are runtime state, not syncable content. Session logs (`session.jsonl`, `session.v[1-9]*.jsonl[.zstd]`) remain the mirrored payload.
|
|
186
187
|
|
|
@@ -188,7 +189,7 @@ Baseline: with `backend: git` (the default), session bytes are stored unencrypte
|
|
|
188
189
|
|
|
189
190
|
```sh
|
|
190
191
|
pnpm install # node ^22.19 || >=24
|
|
191
|
-
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs against the published 0.1.7-alpha.
|
|
192
|
+
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs against the published 0.1.7-alpha.2 peers
|
|
192
193
|
pnpm test # node --test (13 test files; the engine git suite skips without git)
|
|
193
194
|
pnpm run verify:self-contained # dependency specs resolve from the registry
|
|
194
195
|
pnpm run verify:artifacts # shipped files present + index.mjs importable
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-session-sync",
|
|
3
3
|
"description": "Cross-device sync for DeepSeek Harness sessions: a dedicated git mirror of the session store, append-only three-way merge with keep-both + fork conflict resolution, /sync command, sync_pull/sync_push/sync_status tools, and configurable auto push/pull",
|
|
4
|
-
"version": "0.2.
|
|
4
|
+
"version": "0.2.19",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
7
7
|
"url": "git+https://github.com/PerryLink/dsh-session-sync.git"
|
|
@@ -70,7 +70,7 @@
|
|
|
70
70
|
"credentials:none"
|
|
71
71
|
],
|
|
72
72
|
"compatibility": {
|
|
73
|
-
"dshVersions": ["0.1.2-rc.1","0.1.5-rc.2","0.1.7-alpha.1"]
|
|
73
|
+
"dshVersions": ["0.1.2-rc.1","0.1.5-rc.2","0.1.7-alpha.2","0.1.7-rc.1"]
|
|
74
74
|
},
|
|
75
75
|
"capability": {
|
|
76
76
|
"id": "session-sync",
|
|
@@ -107,22 +107,22 @@
|
|
|
107
107
|
"zod": "^4.4.3"
|
|
108
108
|
},
|
|
109
109
|
"devDependencies": {
|
|
110
|
-
"@deepseek-ai/dsh-attachment": "0.1.7-
|
|
110
|
+
"@deepseek-ai/dsh-attachment": "0.1.7-rc.1",
|
|
111
111
|
"@deepseek-ai/cordis": "^4.0.3",
|
|
112
112
|
"@deepseek-ai/cordis-plugin-include": "^1.0.8",
|
|
113
113
|
"@deepseek-ai/cordis-plugin-loader": "^1.0.4",
|
|
114
|
-
"@deepseek-ai/dsh-commands": "0.1.7-
|
|
115
|
-
"@deepseek-ai/dsh-llm": "0.1.7-
|
|
116
|
-
"@deepseek-ai/dsh-session": "0.1.7-
|
|
117
|
-
"@deepseek-ai/dsh-session-format-v3-to-v4": "0.1.7-
|
|
118
|
-
"@deepseek-ai/dsh-storage": "0.1.7-
|
|
119
|
-
"@deepseek-ai/dsh-storage-domain": "0.1.7-
|
|
120
|
-
"@deepseek-ai/dsh-storage-json": "0.1.7-
|
|
121
|
-
"@deepseek-ai/dsh-subprocess": "0.1.7-
|
|
122
|
-
"@deepseek-ai/dsh-system-prompt": "0.1.7-
|
|
123
|
-
"@deepseek-ai/dsh-tools": "0.1.7-
|
|
124
|
-
"@deepseek-ai/dsh-user-approval": "0.1.7-
|
|
125
|
-
"@deepseek-ai/dsh-user-questions": "0.1.7-
|
|
114
|
+
"@deepseek-ai/dsh-commands": "0.1.7-rc.1",
|
|
115
|
+
"@deepseek-ai/dsh-llm": "0.1.7-rc.1",
|
|
116
|
+
"@deepseek-ai/dsh-session": "0.1.7-rc.1",
|
|
117
|
+
"@deepseek-ai/dsh-session-format-v3-to-v4": "0.1.7-rc.1",
|
|
118
|
+
"@deepseek-ai/dsh-storage": "0.1.7-rc.1",
|
|
119
|
+
"@deepseek-ai/dsh-storage-domain": "0.1.7-rc.1",
|
|
120
|
+
"@deepseek-ai/dsh-storage-json": "0.1.7-rc.1",
|
|
121
|
+
"@deepseek-ai/dsh-subprocess": "0.1.7-rc.1",
|
|
122
|
+
"@deepseek-ai/dsh-system-prompt": "0.1.7-rc.1",
|
|
123
|
+
"@deepseek-ai/dsh-tools": "0.1.7-rc.1",
|
|
124
|
+
"@deepseek-ai/dsh-user-approval": "0.1.7-rc.1",
|
|
125
|
+
"@deepseek-ai/dsh-user-questions": "0.1.7-rc.1",
|
|
126
126
|
"@deepseek-ai/schemastery": "^3.18.3",
|
|
127
127
|
"@types/node": "^22.19.0",
|
|
128
128
|
"oxlint": "0.18.1",
|