fix: enforce coding standards for Zod schemas and architecture guardrails

[cursor]

Summary

Audited the codebase against docs/coding-standards.md and strengthened automated enforcement so the registry-driven MCP architecture stays compliant in CI.

Changes

Bug fixes (Zod 4 parameter descriptions)

Fixed .describe() chain order in 7 tool handlers (harness_list, harness_get, harness_search, harness_status, harness_diagnose, harness_describe, harness_schema). In Zod 4, calling .describe() before .optional() / .default() drops descriptions from the registered MCP schema — LLMs depend on these for tool selection.

Error handling

Aligned harness_schema with the standard errorResult() / toMcpError() pattern used by other handlers.

Expanded pnpm standards:check (16 tests, up from 9)

• Singleton HTTP client — HarnessClient only instantiated in src/index.ts
• Write tool safety — create/update/delete/execute handlers call confirmViaElicitation
• Error handling — handlers import and use toMcpError for unexpected failures
• Tool input schemas — Zod v4 import convention, no describe-before-chain anti-pattern, runtime check that every registered input field exposes a description

Verification

pnpm build
pnpm typecheck
pnpm standards:check  # 16 passed
pnpm test             # 2138 passed

Checklist

• No new server.registerTool() calls
• No console.log() in src/
• Toolset files remain pure data
• All Zod params expose descriptions on registered schemas
• pnpm standards:check passes in CI

  

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