From f6298c73bf4c41772d543ba86a78dbc6c09a7d86 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=98=9F=E6=9C=88?= Date: Tue, 2 Jun 2026 13:54:01 +0800 Subject: [PATCH] fix: add missing reason field to planner insufficient_info frontmatter The $SUSPEND edge for insufficient_info uses {{{reason}}} template variable, but the frontmatter schema was missing the reason field. This caused workflow validation to reject the workflow on thread start. Fixed in all 3 copies: .workflows/, examples/, workflows/ --- .workflows/solve-issue.yaml | 3 ++- examples/solve-issue.yaml | 3 ++- workflows/solve-issue.yaml | 3 +++ 3 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.workflows/solve-issue.yaml b/.workflows/solve-issue.yaml index 2089f07..3c23cec 100644 --- a/.workflows/solve-issue.yaml +++ b/.workflows/solve-issue.yaml @@ -40,7 +40,8 @@ roles: required: [$status, plan, repoPath, repoRemote] - properties: $status: { const: "insufficient_info" } - required: [$status] + reason: { type: string } + required: [$status, reason] developer: description: "TDD implementation per test spec" goal: "You are a developer agent. You implement code changes following TDD — write tests first, then implementation." diff --git a/examples/solve-issue.yaml b/examples/solve-issue.yaml index 6edbbce..f3ba8eb 100644 --- a/examples/solve-issue.yaml +++ b/examples/solve-issue.yaml @@ -64,7 +64,8 @@ roles: required: [$status, plan, repoPath, branch, worktree] - properties: $status: { const: "insufficient_info" } - required: [$status] + reason: { type: string } + required: [$status, reason] developer: description: "TDD implementation per test spec" goal: "You are a developer agent. You implement code changes following TDD — write tests first, then implementation." diff --git a/workflows/solve-issue.yaml b/workflows/solve-issue.yaml index 1b3b38c..08bb637 100644 --- a/workflows/solve-issue.yaml +++ b/workflows/solve-issue.yaml @@ -65,8 +65,11 @@ roles: - properties: $status: const: insufficient_info + reason: + type: string required: - $status + - reason developer: description: TDD implementation per test spec goal: You are a developer agent. You implement code changes following TDD — write tests first, then implementation.