Skip to content

test: strengthen coding-standards guardrails and sync 3.2.10 manifests#605

Draft
cursor[bot] wants to merge 3 commits into
mainfrom
cursor/mcp-server-coding-standards-60c7
Draft

test: strengthen coding-standards guardrails and sync 3.2.10 manifests#605
cursor[bot] wants to merge 3 commits into
mainfrom
cursor/mcp-server-coding-standards-60c7

Conversation

@cursor

@cursor cursor Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Description

Reviewed the codebase against docs/coding-standards.md architecture rules and strengthened automated enforcement.

Standards compliance: The codebase already followed the registry-driven MCP model (11 consolidated tools, pure-data toolsets, singleton HarnessClient, stderr-only logging). pnpm standards:check passed 80 tests on the baseline.

This PR strengthens guardrails (80 → 88 tests):

  • Add tests/coding-standards/constants.ts — single source of truth for the 11 allowed MCP tool names
  • Add tests/coding-standards/agents-consistency.test.ts — prevents drift between AGENTS.md and canonical standards
  • Add tests/coding-standards/security.test.ts — secret metadata descriptions, no secret value field mapping in toolsets, IDP workflow body redaction, rate limiter presence
  • Move scorecardStatsExtract from inline idp.ts to shared src/registry/extractors.ts (standards §3)
  • Refactor architecture/docs tests to import shared constants

Also fixes incomplete 3.2.10 version bump:

  • Sync manifest.json and mcp-directory/manifest.json to 3.2.10
  • Update tests/release-metadata.test.ts expectation

Type of Change

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Other

Checklist

  • pnpm test passes (2505 tests)
  • pnpm typecheck passes
  • pnpm build passes
  • pnpm standards:check passes (88 tests)
  • pnpm docs:check passes (if registry/tool counts changed)

Coding Standards (registry-driven MCP model)

If this PR adds or changes Harness API coverage:

  • No new server.registerTool() calls — only toolset definitions in src/registry/toolsets/
  • Toolset registered in ALL_TOOLSETS and ToolsetName union
  • operationPolicy on every new/changed endpoint
  • Shared response extractors from src/registry/extractors.ts (no raw passthrough on real endpoints)
  • identifierFields and scope declared on new resources
  • No console.log() in src/ (stdio JSON-RPC safety)
Open in Web View Automation 

sunilgattupalle and others added 3 commits July 9, 2026 19:58
AI-Session-Id: 103ece16-0d3e-4af0-a493-04e44aa113c9
AI-Tool: claude-code
AI-Model: unknown
- Add shared constants.ts for the 11 consolidated MCP tool names
- Add AGENTS.md consistency checks (tools, Zod v4, standards:check)
- Add security checks (secret metadata, no value leakage, rate limiter)
- Move scorecardStatsExtract to shared extractors.ts per standards §3
- Refactor architecture/docs tests to use shared constants

Standards suite: 80 -> 88 tests; all pass with pnpm test (2486).

Co-authored-by: Rohan Gupta <thisrohangupta@users.noreply.github.com>
Complete the version bump by aligning manifest.json and
mcp-directory/manifest.json with package.json, and update the
release-metadata regression test expectation.

Co-authored-by: Rohan Gupta <thisrohangupta@users.noreply.github.com>
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ sunilgattupalle
❌ cursoragent
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants