OriginRouter CLI 0.4.4

English

Windows background service now actually launches. The scheduled task's
embedded PowerShell startup script escaped embedded quotes in the Bash
style (\"), which PowerShell does not honor. The script therefore failed
to parse, the daemon was never started, and the Local API stayed
permanently not ready — with no log output at all, since the failure
happened before any redirection. All values in the wrapper are now wrapped
in PowerShell single-quote literals. Verified on a real Windows 11 machine:
the generated script parses with zero syntax errors and node.exe receives
correctly quoted arguments.

This was the last remaining failure in the Windows install chain; originrouter setup now completes with all verification checks green.

Re-run the standard install in a normal PowerShell:
irm https://originrouter.com/install.ps1 | iex
Click "Yes" once when the Windows permission prompt appears (UAC may be
silent if prompts are disabled on your machine). No administrator window
is needed.

Windows 后台服务现在能够真正启动。 计划任务内嵌的 PowerShell 启动脚本
此前使用 Bash 风格的引号转义(\"),而 PowerShell 并不认这种转义,导致
脚本解析失败、daemon 从未被启动、Local API 永远无法就绪——而且由于失败
发生在任何重定向之前,连日志都不会留下。现在包装脚本中的所有值都改用
PowerShell 单引号字面量。已在真实 Windows 11 机器上验证:生成的脚本
语法解析零错误,node.exe 收到的参数引号正确。

这是 Windows 安装链路上最后一个遗留问题;originrouter setup 现在可以全绿通过。

在普通 PowerShell 中重新执行标准安装:
irm https://originrouter.com/install.ps1 | iex
出现 Windows 权限弹窗时点一次“是”即可(如果机器关闭了 UAC 提示则静默通过)。
全程不需要管理员窗口。