docs: strengthen coding-standards compliance guardrails

[cursor]

Description

Audited the codebase against docs/coding-standards.md (the canonical registry-driven MCP architecture rules). All 79 pnpm standards:check tests and 3090 unit tests pass on current main.

This PR adds two small guardrails to prevent documentation drift from the enforced model:

• README Development section now documents pnpm standards:check alongside other dev commands
• docs-consistency.test.ts now verifies registerTool() wording (not deprecated server.tool()) and that CONTRIBUTING.md cross-references coding standards

Type of Change

• Documentation

Checklist

• pnpm test passes (3090 tests)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes (79 tests)
• pnpm docs:check not required (no registry count changes)

Coding Standards Review Summary

The pasted automation snapshot references 10 tools, Zod v3, and server.tool() — all outdated. The authoritative source is docs/coding-standards.md + AGENTS.md:

Rule	Status
11 consolidated tools (harness_schema included)	✅ Enforced
Pure-data toolsets (no HarnessClient/Registry/logger)	✅ Enforced
Shared response extractors	✅ Enforced (legacy inline extractors grandfathered)
Scope injection via registry	✅ Enforced
identifierFields + operationPolicy on endpoints	✅ Enforced
Error handling (errorResult / toMcpError)	✅ Enforced
No console.log() in src/	✅ Enforced
Zod v4 + .describe() on tool params	✅ Enforced
Write confirmation via elicitation	✅ Enforced
Singleton HarnessClient	✅ Enforced
CI runs pnpm standards:check on every PR	✅ .github/workflows/ci.yml

  

[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.}