From 13c08129446e9a792816a845508ca9e51881d7a8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=B0=8F=E6=A9=98?= Date: Sun, 7 Jun 2026 03:03:55 +0000 Subject: [PATCH] chore: add changeset for session resume fix (#139) --- .changeset/fix-session-resume-frontmatter.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 .changeset/fix-session-resume-frontmatter.md diff --git a/.changeset/fix-session-resume-frontmatter.md b/.changeset/fix-session-resume-frontmatter.md new file mode 100644 index 0000000..a40b5dc --- /dev/null +++ b/.changeset/fix-session-resume-frontmatter.md @@ -0,0 +1,9 @@ +--- +"@united-workforce/util-agent": patch +"@united-workforce/agent-claude-code": patch +"@united-workforce/agent-hermes": patch +--- + +fix: decouple session resume from isFirstVisit guard + +When frontmatter validation fails, the step is never written to CAS, so isFirstVisit remains true on the next run. Both adapters now always check the session cache regardless of isFirstVisit. When resuming after a frontmatter-only failure (isFirstVisit + cache hit), a minimal correction prompt is sent via buildFrontmatterRetryPrompt() instead of re-sending the full initial prompt. -- 2.43.0