shazhou/united-workforce
8
0
Fork 0
Code Issues 8 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

release: v0.1.2

Browse Source
This commit is contained in:
小橘
2026-06-07 15:44:00 +08:00
parent 81aa282c92
commit ccfd13158e
4 changed files with 22 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/fix-session-resume-frontmatter.md
-9
View File
@@ -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
+8
View File
@@ -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
+6
View File
@@ -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
+8
View File
@@ -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.