From b5f039f73f385cfc09441c8c333888860566534c Mon Sep 17 00:00:00 2001 From: Paul O'Reilly Date: Fri, 31 Jul 2026 10:44:14 +1200 Subject: [PATCH] fix(workflows): use artifacts.item_body not metadata.task_description MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit metadata.task_description is not in the consumer snapshot — the trigger consumer only populates metadata.automation from the outbox typed_payload. artifacts.item_body IS populated via dispatch_service from item_snapshot["body"] (set from typed_payload.body in the consumer, which comes from item.get("body") in emit_work_item_event). For M39 items the body contains the full task description, so ${artifacts.item_body} gives the agent complete implementation instructions. --- task-templates/workflow/airouter-impl-ready@1.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/task-templates/workflow/airouter-impl-ready@1.yaml b/task-templates/workflow/airouter-impl-ready@1.yaml index cf15c79..3da7375 100644 --- a/task-templates/workflow/airouter-impl-ready@1.yaml +++ b/task-templates/workflow/airouter-impl-ready@1.yaml @@ -28,7 +28,7 @@ nodes: You are implementing source code for the following task. ## Task Description - ${metadata.task_description} + ${artifacts.item_body} ## Instructions 1. Read the task description carefully — it specifies the file(s) to create/modify and the exact requirements.