test: expand coding standards enforcement for registry and handler contracts

[cursor]

Summary

Expands automated architecture guardrails in tests/coding-standards/architecture.test.ts so the registry-driven MCP model stays enforced as the codebase grows.

What was already in place

• docs/coding-standards.md documents the consolidated 11-tool architecture
• pnpm standards:check runs in CI alongside build, test, typecheck, and docs:check
• Existing tests already blocked new MCP tools, forbidden toolset imports, console.log() in src/, raw fetch() in handlers/toolsets, and toolset registration drift

New enforcement (8 tests)

Registry resource contracts

• Every CRUD operation and execute action declares operationPolicy (risk + retryPolicy)
• Every resource declares identifierFields
• Resource scope / supportedScopes use only project, org, or account

Tool handler contracts

• Write handlers (create, update, delete, execute) expose a confirm param
• All 11 handlers import Zod via zod/v4
• harness_list keeps pagination defaults (page=0, size=20, max 100)
• API handlers use errorResult() + toMcpError() (local-only describe/schema exempt)

HTTP client singleton

• new HarnessClient() is only allowed in src/index.ts

Verification

pnpm standards:check  # 17 tests pass
pnpm test             # 2144 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.}