[Fix #1186] Allow any type in for.in inline array

[ricardozanini]

Summary

• Removes the type: object constraint from inline array items in for.in, allowing iteration over arrays of any type (strings, numbers, booleans, objects, etc.)
• Updates the DSL reference to reflect the type change from array<object> to array
• Adds a new example (for-inline-primitive-array.yaml) demonstrating iteration over an inline array of numbers

Fixes #1186

Test plan

• All 185 schema validation tests pass
• Verify the new example validates correctly in CI

[Copilot]

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Updates the workflow schema/docs to allow for.in inline arrays to contain primitives (and other non-object values), and adds an example demonstrating primitive iteration.

Changes:

• Relax schema/workflow.yaml so inline for.in arrays no longer require items.type: object
• Update DSL reference typing for for.in from array<object> to array
• Add a new YAML example iterating over an inline numeric array

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
schema/workflow.yaml	Removes the object-only constraint for inline for.in array items
dsl-reference.md	Updates the reference typing/description to match the schema change
examples/for-inline-primitive-array.yaml	Adds a primitive-array iteration example for for.in

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cdavernas]

LGTM! Cheers ❤️