fix(daemon): let the daemon exit while a detached lease is outstanding

[V3RON]

Replaces #85, rebased directly onto main instead of the owned-device-roots stack — this defect predates that work and is unrelated to it.

The defect

simlock daemon stop returns promptly and the process stays alive. The operator is left with a stopped daemon still holding its socket, and whatever restarts it finds the address in use.

LeaseEngine.dispose — the hook DaemonServer#stop invokes — cancelled the quarantine coordinator's timers and not the expiry scheduler's:

/** Cancels the quarantine coordinator's armed retry timers on daemon shutdown. */
dispose(): void {
  this.#quarantine.dispose();
}

A lease's TTL is a real setTimeout, so an outstanding lease kept Node's event loop alive for as long as its deadline had left — fifteen minutes by default for a detached one. LeaseExpiryScheduler.dispose() existed and was never called from production code.

Held leases hid it: shutdown releases them, and releasing cancels the timer. Detached leases are deliberately left alone, since their liveness is the TTL rather than a connection, so they were the only ones left armed.

Why the fix is safe

Cancelling expires nothing early and loses nothing: ttlDeadline is persisted with the lease and re-armed by LeaseExpiryScheduler.restore on the next start. That is the same mechanism that lets a detached lease outlive a restart in the first place, which is the property that had to be preserved — the fix must not become "release everything on shutdown".

Not part of the owned-device-roots stack

It reproduces on main, with none of that stack applied. #85 carried it as the sixth of six stacked PRs and additionally picked up unrelated review fixes from #84 along the way, which drew a request to split this fix out and land it directly on main. This PR is that split: only LeaseEngine.dispose and its tests, cherry-picked from #85's 08abd5de53. The comment-only hunk in e2e/lease-environment-passthrough.test.ts is dropped here since that file doesn't exist on main yet — it's introduced by #83.

Verification

The unit test fails against the old code: removing this.#expiry.dispose() gives expected 1 to be +0, an armed timer surviving disposal. Coverage is in two places:

• a unit test asserting no timer survives disposal and that the lease itself is untouched, since cancelling a timer must not expire a lease;
• an e2e case in daemon lifecycle & recovery that leases detached, stops the daemon, and lets teardown's stray-process check be the assertion.

pnpm run check green: typecheck, typecheck:e2e, lint, format, 995 unit tests, e2e 35 passed / 1 expected fail / 9 skipped. fallow audit clean across 3 changed files.

🤖 Generated with Claude Code

https://claude.ai/code/session_015ia6AUpUzuF7aL3Z4CKUCx

---

Generated by Claude Code