feat: add Hy3 Forge developer MCP Server

[NaixuC]

Summary

Add Hy3 Forge, a local stdio MCP Server that provides an evidence-to-implementation-to-review workflow powered by Hy3.

The Server exposes three MCP tools:

• deep_research

  • Uses Hy3 web discovery to locate current documentation.
  • Safely retrieves page bodies and extracts version, section, and content evidence.
  • Returns structured research reports with source links, verbatim citations, version assumptions, conflicts, uncertainties, and research statistics.

• implement_with_constraints

  • Compiles natural-language development requests into explicit change contracts.
  • Requires user confirmation before writing project files.
  • Enforces allowed-file scope, protected paths, dependency rules, public-interface checks, syntax validation, internal API checks, and controlled repair attempts.
  • Returns operation-level diffs and per-constraint evidence.

• review_code_changes

  • Performs read-only review of real Git diffs.
  • Collects before/after code, callers, tests, and configuration context.
  • Finds bugs, regressions, compatibility issues, security risks, and test gaps with path, line, evidence, impact, minimal fixes, and test suggestions.

Installation and Documentation

• Add PowerShell scripts for installation, separate API key configuration, runtime inspection, reinstall, and uninstall.
• Keep runtime credentials in a Git-ignored local .env.
• Add Chinese and English Server READMEs.
• Add detailed Chinese and English documentation for all three tools.

Validation

• Verified all three tools through a real Codex MCP session.
  • Tool1 completed Hy3 web discovery, official page retrieval, citation binding, and evidence-backed reporting.
  • Tool2 completed natural-language request, contract review, explicit confirmation, Hy3 implementation, validation, and diff output.
  • Tool3 reviewed a real Git diff and identified a deliberately introduced forwarding regression.
• Verified MCP client connection and Server loading through Trae.
• Added unit and integration coverage for tool registration, source safety, document extraction, contract confirmation, rollback, diff review, read-only checks, and redaction.

Security Properties

• Local stdio transport only; no public service endpoint is required.
• No API key is hard-coded in source.
• Tool1 applies public-web safety checks before treating retrieved content as evidence.
• Tool2 cannot write before explicit contract confirmation.
• Tool3 remains read-only and reports Git status before and after review.
  Related to 【犀牛鸟实战issue】Build an MCP Server powered by Hy3 #3