[DSH adapter] Expose credential-reference and auto-recovery controls #2485

Pre-submission checklist | 提交前检查

• I have searched existing issues and this hasn't been mentioned before | 我已搜索现有问题，确认此问题尚未被提及
• I have read the project documentation and confirmed this issue doesn't already exist | 我已阅读项目文档并确认此问题尚未存在
• This issue is specific to MemOS and not a general software issue | 该问题是针对 MemOS 的，而不是一般软件问题

Problem Statement | 问题陈述

Problem statement

I use the DSH adapter in DeepSeek Harness Desktop 0.2.0-rc.2 with @memtensor/memos-local-plugin 2.0.20. Two adapter controls are currently maintained as a local pnpm patch, so package upgrades overwrite them:

1. An optional credentialRef setting that resolves a named reference through DSH's credentials service for an integration that needs a secret. This should use a scoped/safe credential flow; the local workaround places the resolved value in process.env, which I do not recommend adopting verbatim. No credential values are included here.
2. An autoRecoveryEnabled setting (default true) so a DSH profile can disable adapter recovery without changing the shared MemOS memory configuration.

The same local patch also changes DSH message source construction from the legacy { kind: "plugin", plugin: ... } shape to the newer kind: "plugin:<name>" form. Please confirm the supported source contract for current DSH and keep the adapter aligned/documented.

Request

Could the adapter expose supported configuration for these DSH-specific controls, with credentials handled without leaking into process-global state, and document the expected message-source shape? I can split these into focused PRs if the direction is useful.

Environment

• DSH Desktop: 0.2.0-rc.2 (Windows x64)
• Plugin: @memtensor/memos-local-plugin 2.0.20
• This is specific to the DeepSeek Harness adapter; OpenClaw/Hermes behavior need not change.

Willingness to Implement | 实现意愿

• I'm willing to implement this myself | 我愿意自己解决
• I would like someone else to implement this | 我希望其他人来解决