Hypothesis
Repeated gateway and dashboard starts/stops can leak helper processes or exceed bounded shutdown latency.
Safety boundary
The harness accepts only unit names beginning with bunsen-lc-. Canonical hermes-gateway.service and bunsen-dashboard.service names are rejected in code. The production Bunsen gateway stayed active throughout the measured 25-cycle run.
Result
- 25 cycles completed.
- 0 lifecycle survivor cycles.
- 0 net Bunsen user-process growth.
- Gateway stop median 1.127 s, maximum 1.237 s.
- Dashboard stop median 0.199 s, maximum 0.232 s.
- Secret scan: PASS.
The combined lifecycle verdict is DEGRADED, not PASS: the mixed model/tool workload succeeded in 22/25 cycles, below the predeclared 24/25 criterion. The lifecycle sub-claim still passed—zero survivor cycles, no process growth, and bounded stops—but the experiment-level verdict remains degraded because all three web workloads missed the expected phrase. A dedicated follow-up got the fact in 10/10 responses and exact formatting in 9/10.
Falsifier
Fail lifecycle safety if any bunsen-lc-* process survives cleanup, the Bunsen user process count grows, or a canonical service name appears in a start/stop call.