feat(plugins): add restricted DSH ecosystem compatibility

[wangxingjun778]

Feature

• Added P0 compatibility for DeepSeek Harness plugins, supporting pre-built JavaScript packages and Cordis dynamic exports.
• Introduced a restricted Node.js bridge with per-invocation isolation, versioned NDJSON messaging, resource limits, and typed HTTP capabilities.
• Added approval-gated DSH installation with runtime discovery, profile persistence, restart rediscovery, reload, and removal.
• Added component-aware compatibility verdicts, including explicit PARTIAL handling for unsupported Client UI components.

Refactor

• Reworked compatibility assessment around real source inspection and executable ExecutionPlan evidence.
• Replaced compile-only JavaScript adapter generation with deterministic descriptors and Python wrappers.
• Improved profile plugin module tracking to reliably reload generated bridge wrappers.

Enhance

• Hardened bundle validation with hashes, path and symlink checks, size limits, dependency analysis, and required-service detection.
• Added configurable Node runtime timeouts, memory limits, message limits, and bounded stderr capture.
• Extended plugin status output with runtime, source type, verdict, limitations, and skipped Client components.
• Added raw-text and GB18030 support to the governed web_fetch compatibility path.

Fix

• Fixed fail-open compatibility assumptions for unknown dependencies, empty foreign interfaces, and undeclared permissions.
• Fixed detection of npm peer/optional dependencies and Cordis inject service requirements.
• Fixed multi-segment category resolution so architecture-bound plugins such as agent-loop are correctly rejected.
• Fixed partial-install rollback, generated-wrapper reload identity, oversized protocol messages, and Node process cleanup.
• Blocked shell injection and arbitrary commands before any network request can occur.

Documentation

• Added a reproducible native DSH compatibility experiment using real DeepSeek Harness artifacts.
• Documented supported source formats, security boundaries, compatibility classes, and experiment execution.
• Added detailed JSON and Markdown evidence for directly adaptable, partial, incompatible, malformed, and adversarial plugin scenarios.