Upgrading to Kranz 0.16.1

Local runtime IPC protocol 3

Kranz 0.16.1 changed its local runtime IPC protocol from 2 to 3. A client and runtime must speak the same protocol, so a new TUI cannot attach to a runtime still running with 0.16.0, and an old client cannot attach to a new runtime. This separates the new explicit configuration reload behavior from older clients that could apply detected changes automatically. Configuration files do not need migration.

To move a running session to the new version, stop it and start it again with the updated binary. In 0.16.2 or later, press p in the TUI, select the incompatible other runtime, then press s. Review the shutdown confirmation and confirm. The current runtime has no s action in the list; use its usual q confirmation instead.

When the protocols differ, Kranz cannot read the old runtime's full shutdown plan. The confirmation shows only processes it can verify as owned by that runtime. Detached resources may remain running; inspect and stop them separately if needed.

See TUI controls for the runtime list shortcuts and the 0.16.1 and 0.16.2 releases for the complete changes.