Connect AIWG to DeepSeek Harness

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

Status: Experimental. Qualified against `dsh-v0.1.3-alpha.1` at commit

`d347e703908d0406b7a7ef80e3a0e594d86b2215`.

Install DeepSeek Harness using its upstream instructions. Start with Install, Connect, and Verify for the general AIWG setup journey, then:

Use AIWG to complete this documented outcome: Install DeepSeek Harness using its upstream instructions. Start with Install, Connect, and Verify for the general AIWG setup journey, then
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

To run the opt-in OpenRouter conformance smoke, first load the credential into the current process from your approved secret manager. Do not put it on the command line or in a file:

export OPENROUTER_API_KEY="...loaded from your vault..."
AIWG_DSH_LIVE_SMOKE=1 \
  npx -y the package option=@deepseek-ai/[email protected] -- \
  npm run smoke:deepseek-harness:live

The opt-in makes a real model request and may incur provider charges. The smoke creates and removes an isolated workspace, Harness home, and mode-0600 route overlay; pins and records the Harness version; requires an exact marker response; keeps stdout/stderr separate; and scans both for the injected credential value. the check option validates the gate without making a network call:

node tools/providers/deepseek-harness-live-smoke.mjs the check option

Set `AIWG_DSH_BIN` to an exact-version executable when `dsh` is not already on `PATH`. The smoke never reads the user's Harness home, settings, credentials, or prior sessions.