From aeb7180e9dca53672bd20e6ee6cd7007c25902b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=B0=8F=E6=A9=98?= Date: Fri, 22 May 2026 11:22:34 +0000 Subject: [PATCH] =?UTF-8?q?chore:=20fix=20meta.plan=20=E2=86=92=20frontmat?= =?UTF-8?q?ter.plan=20in=20workflow=20procedures?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 小橘 --- .workflows/solve-issue.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.workflows/solve-issue.yaml b/.workflows/solve-issue.yaml index 3eaa4a6..6f9297b 100644 --- a/.workflows/solve-issue.yaml +++ b/.workflows/solve-issue.yaml @@ -44,7 +44,7 @@ roles: - If bounced back from reviewer or tester, reuse the existing branch instead Then implement TDD: - 3. Read the test spec from CAS: `uwf cas get ` (find the hash from the latest planner step's meta.plan) + 3. Read the test spec from CAS: `uwf cas get ` (find the hash from the latest planner step's frontmatter.plan) 4. If bounced back from reviewer or tester: read the previous role's output to understand what needs fixing 5. Write tests first based on the spec 6. Implement the code to make tests pass @@ -99,7 +99,7 @@ roles: - testing procedure: | 1. Run `bun test` for automated test verification - 2. Read the test spec from CAS: `uwf cas get ` (find the hash from the latest planner step's meta.plan) + 2. Read the test spec from CAS: `uwf cas get ` (find the hash from the latest planner step's frontmatter.plan) 3. Verify each scenario in the spec is covered and passing 4. Determine outcome: - passed: all scenarios verified, tests pass