squad-station 0.5.5 โ 0.5.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +42 -0
- package/bin/run.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,48 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to Squad Station are documented in this file.
|
|
4
4
|
|
|
5
|
+
## v0.5.8 - 2026-03-20
|
|
6
|
+
|
|
7
|
+
### ๐ Bug Fixes
|
|
8
|
+
|
|
9
|
+
- Fixed `current_task` corruption when `/clear` is sent while another task is already processing โ `current_task` now reverts to the real task instead of staying pointed at the completed `/clear` message
|
|
10
|
+
|
|
11
|
+
### ๐งช Tests
|
|
12
|
+
|
|
13
|
+
- Added `test_fire_and_forget_clear_while_task_processing` integration test โ verifies `current_task` and agent status are correct when fire-and-forget overlaps with an in-flight task
|
|
14
|
+
|
|
15
|
+
## v0.5.7 - 2026-03-20
|
|
16
|
+
|
|
17
|
+
### ๐ Bug Fixes
|
|
18
|
+
|
|
19
|
+
- Fixed signal race condition: `/clear` followed by a real task no longer leaves the real task stuck at `processing` forever
|
|
20
|
+
- Root cause: `/clear` in Claude Code produces no response turn, so the Stop hook never fires โ its DB message blocked the FIFO signal queue, causing subsequent signals to complete the wrong task
|
|
21
|
+
- Fire-and-forget commands (e.g. `/clear`, `/clear hard`) are now auto-completed at send time in `send.rs`
|
|
22
|
+
- Agent status correctly resets to idle after fire-and-forget if no other tasks are queued
|
|
23
|
+
|
|
24
|
+
### ๐งช Tests
|
|
25
|
+
|
|
26
|
+
- Added `is_fire_and_forget` unit tests (positive + negative cases)
|
|
27
|
+
- Added `test_fire_and_forget_clear_auto_completed` integration test โ reproduces the exact race condition and verifies signal targets the correct task
|
|
28
|
+
|
|
29
|
+
## v0.5.6 - 2026-03-20
|
|
30
|
+
|
|
31
|
+
### ๐ Highlights
|
|
32
|
+
|
|
33
|
+
- `/clear` context management upgraded from vague guidance to **hard rules** โ weaker models (Haiku) no longer ignore `/clear` decisions
|
|
34
|
+
|
|
35
|
+
### ๐ Features
|
|
36
|
+
|
|
37
|
+
- Mandatory `/clear` triggers: topic shift, 3-task threshold, agent hint detection
|
|
38
|
+
- Pre-send checklist added to orchestrator playbook โ run before every `squad-station send`
|
|
39
|
+
- Explicit `How to /clear` section with code example
|
|
40
|
+
- QA Gate step 5 now says "Run the `/clear` checklist" instead of "Decide if `/clear` is needed"
|
|
41
|
+
|
|
42
|
+
### ๐ง Maintenance
|
|
43
|
+
|
|
44
|
+
- Version bumped to 0.5.6 across Cargo.toml, npm-package/package.json, and bin/run.js binary download
|
|
45
|
+
- npm binary download version aligned to 0.5.6 (was stuck at 0.5.3)
|
|
46
|
+
|
|
5
47
|
## v0.5.5 - 2026-03-19
|
|
6
48
|
|
|
7
49
|
### ๐ Highlights
|
package/bin/run.js
CHANGED
|
@@ -43,7 +43,7 @@ function install() {
|
|
|
43
43
|
|
|
44
44
|
function installBinary() {
|
|
45
45
|
// Binary version โ may differ from npm package version
|
|
46
|
-
var VERSION = '0.5.
|
|
46
|
+
var VERSION = '0.5.8';
|
|
47
47
|
var REPO = 'thientranhung/squad-station';
|
|
48
48
|
|
|
49
49
|
var platformMap = { darwin: 'darwin', linux: 'linux' };
|