v1.1.0

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.1.0

Full Changelog: v1.0.9...v1.1.0

v1.0.9

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.9

Full Changelog: v1.0.8...v1.0.9

v1.0.8

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.8

Full Changelog: v1.0.7...v1.0.8

v1.0.7

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.7

Full Changelog: v1.0.6...v1.0.7

v1.0.6

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.6

Full Changelog: v1.0.5...v1.0.6

v1.0.5

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.5

Full Changelog: v1.0.4...v1.0.5

v1.0.4

npm: https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.4

Full Changelog: v1.0.3...v1.0.4

v1.0.3

Terminal authentication for ACP clients, published as deepseekharness-acp-interactive@1.0.3.

• initialize advertises a terminal auth method (Configure DeepSeek API key, args: ["--setup"]) when the client declares the stable ACP v1 clientCapabilities.auth.terminal capability or the ACP Registry validator's legacy _meta["terminal-auth"] flag; other clients are not offered the method.
• dsh-acp-interactive --setup runs an isolated composition containing only @deepseek-ai/dsh-credentials-local, prompts without echoing, and stores DEEPSEEK_API_KEY through the Harness credential store. The ordinary ACP transport never handles or prints the secret and keeps stdout reserved for JSON-RPC.
• Packed-install verification exercises --setup and the real launcher (initialize → session/new with a session-scoped MCP server → session/close).

Assets: deepseekharness-acp-interactive-1.0.3.tgz is the tarball published to npm (npm dist.shasum 542a013ead19a8f43c8df7477e3ef93930e29a13); SHA256SUMS.txt holds its SHA-256.

Install: npm install --global deepseekharness-acp-interactive@1.0.3 — https://www.npmjs.com/package/deepseekharness-acp-interactive/v/1.0.3