context-guardian-deepseek-harness 0.3.4 → 0.3.5
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/README.md +20 -3
- package/README.zh-CN.md +17 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -27,11 +27,11 @@ dsh plugin --profile web add context-guardian-deepseek-harness
|
|
|
27
27
|
|
|
28
28
|
The adapter and Python core share a versioned bridge contract and must stay on
|
|
29
29
|
the same `0.3.x` release line. Pin both sides when reproducing a published setup;
|
|
30
|
-
for example, the `0.3.
|
|
30
|
+
for example, the `0.3.5` pair is:
|
|
31
31
|
|
|
32
32
|
```bash
|
|
33
|
-
python3 -m pip install "context-guardian-core==0.3.
|
|
34
|
-
dsh plugin --profile web add context-guardian-deepseek-harness@0.3.
|
|
33
|
+
python3 -m pip install "context-guardian-core==0.3.5"
|
|
34
|
+
dsh plugin --profile web add context-guardian-deepseek-harness@0.3.5
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
If an older core does not recognize an operation used by the adapter, the
|
|
@@ -129,6 +129,23 @@ Preview with its deterministic Reviewed Facts block. It uses a replay model, so
|
|
|
129
129
|
DeepSeek API key is required.
|
|
130
130
|
Exit the temporary Web process with Ctrl-C when finished.
|
|
131
131
|
|
|
132
|
+
For release verification against the real Harness host and its configured model,
|
|
133
|
+
run the same fixture in live mode:
|
|
134
|
+
|
|
135
|
+
```bash
|
|
136
|
+
CONTEXT_GUARDIAN_DSH_LIVE=1 \
|
|
137
|
+
CONTEXT_GUARDIAN_FIXTURE_PACKAGE=context-guardian-deepseek-harness@0.3.5 \
|
|
138
|
+
npm run dsh-fixture-smoke
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Live mode uses the existing DSH home and provider route, so the configured Harness
|
|
142
|
+
credential stays inside Harness and is never passed to Python. It seeds a long session
|
|
143
|
+
with one deliberately unresolved future-relevant topic. In the Web UI, enter
|
|
144
|
+
`/compact`, confirm that a bounded topic-level Review question appears, manually choose
|
|
145
|
+
Keep or Drop, and confirm that native compaction finishes. The exact question is model-
|
|
146
|
+
dependent: if the native Preview already keeps the topic, zero questions is a valid
|
|
147
|
+
result. Use replay mode for deterministic CI and live mode for the actual host/UI check.
|
|
148
|
+
|
|
132
149
|
## Disable or uninstall
|
|
133
150
|
|
|
134
151
|
To temporarily disable Context Guardian, open `Settings → Agent Presets`, select the
|
package/README.zh-CN.md
CHANGED
|
@@ -30,11 +30,11 @@ dsh plugin --profile web add context-guardian-deepseek-harness
|
|
|
30
30
|
```
|
|
31
31
|
|
|
32
32
|
适配器与 Python 核心共用带版本的 bridge 合同，必须保持在同一条 `0.3.x` 发布线上。
|
|
33
|
-
复现已发布配置时请固定两边的版本；例如 `0.3.
|
|
33
|
+
复现已发布配置时请固定两边的版本；例如 `0.3.5` 配对安装如下：
|
|
34
34
|
|
|
35
35
|
```bash
|
|
36
|
-
python3 -m pip install "context-guardian-core==0.3.
|
|
37
|
-
dsh plugin --profile web add context-guardian-deepseek-harness@0.3.
|
|
36
|
+
python3 -m pip install "context-guardian-core==0.3.5"
|
|
37
|
+
dsh plugin --profile web add context-guardian-deepseek-harness@0.3.5
|
|
38
38
|
```
|
|
39
39
|
|
|
40
40
|
如果旧核心不认识适配器使用的操作，适配器的 fail-open warning 会包含底层 bridge
|
|
@@ -126,6 +126,20 @@ Preview 缺少部分事实。打开 Harness UI 后，先选择名为
|
|
|
126
126
|
确定性 Reviewed Facts 区块。它使用 replay model，不需要 DeepSeek API Key。结束临时 Web 进程时
|
|
127
127
|
按 Ctrl-C。
|
|
128
128
|
|
|
129
|
+
如果要验证真实 Harness 宿主、真实模型和真实 Review UI，可以运行 live fixture：
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
CONTEXT_GUARDIAN_DSH_LIVE=1 \
|
|
133
|
+
CONTEXT_GUARDIAN_FIXTURE_PACKAGE=context-guardian-deepseek-harness@0.3.5 \
|
|
134
|
+
npm run dsh-fixture-smoke
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
live 模式使用现有 DSH home 和 Provider 路由，认证信息留在 Harness 内，不会传给 Python。
|
|
138
|
+
它会预置一个足够长的会话，并额外加入一个刻意未决、与未来安全设计有关的主题。打开 Web
|
|
139
|
+
后输入 `/compact`，确认出现不超过 3 个主题问题，手动选择 Keep 或 Drop，并确认原生压缩
|
|
140
|
+
完成。具体是否弹出问题取决于模型：如果原生 Preview 已经保留该主题，0 个问题也是正确
|
|
141
|
+
结果。replay 模式用于确定性 CI，live 模式用于真实宿主/UI 验证。
|
|
142
|
+
|
|
129
143
|
如果无头组合没有 answerer，适配器会明确报告 Review UI 不可用，并接受已经成功的
|
|
130
144
|
原生 Preview。只有在明确配置无 UI 运行时才设置 `CONTEXT_GUARDIAN_NO_UI=1`；此时
|
|
131
145
|
未决主题按保守建议处理。
|