In the connect-nodes wizard step 1, the “← Back” TextButton and the step heading (“Select a node to connect to …”) occupied the same horizontal Row. When the heading wrapped to a second line the layout produced an L-shaped text block: the left margin of the second line was indented by the width of the Back button, making the heading read as if it belonged to Back rather than to the content below.
SourceListWithBackNavigation placed its nav element and its title in one Row with verticalAlignment = CenterVertically. A single-line heading looks fine in this layout; a two-line heading (common for nodes with longer display names) breaks it because the second line sits inside the same Row slot after the Back button, not below it.
Removed the shared Row and promoted both elements to direct children of the enclosing Column. Back button renders on its own row (left-aligned, naturally); the title Text fills the full width below it via Modifier.fillMaxWidth() with padding(horizontal = CommonLayout.PADDING_SMALL) to match surrounding content insets.
When a nav element (Back, Cancel, breadcrumb) sits in the same Row as a title that may wrap, the second line will always be misaligned. The safe pattern is a vertical nav strip (Back on its own row) followed by the heading on the next row. Review any Row { navElement(); titleText() } pattern during PR review where the title string is dynamic or long.