[PR #1524] [MERGED] test(clients): verify native DeepSeek Harness integration #2941

New issue

Closed

opened 2026-10-17 21:12:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-17 21:12:04 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1524
Author: @N0zoM1z0
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/10/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/deepseek-harness-client

📝 Commits (4)

acd6479 test(clients): verify native DeepSeek Harness integration
b13ed80 fix(ci): avoid load-sensitive escape regression timing
a01bf17 chore: merge CI escape regression timing fix
1a65f54 chore: sync main CI regression coverage

📊 Changes

4 files changed (+400 additions, -0 deletions)

View changed files

📝 docs/installation.md (+38 -0)
📝 docs/testing.md (+15 -0)
📝 package.json (+1 -0)
➕ scripts/verify-deepseek-client.mjs (+346 -0)

📄 Description

DeepSeek Harness users had no tested REA recipe, and #1212 had only schema-level regression coverage. Document its native Cordis MCP patch and add an optional verifier using an installed dsh client, isolated profiles and a deterministic loopback model. Generic rea setup --client does not claim to edit this patch format.

The verifier checks ordinary chat with REA enabled, all 139 tools, the actual model-facing input schemas (166 regex occurrences), native installed-skill loading, Unicode-path analysis and complete JavaScript Evidence. Background title requests do not advance the main workflow. Request artifacts, Evidence digests and owned-process lineage are retained.

Validation:

Actual @deepseek-ai/dsh@0.2.0-rc.2: source and independently installed production-only tarball, each in call and chat modes; all four passed with no live owned descendants.
npm run check:fast and focused advertised-pattern/schema-validity tests (8 tests) passed.
Local OpenAI-compatible adapter only; live DeepSeek API, native Windows and Hopper/Ghidra are unverified. The optional lane is not added to routine CI.

Related: #1212.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1524 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/deepseek-harness-client` --- ### 📝 Commits (4) - [`acd6479`](https://github.com/morluto/rea/commit/acd647926097fddf1c89b9a73735bd00173fd89e) test(clients): verify native DeepSeek Harness integration - [`b13ed80`](https://github.com/morluto/rea/commit/b13ed802955be032508c24d990374d3c848951c5) fix(ci): avoid load-sensitive escape regression timing - [`a01bf17`](https://github.com/morluto/rea/commit/a01bf17fad244f2bf06a25744e6711bfa7ac79c7) chore: merge CI escape regression timing fix - [`1a65f54`](https://github.com/morluto/rea/commit/1a65f546b3640b81b738f9c9402af7f74052e288) chore: sync main CI regression coverage ### 📊 Changes **4 files changed** (+400 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+38 -0) 📝 `docs/testing.md` (+15 -0) 📝 `package.json` (+1 -0) ➕ `scripts/verify-deepseek-client.mjs` (+346 -0) </details> ### 📄 Description DeepSeek Harness users had no tested REA recipe, and #1212 had only schema-level regression coverage. Document its native Cordis MCP patch and add an optional verifier using an installed `dsh` client, isolated profiles and a deterministic loopback model. Generic `rea setup --client` does not claim to edit this patch format. The verifier checks ordinary chat with REA enabled, all 139 tools, the actual model-facing input schemas (166 regex occurrences), native installed-skill loading, Unicode-path analysis and complete JavaScript Evidence. Background title requests do not advance the main workflow. Request artifacts, Evidence digests and owned-process lineage are retained. Validation: - Actual `@deepseek-ai/dsh@0.2.0-rc.2`: source and independently installed production-only tarball, each in `call` and `chat` modes; all four passed with no live owned descendants. - `npm run check:fast` and focused advertised-pattern/schema-validity tests (8 tests) passed. - Local OpenAI-compatible adapter only; live DeepSeek API, native Windows and Hopper/Ghidra are unverified. The optional lane is not added to routine CI. Related: #1212. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-17 21:12:04 +00:00