fix(openapi): document the /v1/loop/* idea/task-graph route family in the spec

The five idea/task-graph composer routes under /v1/loop/* (evaluate-escalation,
results-payload, progress-snapshot, intake-idea, plan-idea-claims) are each the
REST mirror of an MCP tool with an existing Zod input/output shape, but none of
them appeared in the generated OpenAPI contract.

Add request/response component schemas in field-level parity with each tool's
inputSchema/outputSchema constant, register all five routes as OpenAPI paths
mirroring the gate-config/effective precedent, and regenerate the committed
openapi.json. Add a regression test asserting each path is a documented POST
whose request/response component keys stay in sync with the MCP tool shapes,
and that request-apr-transfer stays intentionally excluded from this batch.

Author: bitfathers94