Railbase core v0.20.17

Closing a console-launched Railbase now really stops it.

Closing the terminal used to leave the supervisor running: it caught the terminal's hangup, found no pending update, and kept going — reparented, with no terminal, still holding the HTTP port and the vault. The next launch then failed with address already in use against an invisible process. A hangup now stops the worker and exits, the way every other Unix service behaves. nohup ./railbase serve still detaches as before.

A server that cannot start no longer restarts forever. A boot that never began serving — the port is taken, the interactive port offer was declined — now exits with a distinct code (7) that the supervisor understands as a startup failure: it reports the error once and stops, instead of retrying every two seconds and re-asking the same question. The signal comes from the server itself rather than from a health probe, so it stays correct when something else (an orphaned instance, another service) is answering on that port.

Rollback stays available the moment an update commits. The rollback anchor is recorded before the update is published as committed, closing a window where the Update Center could show "updated" while offering nothing to roll back to.

Connect is gated on a connection test — without blocking what cannot be tested. On a plugin's Connect page, a system whose configuration can be probed keeps Connect disabled until "Test connection" passes for the values currently in the form; editing a field re-locks it. Where the server cannot reach the system itself — an on-prem database read by the agent — the test says so ("Not verified yet…") and creation proceeds, because the source must exist before the agent can be pointed at it. File and push sources are unaffected.