Demo:

Diagnostic diff on typing conformance tests

No changes detected when running ty on typing conformance tests ✅

Thanks for looking into this.

It now seems unfortunate that the module name comes directly (without any space) after the completion text which seems expected acording to the LSP specification

/**
 * Additional details for a completion item label.
 *
 * @since 3.17.0
 */
export interface [CompletionItemLabelDetails](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionItemLabelDetails) {

	/**
	 * An optional string which is rendered less prominently directly after
	 * {@link CompletionItem.label label}, without any spacing. Should be
	 * used for function signatures or type annotations.
	 */
	detail?: string;

	/**
	 * An optional string which is rendered less prominently after
	 * {@link CompletionItemLabelDetails.detail}. Should be used for fully qualified
	 * names or file path.
	 */
	description?: string;
}

I think we should at least insert a space at the front of detail if we want to use that field.

Or we keep using detail for the type but change the syntax to : {type}, similar to what we show in inlay hints. Wdyt?

Edit: I only just now saw your detailed write-up on the issue. I think what you did makes sense. I'm only wondering if we should introduce a space to make this look less squeezed together

Edit2: It seems that r-a solves this visual issue by using (use <module name>) for the left aligned content which helps a bit.

mypy_primer results

No ecosystem changes detected ✅
No memory usage changes detected ✅

Yeah and r-a inserts a leading space too.

I added the leading space and added (import <name>), which I think also helps (similar r-a's (use <name>)).

Demo: