feat: expose loop-audit and circuit breaker over MCP

[THRISHAL12345]

Summary

Exposes the loop_audit_score and loop_check_breaker tools through the Model Context Protocol (MCP) server, enabling AI agents to dynamically query a project's readiness score and circuit breaker (stagnation) status.

Changes

• New pattern or starter (followed templates/pattern-template.md and updated registry.yaml)
• Documentation / example improvement
• Tool changes (mcp-server)
• Story (includes a real failure or surprise and the lesson learned)

Checklist (from CONTRIBUTING)

• All required sections are present for patterns
• Links work from README.md, patterns/README.md, starters/README.md, and docs/index.md
• No secrets, tokens, or internal company URLs
• STATE.md examples use the .example suffix
• Safety-related content references docs/safety.md
• Ran node tools/loop-audit/dist/cli.js . (or on the starter) and addressed all findings

Testing / Dogfooding

• loop-audit passes on the affected starters or this repository
• Manually reviewed the generated state and skill output

Screenshots / Examples

loop_audit_score via MCP (JSON-RPC over stdio)

Response

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "## Loop Readiness: 100/100 (L3)\nStrong loop readiness — good candidate for L3 with explicit gates.\n\n- ✅ State file(s): STATE.md\n- ✅ Triage skill present.\n- ✅ Verifier skill present.\n- ✅ Safety documentation present.\n..."
      }
    ]
  },
  "jsonrpc": "2.0",
  "id": 2
}

---

loop_check_breaker via MCP (JSON-RPC over stdio)

Response (inactive state)

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "No loop-ledger.json found. Circuit breaker is inactive."
      }
    ]
  },
  "jsonrpc": "2.0",
  "id": 3
}