Symptom

The server settings tab (EditServer composable) had a meaningless horizontal divider, separate host and port fields with no way to test connectivity, and no metadata about the server (model, OS, version, node count). Refreshing nodes required an app restart.

Root cause

EditServer delegated layout entirely to ServerConnectionForm, which was designed for the connect flow (existing server editing context) and included an unneeded divider. No test-connectivity affordance or server metadata panel existed in the settings view.

Fix

• Removed the HorizontalDivider from EditServer in ServerView.kt.
• Inlined host and port fields into a single Row with a Test button; the button calls NodeHttp.readHealth(node) asynchronously, showing a spinner inside the button while in-flight and rendering “Connected” (primary color) or an error string (error color) as feedback below the row.
• Added a “Server Information” section below the connection row displaying model, OS, version, and live node count sourced from ServerMetaData.nodes.size.
• Added a Refresh Nodes button that calls NodeHttp.readNodes(node) and pushes each returned node into ClientNodeManager.update(), allowing the user to sync without restarting the app.

Prevention

Settings screens for connected resources should surface the resource’s live metadata and provide an inline connectivity test. Any edit form that lets users change a connection address should have an adjacent test-reachability action so the user can confirm the change before navigating away.