chore: coding standards compliance review and test coverage

[cursor]

Description

Audited the codebase against docs/coding-standards.md and verified all automated guardrails pass on latest main.

This PR also rebases and extends the test coverage from #836, with one fix after main landed native FME rollout status support (#838):

• Governance: multi-scope CRUD dispatch tests for policy / policy_set (resource_scope account/org/project)
• Infrastructure: bodyBuilder yaml synthesis and environment Infrastructure-section deep links
• FME rollout prompt: prompt registration, dual-mode scope validation, legacy vs Harness-native interpolation
• Prompt cleanup: removed dead nativeModeCaveat from feature-flag-rollout (computed but never appended; obsolete after feat: wire native FME traffic type and rollout status lists #838)

Standards review summary

Rule	Status
11 consolidated MCP tools only (registerTool, no new handlers)	✅ enforced by architecture.test.ts
Pure-data toolsets (no HarnessClient/Registry/logger)	✅
stderr-only logging (no console.log in src/)	✅
Singleton HarnessClient in src/index.ts	✅
Shared response extractors	✅
Scope injection via registry (no manual scope queryParams)	✅
Zod v4 + .describe() on tool inputs	✅
Write tools require elicitation / confirm	✅
operationPolicy on every endpoint	✅

Note: Automation snapshots referencing "10 tools", Zod v3, or server.tool() are outdated. Canonical source is docs/coding-standards.md (11 tools incl. harness_schema, Zod v4, registerTool()).

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other — standards compliance audit + test coverage

Checklist

• pnpm test passes (3105 tests)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes (77 tests)
• pnpm docs:check not required (no registry/tool count changes)

Coding Standards (registry-driven MCP model)

• No new server.registerTool() calls
• No toolset or handler architecture changes beyond prompt dead-code removal

  

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