feat: sin forge — Integrate SIN-Code-Forge-Tool (beta)

[Delqhi]

Description

Integrate SIN-Code-Forge-Tool as sin forge subcommand.

Current State

• SIN-Code-Forge-Tool exists at OpenSIN-Code/SIN-Code-Forge-Tool
• Go-based, has mcp/forge_mcp_server.py scaffold but 0 MCP tools implemented
• No pyproject.toml — can't install via pip/uv
• NOT integrated into sin CLI

Required Work

1. Add pyproject.toml with entry points
2. Implement MCP tools in mcp/forge_mcp_server.py
3. Add sin forge top-level command
4. Add to sin status detection

Acceptance Criteria

• sin forge --help works
• MCP server exposes at least 3 tools
• Installable via pip install sin-code-forge-tool
• sin status shows Forge status

Priority

MEDIUM — Tool exists but needs hardening before integration

[Delqhi]

Not addressed in v3.0.0–v3.2.0 (focus was on the agent loop, verification gate, hooks, slash commands). Remaining work for future release train.

[Delqhi]

Status (2026-06-12, post-v3.5.0)

Priority: LOW — defer; SIN-Code-Forge-Tool is beta.

Current state

• ❌ SIN-Code-Forge-Tool is referenced in ECOSYSTEM.md as beta
• ❌ Not in mcpclient/registry.go
• ❌ No CLI integration (no sin-code forge subcommand)
• ❌ No MCP exposure

What's needed to ship

• Decide: is Forge a CLI tool, an MCP server, or both?
• Add to registry.go with consistent prefix
• Add permission_defaults.go rule
• Document in ECOSYSTEM.md with stable ACTIVE status
• Or: keep beta status, document integration path

Cross-refs

• ECOSYSTEM.md (Forge row, beta state)
• Sister-issue: feat: sin security — Integrate SIN-Code-Security-Bundle (production ready) #36 (sin security — similar pattern)