Backfill required MCP form and field operations

[S4Mi]

Summary

• backfill MCP-required form and field operations that are missing from the mcp-1.0 source bundle using the v3.0 formz bundle during MCP artifact generation
• add MCP metadata/examples for form delete, single-field read/create/delete, and keep joint form-and-fields endpoints as the primary form authoring path
• extend MCP spec validation so these core operations cannot silently disappear from openapi-v3.0.mcp.yaml

Why

The MCP server policy requires these operation IDs to exist in the MCP OpenAPI artifact. The hosted mcp-1.0 source currently omits some of them, so FormalooMCP had to treat the local spec as safer than the hosted MCP artifact.

This PR fixes the generated docs side while preserving the intended API order: agents should start with composed MCP form tools or the joint form-and-fields endpoints (formFieldsRetrieve / formFieldsPartialUpdate) for normal form authoring. Single-field endpoints are still valid for targeted one-field reads, adds, or deletes, but they are not documented as the first/default route for multi-field form construction or coordinated updates.

Validation

• ./generate.sh
• npm run validate:mcp-spec
• verified generated openapi-v3.0.mcp.yaml contains formsDestroy, fieldsRetrieve, fieldsCreate, and fieldsDestroy
• verified the generated single-field descriptions steer form authoring, ordering, logic-aware edits, and coordinated updates to the joint form-and-fields flow first
• cross-checked generated MCP operation IDs against FormalooMCP operation-policy.json: no missing policy operations