[PerryLink]

Summary

• Narrow the remote-control surface exposed through WeChat and close the 0.10.0-related paths:
  • audit + secure-fs helpers, stricter config/state validation, bridge/slash hardening, redaction.
• Add scripts/ci-local.sh, a Linux precheck that catches Windows-green/CI-red regressions before push.

Verification

• npm ci --ignore-scripts in a clean upstream/main worktree with these changes applied.
• npm test: 819 passed (50 files).
• npm run build: pass.

Notes

This branch is based on upstream/main (2185375) and intentionally excludes the fork's family-README/docs commits. Please review the security surface carefully; it is a large change concentrated in src/bridge/bridge.ts plus tests.

[PerryLink]

CI build is green. Local verification on a clean upstream/main worktree with these changes applied: npm ci --ignore-scripts; npm test → 819 passed (50 files); npm run build → pass. The branch intentionally excludes the fork-only family README/docs commits.

[PerryLink]

Updated this PR with the DSH 0.2.1-rc.2 adaptation (same PR, not split):

• engines.dsh and the @deepseek-ai/dsh peer are now >=0.2.1-0 <0.3.0-0;
• admission matrix explicitly covers 0.2.1-rc.2; the 0.2.0 line is no longer claimed;
• version 0.11.1; README/PUBLISH/CHANGELOG synced.

Verification: npx vitest run tests/host-line.test.ts 29/29; full suite 821 passed; npm run build pass. A real rc.2 host smoke with published 0.11.0 already returned HTTP 200 + boot marker. The security/CI changes remain in the same PR as requested.