LIFECYCLE EXPERIMENTS / v0.1.9 / 2026-11-13

1,140 scripted trials. Every cleanup inside its declared bound.

We ran the published v0.1.9 binaries on native macOS arm64 and Linux x86_64: expiry, killed supervisors, an interrupted launcher with blocked output, and keyed retries. An independent observer decided each cleanup by watching the service processes and their port, not by asking ProcLease. All 570 trials on each platform passed. The total includes 1,020 product trials and 120 observer controls. These figures come from the primary series, run with the amended observer of protocol version 2. An earlier series with the first observer also passed and stays published separately. These are scripted host CLI tests, not agent sessions, and not a benchmark.

570/570MACOS ARM64 PASSED
570/570LINUX X86_64 PASSED
0FAILED, TIMED OUT OR ERRORED

01 / RESULTS

Thirty repetitions per scenario, per platform.

Each detached (default) or foreground case is counted separately. Every row passed all of its declared criteria in every repetition.

On narrow screens, scroll tables horizontally to compare both platforms.

PASSED TRIALS BY SCENARIO
ScenarioWhat passing requiredmacOSLinux
Expiry, detached and foregroundParent and same-group child are seen stopped and the port closes in the deadline window; TERM-ignoring services keep running through the 1 s grace, then stop; state expired120/120120/120
Keeper or guardian SIGKILLIdentity checked before the signal; group gone and port closed within 3.5 s; no supervisor left; state interrupted60/6060/60
Foreground SIGINT, stdout blockedSignal sent only after confirming one running job, a full pipe and the live launcher; exit 130 within 6.5 s with the pipe still unread; group gone; state interrupted30/3030/30
Sequential retry, both modesSame job and deadline, reused: true, one service start60/6060/60
8 simultaneous same-key callers, both modesOne job, one start, one creator and seven reusers60/6060/60
Changed environment, both modesOrdinary retry rejected naming environment; --reuse returns the job and the service keeps its original environment60/6060/60
Changed command, both modesRejected with and without --reuse; original job unchanged60/6060/60
Retry after expiry, both modesRetained expired record returned; service not started again; port stays closed60/6060/60
Negative controlsThe observer never reports cleanup for a live process, or without first seeing it60/6060/60

02 / TIMING

How long cleanup took after each event.

Seconds until the service parent and child were both seen absent or exited, median and maximum of 30 trials in the primary series. The observer polls every 0.05 s and up to three trials ran at once, so these describe these runs only. They are not benchmarks, and the two hosts differ in hardware, load and Python version.

SECONDS AFTER THE EVENT, MEDIAN / MAX
EventmacOSLinux
Detached expiry, default TERM0.070 / 0.1030.026 / 0.067
Detached expiry, TERM ignored (1 s grace)1.051 / 1.0991.034 / 1.056
Foreground expiry, default TERM0.076 / 0.1040.018 / 0.065
Foreground expiry, TERM ignored1.058 / 1.1121.042 / 1.057
Keeper SIGKILL, TERM ignored1.067 / 1.1041.030 / 1.084
Guardian SIGKILL, TERM ignored1.064 / 1.0951.027 / 1.079
Foreground SIGINT, stdout blocked1.155 / 1.2001.093 / 1.120

Recorded state is kept apart from observed cleanup. After a keeper SIGKILL every group was cleaned up, yet no record carried the keeper's finalization marker, because that keeper was gone. After a guardian SIGKILL, all 60 did.

03 / METHOD

Real binaries. Independent observation.

04 / LIMITS

What these trials do not show.

The first counted series used an observer that ignored ps failures and counted 21 such samples as stopped. It also passed 570 of 570 trials per platform, but it is kept as a separate, earlier dataset. The primary series repeated every trial with the amended observer.

Read the full report for artifact hashes, host conditions, every timing and the reproduction steps.