Clarify workflow harness prompt to execute bash steps as shell commands

[tbrandenburg]

Motivation

• Fix incorrect generation semantics where workflow steps with type: bash were being treated as agent prompts and invoked via the agent CLI instead of executed as shell commands.
• Ensure deterministic, safe harness scripts by explicitly mapping step types so the generator does not conflate shell commands and agent prompts.

Description

• Updated packages/frontend/src/templates/WORKFLOW_TO_HARNESS_PROMPT_TEMPLATE.md to add a bash -lc exception limited to type: bash steps and to introduce a Step Type Mapping that defines exact handling for type: bash and type: agent steps.
• Scoped prompt/stdin handling guidance so printf '%s' "$PROMPT" semantics apply only to type: agent steps and documented that type: bash must not call the configured agent CLI.
• Added assertions to packages/frontend/src/utils/workflowHarnessPrompt.test.ts to validate the new guidance appears in generated prompts.

Testing

• Ran the targeted frontend unit tests with npm --prefix packages/frontend test -- src/utils/workflowHarnessPrompt.test.ts, and the test suite passed (3 tests passed).
• Verified the changed template and tests were syntactically valid via the project test run and local file checks.

---

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 1:02pm