fix: relax TestTimeoutKillsTask threshold for Windows CI

docs/changelog.md

@@ -4,6 +4,14 @@ All notable changes to `wf` are documented here. This project follows [Semantic
 
 ---
 
+## Unreleased
+
+### Fixed
+- `gofmt` import ordering after org rename (`parser.go`, `store.go`)
+- `TestTimeoutKillsTask` flaky on Windows CI — relaxed timeout threshold from 5s to 15s
+
+---
+
 ## [0.2.0] — 2026-03-13
 
 Expands `wf` from a basic sequential workflow runner into a full infrastructure automation runtime. The execution engine, storage layer, and DAG model were substantially redesigned. Six new CLI commands, three execution modes, and a formal security model were added. The logger and config subsystems were refactored.

tests/integration/scenarios_test.go

@@ -528,9 +528,11 @@ retries = 0
 	if err == nil {
 		t.Fatal("expected timeout error, got nil")
 	}
-	// Must abort well under 5 seconds (not wait the full 30 s).
-	if elapsed > 5*time.Second {
-		t.Errorf("task did not time out promptly: elapsed %v (expected < 5s)", elapsed)
+	// Must abort well under 15 seconds (not wait the full 30 s).
+	// Windows CI runners are slower at process group teardown, so we allow
+	// a generous margin while still catching a "waited the full 30 s" bug.
+	if elapsed > 15*time.Second {
+		t.Errorf("task did not time out promptly: elapsed %v (expected < 15s)", elapsed)
 	}
 }