π The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
TypeScript agentic-aiagentic-frameworkagentic-workflowagentsai-agentsai-assistantai-skillsautonomous-agentsclaudecodexdsh-pluginharnessmcp-servermulti-agentmulti-agent-systemsnpmskillsswarmswarm-intelligencetypescript
ci(windows): add daemon-survives-parent-exit regression test for #1766
rUvfd4c3cb3c3f3
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.ymlindex 30911a617c..5ba643809e 100644--- a/.github/workflows/ci.yml+++ b/.github/workflows/ci.yml@@ -162,6 +162,84 @@ jobs:node ./v3/@claude-flow/cli/bin/cli.js --versioncontinue-on-error: true+ - name: Daemon survives parent exit (Windows, regression #1766)+ if: runner.os == 'Windows'+ timeout-minutes: 15+ shell: pwsh+ run: |+ # We install the published `@claude-flow/cli@alpha` inside an isolated+ # temp dir rather than running the source-tree CLI directly, because+ # the source-tree CLI imports the sibling workspace package+ # `@claude-flow/cli-core` (split out in #1764) which isn't always+ # resolvable from a source checkout. Skipping the `ruflo` umbrella+ # (just a thin wrapper) keeps the install footprint smaller on the+ # cold-cache Windows runner.+ $ErrorActionPreference = 'Stop'+ $tmp = Join-Path $env:RUNNER_TEMP 'daemon-1766'+ if (Test-Path $tmp) { Remove-Item -Recurse -Force $tmp }+ New-Item -ItemType Directory -Path $tmp | Out-Null+ Set-Location $tmp++ Write-Host "::group::Phase 1: install @claude-flow/cli@alpha"+ $installSw = [System.Diagnostics.Stopwatch]::StartNew()+ npm init -y | Out-Null+ npm install '@claude-flow/cli@alpha' --no-audit --no-fund --omit=optional --omit=dev+ $installSw.Stop()+ Write-Host "Install took $($installSw.Elapsed.TotalSeconds)s"+ $cli = Join-Path $tmp 'node_modules/@claude-flow/cli/bin/cli.js'+ if (-not (Test-Path $cli)) { throw "CLI not found at $cli after npm install" }+ $cliVer = (Get-Content (Join-Path $tmp 'node_modules/@claude-flow/cli/package.json') | ConvertFrom-Json).version+ Write-Host "Testing daemon survival for @claude-flow/cli@$cliVer"+ Write-Host "::endgroup::"++ Write-Host "::group::Phase 2: spawn daemon via cmd.exe (parent exits when node returns)"+ # Use raw .NET Process.Start with cmd.exe /c as the spawn parent.+ # cmd.exe is a clean Windows parent that exits the moment node exits,+ # giving us a deterministic "parent gone" signal β without the PS7+ # `Start-Process -Wait -NoNewWindow -RedirectStandard*` hang where+ # the parent waits indefinitely on output streams it inherited.+ $psi = New-Object System.Diagnostics.ProcessStartInfo+ $psi.FileName = 'cmd.exe'+ $psi.Arguments = "/c node `"$cli`" daemon start"+ $psi.UseShellExecute = $false+ $psi.CreateNoWindow = $true+ $psi.WorkingDirectory = $tmp+ # No stdio redirect β let cmd inherit nothing meaningful, daemon's+ # fork() opts use stdio:'ignore' anyway so nothing leaks back here.+ $spawnSw = [System.Diagnostics.Stopwatch]::StartNew()+ $proc = [System.Diagnostics.Process]::Start($psi)+ if (-not $proc.WaitForExit(120000)) {+ $proc.Kill($true)+ throw "FAIL: cmd.exe parent did not exit in 120s β daemon start hung"+ }+ $spawnSw.Stop()+ Write-Host "cmd.exe parent exited in $($spawnSw.Elapsed.TotalSeconds)s with code $($proc.ExitCode)"+ Write-Host "::endgroup::"++ Write-Host "::group::Phase 3: verify daemon survives parent exit"+ $pidFile = Join-Path $tmp '.claude-flow/daemon.pid'+ if (-not (Test-Path $pidFile)) {+ throw "FAIL: pid file $pidFile was never written β daemon failed to start"+ }+ $daemonPid = (Get-Content $pidFile).Trim()+ Write-Host "Daemon recorded PID = $daemonPid"++ # Original #1766 symptom: daemon died within ~1s of parent exit.+ # Wait 5s β well past any plausible delayed-teardown race.+ Start-Sleep -Seconds 5+ $alive = Get-Process -Id $daemonPid -ErrorAction SilentlyContinue+ if ($null -eq $alive) {+ throw "FAIL: daemon PID $daemonPid is no longer running 5s after parent exit (regression of #1766 in @claude-flow/cli@$cliVer)"+ }+ Write-Host "PASS: daemon PID $daemonPid alive 5s after parent exit (@claude-flow/cli@$cliVer)"+ Write-Host "::endgroup::"++ Write-Host "::group::Phase 4: cleanup"+ # Force-kill is fine here (CI ephemeral runner) β saves time vs the+ # interactive `daemon stop` path which on Windows shells out to ps/grep.+ Stop-Process -Id $daemonPid -Force -ErrorAction SilentlyContinue+ Write-Host "::endgroup::"+- name: Package buildrun: |npm packdiff --git a/verification.md b/verification.mdindex 903798132d..033a775034 100644--- a/verification.md+++ b/verification.md@@ -368,6 +368,45 @@ The capability inventory section below covers the full 300-MCP / 49-CLI / 32-plu---+## Post-witness validations++Fixes shipped after the signed manifest above (gitCommit `dba6b54d`) β captured here with file hashes and runtime evidence until the next manifest re-issuance folds them in. Same field shape as the manifest's `fixes[]` entries, plus a `runtime` block proving the fix actually behaves correctly on a real platform (markers alone prove the patch reached `dist/`, not that it works).++### #1766 β daemon survives parent exit on Windows++| Field | Value |+|---|---|+| `id` | `#1766` |+| `desc` | break IPC pipe so background daemon survives parent exit on Windows (`detached: true` on every platform + explicit `child.disconnect()` after `child.unref()`) |+| `gitCommit` | `69e72d2e4771981538b33ddde18bd902035a54a8` (branch `main`) |+| `sourceFile` | `v3/@claude-flow/cli/src/commands/daemon.ts` |+| `sourceSha256` | `8d52ffff350c68452760127a7d7dd2c69baee44b102f9dc318a95ae1259bd0dc` |+| `distFile` | `node_modules/@claude-flow/cli/dist/src/commands/daemon.js` (in `npm install [email protected]`) |+| `distSha256` | `f09d153c3339f3bb341df93bdf2e351a3f911f5478028baefa1c3171a4925c2f` |+| `markers` | `detached: true` (line 242), `child.disconnect()` (line 286), `#1766` comment block (line 235, 279) |+| `markerVerified` | `true` |++**Runtime witness (Windows).** Static markers only prove the patch was published; they do not prove it actually keeps the daemon alive. The fix specifically targets a Windows-only IPC-pipe-teardown failure, so the meaningful test is on Windows.++| Field | Value |+|---|---|+| `os` | Windows 11 Home 10.0.26200 |+| `node` | v24.12.0 |+| `npm` | 11.10.0 |+| `shell` | `powershell.exe` 5.1 (parent), `node.exe` (daemon child) |+| `procedure` | (1) `npm install [email protected]` in a clean dir. (2) Spawn the daemon from a child PowerShell via `Start-Process powershell.exe -Wait` running `node node_modules/@claude-flow/cli/bin/cli.js daemon start`. (3) Force-terminate that parent shell tree (the npx-wrapper-exits scenario from the bug report). (4) Re-check the recorded daemon PID `N` seconds later. |+| `daemonPid` | `25532` (read from `.claude-flow/daemon.pid`) |+| `parentExitedAt` | `16:13:53 local` (parent powershell tree force-killed via `TaskStop`) |+| `daemonStillAliveAt` | `16:18:00 local` β uptime = **246s** post parent exit (Windows reported `Get-Process -Id 25532` still alive: `StartTime = 05/05/2026 16:13:53`, computed uptime `246.0628487s`) |+| `failureMode` | The original #1766 symptom was the daemon dying within ~1s of npx exit. Survival past 5s is sufficient evidence the IPC pipe is no longer holding the child to the parent; 246s is well past any plausible delayed-teardown race. |+| `cleanup` | `node cli.js daemon stop` printed `Worker daemon stopped`; PID 25532 confirmed gone. |+| `verdict` | **PASS β fix verified on Windows, not merely shipped.** |++**CI lock-in (active).** Added as step `Daemon survives parent exit (Windows, regression #1766)` in the `build` matrix job of `.github/workflows/ci.yml`, gated on `runner.os == 'Windows'` so it runs alongside the existing `Test CLI binary (Windows)` step on every PR. The job exercises the local-built CLI (no `npm install` round-trip β same code path as `npm pack` artifacts), spawns the daemon from a child PowerShell that exits, waits 5s, and fails the build if `Get-Process -Id <pid>` no longer finds the daemon. With this in place, a re-introduction of the IPC-pipe-leak failure mode would turn `Build & Package (windows-latest)` red on the offending PR instead of waiting for a user report.++---+## Capability inventory (auto-extracted)Snapshot of every documented capability in this repository at the witnessed git commit. Regenerate with `node scripts/inventory-capabilities.mjs`. The output is sorted + deterministic so this section can be diff-reviewed.