feat: add automated coding standards enforcement

[cursor]

Summary

Adds automated enforcement of the registry-driven MCP server architecture rules documented in docs/coding-standards.md.

Changes

• scripts/check-standards.js — CI script that blocks architectural anti-patterns:

  • No console.log() in src/
  • registerTool() only in the 11 consolidated harness-*.ts handlers
  • No unexpected files under src/tools/
  • fetch() only in allowlisted paths (HarnessClient, log-resolver, webhooks, entity-schema)
  • HarnessClient singleton in src/index.ts only
  • Toolsets must not import HarnessClient, McpServer, or Registry
  • Toolsets must not use console.*
  • ToolsetName union ↔ toolset files ↔ ALL_TOOLSETS stay in sync

• tests/coding-standards.test.ts — Vitest mirror of key checks plus integration with the script

• pnpm standards:check — New npm script; wired into CI workflow

• Fixes for existing violations:

  • ccm.ts / sto.ts: remove HarnessClient imports; use HarnessClientInterface via PreflightContext
  • idp.ts: replace console.error with createLogger
  • types.ts: extend HarnessClientInterface with request() and getCurrentUserId(); add knowledge-graph and semantic-layer to ToolsetName

Verification

pnpm build && pnpm typecheck && pnpm standards:check && pnpm test

All 2118 tests pass.

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}