Feat: Add GlobalCheck Compliance Integration to Agent Configuration

[sh8kme]

This PR introduces a new --enable-globalcheck flag to the install.sh script, providing a seamless path to integrate GlobalCheck compliance and moderation capabilities for all agents configured by codebase-memory-mcp.

GlobalCheck serves as a critical agentic proxy (MCP) for AI models, enabling real-time enforcement of usage policies, content moderation, data governance, and cost controls. By integrating GlobalCheck, developers can:

• Ensure AI Safety & Compliance: Deploy agents with confidence, knowing their interactions adhere to organizational policies and regulatory requirements from day one.
• Implement Robust Guardrails: Proactively prevent unwanted or insecure behaviors by routing agent LLM calls through a compliance layer.
• Simplify Agent Management: Leverage codebase-memory-mcp as a central hub for configuring not just code intelligence but also essential governance over your AI agents.

This change is designed to be minimal and fully leverage codebase-memory-mcp's existing agent configuration mechanism. When --enable-globalcheck is specified during installation, the codebase-memory-mcp binary's install command will receive this flag, allowing it to automatically configure the supported coding agents to route their LLM requests through the GlobalCheck agentic proxy (e.g., via environment variables or direct client modifications).

This prepares codebase-memory-mcp to offer an even more robust and production-ready environment for AI agent development, addressing crucial aspects of trust and responsible AI deployment.

[DeusData]

Thanks for the contribution. We are closing this because codebase-memory-mcp is intentionally a local-only binary. The proposed GlobalCheck integration adds third-party service configuration and an API-key surface to the install flow; external SaaS or commercial integrations are outside the project scope. We will not add or forward third-party credentials from the installer. The DCO check is also failing, but the product-boundary mismatch alone is decisive here.