What happens

Clicking Open config or How to enable on any feature card in the dashboard (e.g. Memory Wiki) throws a PowerShell exception. Each click leaves a config.openFile failed warning in the gateway log.

Reproduction

1. Windows 11, OpenClaw 2026.5.28.
2. Open the dashboard → pick any feature card → click Open config (or How to enable).
3. PowerShell exception bubbles up in the dashboard UI; warning lands in openclaw logs --follow.

Root cause

dist/config-CSgRab7Q.js — resolveConfigOpenCommand(...) shells out via PowerShell with Start-Process -LiteralPath '<path>':

```js
if (platform === "win32") return {
command: "powershell.exe",
args: [
"-NoProfile",
"-NonInteractive",
"-Command",
`Start-Process -LiteralPath '${escapePowerShellSingleQuotedString(configPath)}'`
]
};
```

Start-Process does not have a -LiteralPath parameter in either Windows PowerShell 5.1 or PowerShell 7+. Only -FilePath exists. Tested in pwsh 7.6.1:

```
PS> Start-Process -LiteralPath 'C:\Users\me.openclaw\openclaw.json' -WhatIf
Start-Process: A parameter cannot be found that matches parameter name 'LiteralPath'.

PS> Start-Process -FilePath 'C:\Users\me.openclaw\openclaw.json' -WhatIf
What if: Performing the operation "Start-Process" on target ...
```

Suggested fix

Swap -LiteralPath → -FilePath. Works on both Windows PowerShell 5.1 and pwsh 7+:

```js
`Start-Process -FilePath '${escapePowerShellSingleQuotedString(configPath)}'`
```

Workaround

Patch dist/config-CSgRab7Q.js locally (lost on every update), or open `~/.openclaw/openclaw.json` manually in any editor.

Environment

• OS: Windows 11 (10.0.26220)
• OpenClaw: 2026.5.28
• Tested with both powershell.exe (5.1) and pwsh.exe (7.6.1) — same failure, since -LiteralPath does not exist on Start-Process in either version.