Skip to content

feat(install): add DSH (DeepSeek Harness) as a skill install target - #1061

Open
luxiang-clx wants to merge 4 commits into
DingTalk-Real-AI:mainfrom
luxiang-clx:feat/dsh-skill-target
Open

feat(install): add DSH (DeepSeek Harness) as a skill install target#1061
luxiang-clx wants to merge 4 commits into
DingTalk-Real-AI:mainfrom
luxiang-clx:feat/dsh-skill-target

Conversation

@luxiang-clx

@luxiang-clx luxiang-clx commented Aug 19, 2026

Copy link
Copy Markdown

Summary

  • Add dsh to every installer registry (JS, Shell, PowerShell, Go) so DWS Skills install under ${DSH_HOME:-$HOME/.dsh}/skills.
  • DSH reads that path via @deepseek-ai/dsh-skill-filesystem's <dshHome>/skills root; without this change, the new agent silently gets no skills.

Risk tier

  • Documentation-only
  • High-risk

Verification

  • ./scripts/policy/check-changelog-pr.sh --content-only origin/main HEAD (run on PR)
  • ./scripts/policy/check-command-surface.sh --strict (run on PR — no command surface change, only agent registry entries)
  • ./scripts/release/verify-package-managers.sh (run on PR after make package — all four registries stay in sync)
  • ./scripts/policy/check-generated-drift.sh (N/A — no generator input or generated artifact touched)
  • Documentation-only tier checks (N/A)
  • Full local suite run (N/A — not high-risk)

Notes

  • install.sh and install-skills.sh are kept byte-identical for the DSH case; both must be updated together when this change is backported.
  • No upstream contract drift; the new agent stays within the pinned total used by TestAgentRegistriesMatchUpstream*.

@github-actions
github-actions Bot enabled auto-merge August 19, 2026 14:47
@haofeng0705

Copy link
Copy Markdown
Collaborator

It's recommended to revise the PR content and remove the meaningless parts

@haofeng0705
haofeng0705 disabled auto-merge August 19, 2026 14:58
@luxiang-clx
luxiang-clx force-pushed the feat/dsh-skill-target branch from 58902ff to 9d1d7e6 Compare August 19, 2026 23:57
@github-actions
github-actions Bot enabled auto-merge August 19, 2026 23:57
Recognizes DeepSeek Harness as a non-universal Agent so DWS skills
install to ${DSH_HOME:-$HOME/.dsh}/skills, matching
@deepseek-ai/dsh-skill-filesystem's <dshHome>/skills discovery root.
auto-merge was automatically disabled August 19, 2026 23:59

Head branch was pushed to by a user without write access

@luxiang-clx
luxiang-clx force-pushed the feat/dsh-skill-target branch from 9d1d7e6 to db4beef Compare August 19, 2026 23:59
@github-actions
github-actions Bot enabled auto-merge August 20, 2026 00:00
@luxiang-clx

Copy link
Copy Markdown
Author

It's recommended to revise the PR content and remove the meaningless parts

done

@haofeng0705
haofeng0705 disabled auto-merge August 20, 2026 01:52
@github-actions
github-actions Bot enabled auto-merge August 20, 2026 09:41
@xianjianlf2

Copy link
Copy Markdown

I opened a stacked fix PR here: luxiang-clx#1

It addresses the current CI blockers I could reproduce:

  • Interface Integrity / Schema compatibility: removes stale consumed flag migration receipts now that base, stable v1.0.59, and the candidate all reached the after state.
  • DSH skill target behavior: Go skill setup/install resolution now honors DSH_HOME, matching the shell installers.

Local verification:

  • go test ./internal/app -run 'TestAgentSkillPathsCoversSetupHomes|TestCrossPlatformCoverageUpstreamAgentEnumerationAndEffectiveRoots'\n- make skill-command-integrity\n- make authoritative-interface-integrity BASE_REF=62d72ad84cb667379c02132148086bd984ea69c9 STABLE_REF=v1.0.59 CANDIDATE_REF=HEAD\n- make schema-compatibility BASE_REF=62d72ad84cb667379c02132148086bd984ea69c9 STABLE_REF=v1.0.59 CANDIDATE_REF=HEAD\n- ./scripts/ci/run-app-race-tests.sh run ./internal/app c (ok ... internal/app 261.605s)\n

…igrations

fix: align dsh skill root handling
auto-merge was automatically disabled August 20, 2026 10:44

Head branch was pushed to by a user without write access

@github-actions
github-actions Bot enabled auto-merge August 20, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants