v0.4.23 — Each Checkout Its Own Sink

Sessions on one machine no longer take each other's fleet events. Before this, every session launched from one user-level harness configuration shared one event sink, and the first stop hook to run took everyone's events. Each checkout now has its own sink. Events already waiting in the old shared sink are not delivered after upgrading. A seat that names --project keeps its sink as it was.

What's fixed

• Give each checkout its own fleet-event sink, so sessions on one machine stop taking each other's events #303