[Bug]: [Desktop][Windows] v1.38.6 启动时固定闪一次终端窗口

[Starin-Snowflakes]

Version line

v2 — Go rewrite (1.x), main-v2 (active development)

Exact version

Reasonix v1.38.6（windows-amd64）

What happened?

每次启动桌面端都会先闪出一个黑色终端窗口（约 1 秒），然后才进入界面。
该问题从 v1.38.6 开始出现，之前版本没有。
已确认与“启动时检查更新”无关：config.toml 里 check_updates = false 后现象依旧。

Steps to reproduce

1. 完全退出 Reasonix（托盘图标 -> Quit）。
2. 正常启动 Reasonix 桌面端（双击桌面快捷方式）。
3. 观察启动瞬间的屏幕。

预期行为：
Reasonix 主窗口直接打开，不出现任何其他窗口。

实际行为：
每次启动时，主窗口出现之前，会先闪出一个黑色终端/控制台窗口约 1 秒。该现象 100% 复现。

补充说明：

• 在 config.toml 中设置 check_updates = false 后仍可复现，因此与启动时的更新检查无关。
• 该终端窗口属于 versions\v1.38.6\reasonix-desktop.exe（PE 子系统为 console）。

OS / platform

Windows 11 x64，Reasonix v1.38.6（windows-amd64），默认安装路径

Relevant logs or output

[StefanBelo]

I have got 1.38.3 version, tommorow it suggested to update to 1.38.5 version, but anytime it failed with following error:

I have tried and installed 1.38.5 manually but again it installed correctly, but when runing Reasonx app it stopped with error message saying service version differs.

I had to go back to 1.38.3 when deleting all, but now again above error, so it seems the problems you introduced with .5 remain in .6 version as well.

[SivanCola]

Fixed by #10230 (merge f5f175205374).

The Windows Desktop service is now linked as a GUI-subsystem executable, preventing Windows from creating the startup console for the service. The production build and native-startup CI also check the PE subsystem.

Verification: source inspection of the Windows GUI linker flag and its build contract; the fixing PR also records five native Windows shortcut launches with zero console windows. Local regression checks passed at main-v2 e4bfeb67f912; the reporter's original machine was not rerun. Native results attributed to a fixing PR are that PR's recorded evidence.

Release availability: merged into main-v2 for the next planned Desktop/CLI release, v1.38.9. It is not included in the published v1.38.8 build, and v1.38.9 has not been published at the time of this reply.

Closing as completed. If the same reproduction persists in a build containing these changes, please reopen with that build's exact version and the new error or reproduction.