Command Line Empty for Process Initiated by System

## Expected Behavior
I should be able to see all PowerServe process by running the following:

```powershell
Get-Process pwsh | where commandline -match 'Start-PowerServe'
```

## Current Behavior
When process is initiated by SYSTEM level process the command line is empty.

Grabbing all pwsh process:
```powershell
get-process pwsh | select id,commandline

Id CommandLine
-- -----------
22084 "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo
72956 "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo
89868 "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo
…3616 "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo
…4128
```

Note that last blank one.

If I run the following, I can determine the PID:
```powershell
> PowerServeClient.exe -c '$PID' -p LePipe
184128
```

## Possible Solution
Not sure if this can be fixed, or if it just needs to be documented. I'm mostly interested in tracking perf of that process incase it needs to be killed.

## Steps to Reproduce

1. Execute a SYSTEM level process (in my case a python script) that calls PowerServeClient.
2. Wait for pwsh process to be started
3. Check running processes for pwsh with no commandline.

## Your Environment

* Version: `PowerServeClient 0.0.1-alpha2+2da69ad335bab00597fe9d532983522a6fa29808`
* Operating System(s): Windows 10 22H2 (19045.3570)
* PowerShell Version(s): 7.3.9

Start with the PowerServeClient entry point and reproduce the issue on Windows 10 with a SYSTEM-level process that launches PowerShell. Compare process inspection for user- and SYSTEM-started pwsh processes, then determine whether the missing command line can be exposed or should be documented as a limitation. Done means the behavior is fixed or clearly documented, with the PID-based tracking workflow still usable.

Written by the indexing model from the issue text.