[Christian Pfeiffer (ChrisTX)]

This replaces #2333, which I closed by accident when cleaning up my forks. It's the same change, rebased onto the current main.

6f76c6e introduced a correct change to the ValidateSet, but added a redundant check that is already handled in StartEditorServicesCommand.cs in its StartLogging() routine. In fact, exchanging the values in Start-EditorServices will suppress the warning about the old PSES log levels that StartLogging() would normally emit.

However, the check is actually harmful on top of this issue since it doesn't check if LogLevel is even set.
If LogLevel is $null, then the default option

default { $LogLevel }

isn't valid PowerShell anymore:

The variable cannot be validated because the value $null is not a valid value for the LogLevel variable.

[Copilot]

🟢 Approval recommended

No active review issues are reported for the removal of redundant log-level translation from the PowerShell startup wrapper.

No open issues 🎉

What changed in this PR

Removes redundant log-level translation from the PowerShell startup wrapper, leaving legacy-level handling to StartEditorServicesCommand.StartLogging().

Changes:

• Removes the reassignment that causes validation errors when LogLevel is omitted.
• Leaves legacy log levels unchanged for downstream handling and warnings.
• Normalizes indentation for SessionDetailsPath.

File	Description
module/​PowerShellEditorServices/​Start-EditorServices.ps1	Removes duplicate log-level conversion and adjusts parameter indentation.

_{Review effort: Balanced}