Support function-based workflow harness template while preserving behavior

[tbrandenburg]

Motivation

• Make the harness-generation prompt contract explicit about supporting function-wrapped step implementations while ensuring safety and existing semantics are preserved.

Description

• Added a run_agent() helper contract to the WORKFLOW_TO_HARNESS_PROMPT_TEMPLATE.md to define prompt piping and CLI invocation semantics for type: agent steps.
• Added an optional catch() hook description for centralized failure logging/recovery behavior and its expected semantics.
• Documented that wrapper functions (for example step1(), step2()) are allowed provided they preserve execution order, dry-run semantics, prompt delivery, and non-zero exit status behavior.
• Updated the template guidance around step structure and behavior-preservation requirements so generated scripts remain deterministic and safe.

Testing

• Ran frontend unit tests for the harness prompt rendering with npm --prefix packages/frontend run test -- --run src/utils/workflowHarnessPrompt.test.ts and the test suite passed.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
made	Ready	Preview, Comment	Mar 14, 2026 7:39pm