Make orchestration run input usable: object MCP schema + JSON Logic inputMapping

[arantespp]

Two related changes that together make values passed to start-orchestration-run actually usable downstream.

1. fix(server): MCP tools advertise object-typed body fields as objects

The MCP tool schema generator (soatToolsHelpers.ts) collapsed every OpenAPI object body field to type: string, because getJsonSchemaType had no object branch. So start-orchestration-run advertised input as a string and object inputs arrived as null (state: {}). The OpenAPI spec already declared input as object, so this was purely a generator bug; no spec/SDK/CLI regeneration was needed.

  if (schemaType === 'array') return 'array';
+ if (schemaType === 'object') return 'object';
  return 'string';

Benefits every object-typed body field across all REST-backed MCP tools, not just orchestration runs.

2. feat(orchestrations): evaluate inputMapping values as JSON Logic

inputMapping values were resolved only as state.<path> strings — no literals, no inline computation. Each value is now evaluated as JSON Logic against the run state, reusing the same evaluator as transform/condition nodes:

Value	Behaviour
String, number, boolean, array, multi-key object	Literal, passed as-is
{"var": "key"}	Resolved from state (state.key; missing → null)
Any other single-key object	Evaluated (cat, >, if, arithmetic, …)

"input_mapping": {
  "language": "pt-BR",
  "documentId": { "var": "temaDocumentId" },
  "label": { "cat": ["Tema: ", { "var": "titulo" }] },
  "isLong": { ">": [{ "var": "wordCount" }, 500] }
}

This makes run input directly usable: values passed via input become initial state and can be referenced with {"var": "key"} — eliminating boilerplate transform nodes.

outputMapping is intentionally unchanged (still a state.<path> write target — JSON Logic is a read-only evaluator and cannot express an assignment destination).

⚠️ Breaking change

inputMapping values are no longer state.<key> path strings. A bare string is now a literal; use {"var": "key"} to read from state. The orchestrate-a-sonnet tutorial, module docs, smoke tests, and affected unit tests are migrated.

Tests (red/green TDD)

• Feat files #1: getJsonSchemaType('object') and buildInputSchema object-prop tests (the red test was object → string).
• Feat files #2: rewrote the applyInputMapping unit suite for JSON Logic semantics; replaced the two obsolete resolveFromState-branch REST tests with an end-to-end test asserting literal + run-input {var} + computed expression via required_action.context; added a live-server smoke assertion.

🤖 Generated with Claude Code

[github-actions]

Deploy Outputs

Package	Stack	Output Key	Output Value
@soat/website	SoatWebsite-claude-dazzling-archimedes-wsznne	BucketWebsiteURL	http://soatwebsite-claude-dazzling-archimede-staticbucket-wcojk72qzyah.s3-website-us-east-1.amazonaws.com