Tracks the Chronicle connection lifecycle and broadcasts phase changes.

Lifecycle is the single source of truth for whether a client is connected and for the connection_id used on the wire. It mirrors the C# client's IConnectionLifecycle: there is one lifecycle per Chronicle.Client, every artifact that needs the connection (the registration coordinator, reactors, reducers, seeders, webhook and subscription registrars) subscribes to it, and the connection is driven through a small set of phase transitions.

Phases

The connection moves through three ordered phases:

• :disconnected — no live session with the kernel.
• :connected — the session handshake completed (the kernel acknowledged the connection_id via its first keepalive). The channel can carry calls.
• :registered — the registration coordinator has registered the base artifacts (event store, event types, read models, constraints, projections). Observers may now safely register their observation streams, and seeders may run.

Splitting :connected from :registered is what keeps reducers and reactors from racing ahead of their server-side definitions — they wait for :registered, never merely :connected.

connection_id

The lifecycle owns the connection_id. It is adopted on connected/2 and rotated on disconnected/1, so every reconnect uses a fresh id, exactly like the C# client. Because the id lives in one place, the value used in the session handshake and in every reactor/reducer registration is guaranteed consistent for a given connection epoch.

Subscribing

Subscribers call subscribe/1, which returns the current {phase, connection_id} snapshot and delivers it as a message. This closes the race where a subscriber starts after a phase change has already happened: it always learns the current phase immediately, whether it subscribed before or after the transition. Subsequent transitions arrive as messages of the form:

{:chronicle_lifecycle, phase, connection_id}

where phase is :connected, :registered, or :disconnected.