dsh-proxy-routing v0.4.2

Highlights

• Fixes npm peer resolution for DSH consumers by supporting both public @deepseek-ai/dsh-settings prerelease lines: 0.1.0-rc.8 and 0.1.1-rc.1+.
• Retains the 0.4.1 proxy-routing features, including the official settings namespace, bounded discovery, Web Network Proxy controls, loopback diagnostics, lossless probe serialization, and sanitized status verification.

Validated with 117 passing tests, client typecheck/build, syntax and package checks, and a clean npm installation without --force or --legacy-peer-deps.

dsh-proxy-routing v0.4.1

Highlights

• Migrates proxy persistence to the official proxy-routing settings namespace in $DSH_HOME/settings.yaml.
• Adds Full Access-only bounded proxy discovery and restricted-session guidance.
• Adds the Web Settings → General → Network Proxy row and loopback RPC diagnostics.
• Fixes lossless JSON output for successful probes and sanitizes net_proxy_status --verify results.

Validated with 117 passing tests, client build/typecheck, package checks, and live HTTP/SOCKS5 proxy probes.

dsh-proxy-routing v0.4.0

Highlights

• Migrates persistence to the official ctx.settings proxy-routing namespace in $DSH_HOME/settings.yaml.
• Removes runtime compatibility with the private proxy-agent.json file; existing files are ignored and require manual migration.
• Preserves the v2 canonical route model, direct Agent default, HTTP/CONNECT/SOCKS5 transport behavior, per-execution routing, and provider-specific routing.
• Declares profile username/password fields as secret settings roles and keeps status, logs, and tool output redacted.
• Keeps serialized ControlPlane transitions, revision/CAS checks, participant prepare/commit/finalize/rollback/dispose lifecycle, settings-backed compensation, and external hot reload.

Validation

• Canonical and settings migration tests passed.
• Targeted ControlPlane suite: 8 passed.
• Host module node --check passed.
• npm pack --dry-run passed.

The npm publish command was attempted against the public registry; this environment reported ENEEDAUTH because npm credentials are not configured.