Merge pull request 'release: v0.1.2 — session resume fix' (#153) from release/session-resume-fix into main

Reviewed-on: #153
Reviewed-by: scottwei <shazhou.ww@gmail.com>

.changeset/fix-session-resume-frontmatter.md

@@ -1,9 +0,0 @@
----
-"@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.

packages/agent-claude-code/CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+## 0.1.4 — 2026-06-07
+
+- 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.
+

packages/agent-hermes/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @united-workforce/agent-hermes
 
+## 0.1.5 — 2026-06-07
+
+- 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.
+
 ## 0.1.1
 
 ### Patch Changes

packages/util-agent/CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+## 0.1.2 — 2026-06-07
+
+- 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.
+