Proposal: add a DeepSeek Harness (DSH) adapter — purely additive under dsh/

Nobody has claimed this yet.

## Summary

I ported LLMQuant Data's orchestration skills to **DeepSeek Harness (DSH)** — the 6 playbooks in `skills/` (morning-brief, earnings-watch, 13f-diff, portfolio-pulse, polymarket-watch, llmquant-setup) now also run under DSH via the `@llmquant/data-mcp` server. I'd like to contribute this back.

Before opening a PR I want to check scope: **would you accept an additive `dsh/` adapter inside this repo, or would you prefer it as a standalone repo under LLMQuant?**

## What the adapter contains

- `dsh/skills/` — the 6 playbooks rewritten for DSH:
- tool names use DSH's `mcp__llmquant-data__` prefix;
- `hermes cron` / `--deliver telegram` replaced with DSH's actual scheduler (`dsh-schedule` session-local reminders, plus `dsh --profile headless` as the OS-cron primitive);
- Hermes persona/config references (`~/.hermes/SOUL.md`, `hermes skills tap add`) replaced with DSH equivalents (`AGENTS.md`, `/.dsh/skills`).
- `dsh/setup.md` — DSH wiring: `cordis.patch.yml` insert via `@deepseek-ai/dsh-mcp-client`.
- `dsh/config/mcp-dsh.patch.example.yml` — config template (API key masked).
- `dsh/scheduler/` — `dsh headless` wrapper + Windows Task Scheduler / cron examples (DSH has no built-in calendar cron).

## Guarantees

- **Purely additive:** the PR only adds `dsh/**`. Existing `skills/`, `templates/`, `config/`, and `SETUP.md` remain byte-identical — no change to any Hermes behavior.
- **Attribution kept:** it's a derivative of this repo (and `LLMQuant/skills`), both MIT; the notices stay in place.

## Why this helps

DeepSeek Harness ships an MCP client, skill discovery, and a headless CLI, but there's no upstream LLMQuant path for it. The 18 analysis skills in `LLMQuant/skills` are framework-agnostic and reused unchanged; only these 6 orchestration playbooks needed porting.

If you'd rather keep this repo Hermes-only, just say so — I'll publish the adapter as a separate repo and open a small README cross-link instead.

Start by reviewing the proposed dsh/** layout, including dsh/skills/, dsh/setup.md, dsh/config/mcp-dsh.patch.example.yml, and dsh/scheduler/. The first decision is whether this adapter belongs as a purely additive contribution here or in a standalone repository; done means that scope is accepted and the contribution path is clear.

Written by the indexing model from the issue text.