Summary

Fix documentation to use correct YAML field naming conventions.

@jhrozek identified this issue on this PR #3006.

Problem

The composite tools documentation was using incorrect YAML field names that didn't match the actual API implementations. This caused confusion because:

1. type: tool_call was used in docs, but the actual valid value is type: tool (per WorkflowStep.Type enum in the CRD)

2. on_error: (snake_case) was used in Kubernetes CRD examples, but the actual JSON field name is onError: (camelCase)

Root Cause

ToolHive has two different configuration formats with different yaml conventions.

Example: CRD vs rawConfig

Documentation examples were inconsistently mixing these conventions, particularly in docs/operator/ which documents the Kubernetes CRDs but was using snake_case field names from the CLI format.

In the long term, we should simplify are configuration system, but in the meantime make the docs reflect reality.

Changes

docs/operator/virtualmcpcompositetooldefinition-guide.md

• Fixed type: tool_call → type: tool
• Fixed section heading #### tool_call (Phase 1) → #### tool (Phase 1)
• Fixed validation text to reference tool instead of tool_call

docs/operator/composite-tools-quick-reference.md

• Fixed on_error: → onError:

docs/operator/advanced-workflow-patterns.md

• Fixed on_error: → onError:

docs/proposals/THV-2106-virtual-mcp-server.md

• Fixed on_error: → onError: - in K8s CRD section only