fix(daemon): register a verified runtime-memory policy for DeepSeek Harness

[zfy0701]

Summary

Selecting the none memory provider for an agent on dsh-acp (DeepSeek Harness) failed at launch with none memory is not supported for this runtime (off-switch unverified): dsh-acp. The runtime was never classified in the runtime-memory registry, and it is also the default pool preset runtime, so every preset agent that picked none hit this.

• Register dsh-acp in RUNTIME_MEMORY_POLICIES as a verified no-op (same classification as kiro-cli).
• Add a dsh profile to the ACP matrix so the runtime-memory contract test covers it.

Why a no-op is correct

Checked against the pinned adapter, @openma/deepseek-harness-acp@0.4.33, whose vendored runtime is dsh 0.1.5-rc.1:

• No memory package in the default composition; the dsh README lists memory MCP servers as an opt-in overlay under config/examples/, never part of a default profile.
• dsh-session-reference (cross-session context) is not mounted by dsh-base, the ACP app, or the preset.
• session-query-sqlite is path: ':memory:', openAt: never.

native stays unsupported: $DSH_HOME also owns credentials, presets and settings, so redirecting it needs its own isolation design (same reasoning as Grok).

The classification holds for this adapter version; a bump of DEEPSEEK_HARNESS_ACP_VERSION should re-check the default profile.

Matrix profile

The scenario/caps are taken from the adapter's initialize and configOptions: loadSession, http-only MCP, image prompts (the base mounts attachment-local), a sandbox-mode selector (read-only / workspace-write / danger-full-access), model and reasoning-effort selectors, prompt usage, and the universal skills identity from the curated catalog.

Test plan

• vitest run test/acp-matrix/runtime-memory-contract.test.ts test/memory-provider-dispatch.test.ts test/runtime-launch.test.ts test/evaluation-permission.test.ts (105 passed)
• daemon typecheck, eslint, prettier

🤖 Generated with Claude Code · Claude Opus 5.5

[agentconnect-md-test]

Approved. The dsh-acp policy enables none for the reviewed 0.4.33 default composition, where cross-session memory is not mounted, while keeping native unsupported. The new ACP matrix profile records that provider contract. I found no blocking issue in the verified merge. git diff --check passed; I could not rerun Vitest locally because this checkout has no installed dependencies. Recheck the no-op classification when the adapter version changes.

_{sent by review-bot (Codex · gpt-6-sol) · open in session}