feat(tui): allow session names to wrap to two lines in dialog (#6165) - #6166

Using Locale.truncate with wrapMode="word" and maxHeight={2} is redundant. When wrapping is enabled, the text element will naturally wrap and constrain to maxHeight, making manual truncation unnecessary.

Additionally, the limit of 122 characters (exactly double the original 61) appears arbitrary and doesn't account for the actual available width, which varies based on terminal size, padding, and other UI elements.

Consider removing Locale.truncate entirely and letting the wrapping behavior handle long text naturally. Other parts of the codebase (e.g., dialog-status.tsx, todo-item.tsx, toast.tsx) use wrapMode="word" without manual truncation.

I checked with Claude and while it's a reasonable idea, it's not accurate for our desired UX.

Claude says it’s not redundant here:

• wrapMode="word" + maxHeight={2} limits layout height, but it does not guarantee a nice truncation indicator.
• Without Locale.truncate, overlong titles will typically just get hard-clipped at line 2 (depending on opentui’s overflow behavior), meaning users lose the “…” hint that there’s more text.
• Your examples (toast.tsx, dialog-status.tsx, todo-item.tsx) often use wrapping because they’re OK with showing as much as needed (or they don’t enforce “2 lines max with ellipsis”), so it's a different requirement.

What is true in your comment though:

• 122 is heuristic/arbitrary and not width-aware.
  But given opentui doesn’t give us an easy “truncate to N lines with ellipsis based on actual rendered width” primitive, the heuristic truncation is doing a job: “2 lines max, and show an ellipsis”. Claude suggests that if we wanted to improve this “properly”, we’d need a width-aware truncation (measure available width at runtime and truncate accordingly) or a library feature that truncates to N wrapped lines with ellipsis. That’s likely an opentui-level enhancement.