test: cover PR #398 Zod descriptions and entity schema cache keys

[cursor]

Summary

Adds regression tests for recently merged production changes where missing coverage carried meaningful business risk.

Risky behavior now covered

PR #398 — Zod 4 input schema descriptions

• Risk: In Zod 4, calling .describe() before .optional() / .default() strips field descriptions from the MCP tool surface, breaking LLM tool selection for pagination, scope, and filter fields.
• Coverage: Runtime assertions on all 7 affected tool handlers (harness_list, harness_search, harness_status, harness_describe, harness_diagnose, harness_get, harness_schema) plus static architecture guard in architecture.test.ts.

PR #396 — Live entity schema cache isolation by scope

• Risk: A shared cache key across org/project scopes could serve the wrong YAML schema for a different org or project.
• Coverage:
  • buildLiveSchemaCacheKey unit tests for account/org/project differentiation
  • bundledSnapshotMatchesScope rejects mismatched org/project against vendored meta
  • preloadBundledEntitySchemas warms cache with scope-aware keys from vendored meta (not account-only keys)
  • harness_schema integration tests proving separate cache entries for org and project scope identifiers

Test files added/updated

File	What it guards
tests/tools/zod-input-schema-descriptions.test.ts	MCP field descriptions survive Zod 4 chaining on all 7 tool handlers
tests/tools/entity-schema-cache-keys.test.ts	Cache key format, bundled scope matching, preload warming
tests/tools/entity-schema-bundled.test.ts	Bundled-first path, project scope validation, cross-org/project rejection
tests/tools/harness-schema-tool.test.ts	End-to-end org/project cache isolation via harness_schema
tests/coding-standards/architecture.test.ts	Static Zod describe-chain-order enforcement

Why this reduces regression risk

• LLM tool selection: Description loss is silent at compile time; runtime schema inspection catches it before agents lose field hints.
• Wrong-schema serving: Scope cache collisions would cause agents to author YAML against the wrong org/project schema — high blast radius for create/update flows.
• Startup cache warming: preloadBundledEntitySchemas was changed to use scoped keys; without tests, a revert to account-only keys would reintroduce the collision bug at process start.

Validation

pnpm test  # 2204 passed

  

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