Nexus Launcher v1.0.3

Nexus 1.0.3

1.0.3 — 2026-09-26

• 修复 macOS/Linux 内置 Node 的 bin/npm、bin/npx 及存在的 Corepack 入口：打包展开符号链接后仍从正确的包目录启动，避免选择 bin/node 时出现 npm_probe_failed 并连带显示 pnpm 不可用。旧构建缓存会重新生成；已安装包需要升级才能获得修复。
• 官方桌面端后台运行时可再次“打开桌面端”，恢复已有窗口而不重启任务。按实际宿主能力显示入口，旧独立宿主保留原有控制方式。
• 明确关闭窗口后进程可能继续运行；切换模式或修改数据前仍须中止桌面端。保留新旧 Harness 接口兼容，不自动升级用户 Harness。

验证范围

平台构建和自动化检查不等于所有设备上的真实升级验收。内置 Harness 仍为 0.1.6-alpha.2；新版兼容适配不代表所有会话迁移及第三方插件已验收。

---

1.0.3 — 2026-09-26

• Fix bundled macOS/Linux Node bin/npm, bin/npx and available Corepack entry points. They now launch from the correct package directory after packaging dereferences symbolic links, preventing npm_probe_failed and the resulting unavailable pnpm status when bin/node is selected. Old build caches are regenerated; installed applications need an update to receive the fix.
• Open Desktop can restore an existing background desktop window without restarting its tasks. The running host advertises support; older independent hosts retain their existing controls.
• Clarify that closing a window may leave Desktop running. Stop Desktop before switching modes or changing data. Compatibility with older and newer Harness interfaces remains; user Harness installations are not upgraded automatically.

Verification scope

Platform builds and automated checks do not establish real upgrade acceptance on every device. Bundled Harness remains 0.1.6-alpha.2; compatibility work does not certify every session migration or third-party plugin.

Nexus Launcher v1.0.2

Nexus Launcher 1.0.2

中文

• 修复官方 Desktop 安装插件时包管理器可能沿源码链接修改官方运行文件的问题；安装前解除 Profile 中的官方源码投影，保留配置和外部插件链接。
• 打开设置按所选 Harness 的设置接口选择旧版 settings.yaml 或新版 Profile 配置；支持编译产物检测，未知接口明确报错。
• 快照恢复按唯一条目 id 回填当前密钥，避免配置列表重排后密钥错配；身份缺失或歧义时在写入前拒绝恢复。
• 增加 V3/V4 实时会话通知、迁移后配置恢复及插件写入边界的回归覆盖。

验收边界

未自动升级 Harness 或修改第三方插件。已核对 0.1.7-rc.1 关键接口，但不宣称所有第三方插件兼容或新版真实会话迁移已全面验收。程序仍保留官方源码启动与共享运行时结构。Git/SSH/LFS 和对应源码继续提供，不捆绑 GCM；离线转发请保留源码配套。运行时仍为显式路径优先，否则内置。本地 unsigned 验收不代表生产代码签名，CI 不代替所有真机安装升级验收。旧版公开附件保持不变。

English

• Protect official runtime files from package-manager traversal of source links during Desktop plugin installation. Detach official source projections in the Profile while preserving configuration and external plugin links.
• Open legacy settings.yaml or the new Profile configuration according to the selected Harness settings interface, including compiled artifacts; report unknown layouts explicitly.
• Restore current secrets by unique entry id rather than array position, preventing credential misassignment after configuration reordering. Reject missing or ambiguous identities before writing.
• Add regression coverage for V3/V4 live session notifications, migrated configuration recovery and plugin write boundaries.

Acceptance limits

Harness is not automatically upgraded and third-party plugins are unchanged. Key 0.1.7-rc.1 interfaces were reviewed; full third-party compatibility and real-session migration are not claimed. Official source-mode startup and shared runtimes remain. Git/SSH/LFS and corresponding source are provided without GCM; retain source companions when redistributing offline. Explicit runtime paths retain priority over bundled tools. Local unsigned acceptance is not production signing, and CI is not installation/upgrade acceptance on every device. Existing public downloads remain unchanged.

Nexus Launcher v1.0.1

Nexus Launcher 1.0.1

中文

• 采用透明“鲸鱼站长”作为统一图标，覆盖窗口、托盘、安装包与侧栏。
• 维护页诊断包移至本地依赖和离线配置档修复附近；诊断包与离线修复支持折叠，折叠不清空当前表单。
• 移除维护页重复嵌入的插件管理，保留独立“内置插件”和“配置与插件”入口。
• 修复插件仓库链接在 Electron 中点击无反应：通过受限的桌面接口打开 HTTPS GitHub 链接，拒绝其他协议、域名及带凭据地址。
• 设置页“原生集成”移至“安装包身份”上方，“启动配置说明”移至“帮助”下方。
• Windows/macOS ZIP 附件增加 _portable.zip 后缀，安装包名称不变；同步更新产物收集、摘要和来源校验规则。此命名不表示用户数据改存程序目录。

已知限制

本次未改变 Harness 数据存储或运行时优先级（显式路径优先，否则内置）。Git/SSH/LFS 与对应源码仍随发行提供，不捆绑 GCM。历史会话管理 JSON 错误仍属于未复现问题，未宣称已修复。自动测试及 CI 安装包检查不代替所有系统真机安装升级验收；本地 unsigned 验收不代表生产代码签名。原 1.0.0 下载附件保持不变。

English

• Adopt the transparent Whale Station Master icon across the window, tray, packages and sidebar.
• Move diagnostic bundles beside local dependencies and offline profile repair. Bundles and offline repair are collapsible without clearing form state.
• Remove duplicate plugin management embedded in Maintenance, while preserving Built-in plugins and Configuration and plugins.
• Fix plugin repository links that did not open in Electron. A restricted desktop bridge opens HTTPS GitHub links and rejects other schemes, domains and credential-bearing URLs.
• Move Native integration above Release identity and Launch configuration explained below Help.
• Add _portable.zip to Windows/macOS ZIP attachment names, preserving installer names. Update collection, checksum and provenance checks accordingly. The filename does not imply storing user data beside the executable.

Known limits

Harness data storage and runtime priority (explicit paths, otherwise bundled) are unchanged. Git/SSH/LFS and corresponding source remain provided, without GCM. The historical session-manager JSON error remains unreproduced, not claimed fixed. Automated and CI package checks do not replace installation/upgrade acceptance on every device; local unsigned acceptance is not production code signing. Existing 1.0.0 downloads remain unchanged.

Nexus Launcher v1.0.0

Nexus Launcher 1.0.0

中文

使用体验与修复

• Harness 未启动，也能管理和修复配置。 插件清单、启用、禁用、安装、检查及移除优先复用所选 Harness 的官方管理器和保护规则；新插件默认保持禁用，禁用不会删除依赖。旧版本保留兼容入口。
• 正常启动先运行，失败才诊断。 减少每次启动前重复拷贝和兼容检查；只有证据明确指向缺失依赖时，才允许有限修复并重试一次。配置、版本或停止操作发生变化时，旧恢复任务不会继续启动。
• 启动超时与真正失败分别留档。 超时只表示尚未确认就绪，不会擅自停止或重启仍在运行的 Harness；之后若发生真实失败，仍会保存新的错误证据。
• 修复 Desktop 的旧官方包遮蔽问题。 启动时绑定当前版本的官方模块，并备份遮蔽它们的旧官方包，避免旧 settings 提供方与新接口冲突。第三方插件和配置保持原样。
• 离线修复更可控。 配置修复提供预览、备份、复查与恢复路径；不以禁用所有等待服务的插件代替定位。Node、pnpm 和 Git 优先使用明确指定的路径，否则使用内置工具，未采用系统环境优先的新规则。
• 版本切换更直接。 安装准备完成后可直接切换至该版本；上游 0.1.7 的兼容判断按实际能力和构建目标处理，不用版本白名单决定启动加速。
• 配置与历史记录更清晰。 快照、检查点按本机时区显示时间，详情使用抽屉并提供可读配置和源码视图；补齐插件版本、仓库链接、问题标记及删除相关入口。
• 设置错误不再静默忽略。 修复随机端口 0 等配置传递问题；明确工具路径覆盖的适用范围，日志级别或系统开机启动设置失败时显示原因。

离线工具与分发材料

• 内置完整 Git 命令行、SSH 和 Git LFS，不捆绑可选 GCM 网页登录助手及其依赖。不会修改用户系统或全局 Git 配置；需要额外登录助手时可显式指定自行配置的 Git。
• 运行所需工具仍随 Nexus 提供。Git 及相关组件的对应源码作为独立附件与安装包一同提供，不计入日常运行时加载；再次分发二进制时应同时满足其源码交付条件。
• 发行流程校验通知原文摘要、源码清单、源码附件和安装包来源，材料不完整时不放行发布。

已知限制与验收范围

• Nexus 负责启动、就绪判断及离线修复，不承诺捕获所有第三方插件运行时错误。会话管理插件历史 JSON 错误在隔离官方 Desktop 后端中未复现：相关接口返回 200 和有效 JSON，不能据此宣称原故障已修复或确认上游有错。
• 官方 Desktop 仅在上游与 Electron 支持的交集内启用。Nexus 支持某个平台，不等于对应 Harness 提供该平台的 Desktop。
• 切回旧 Harness 槽位不会降级上游会话数据格式；升级前请保留数据备份。
• 自动化测试、真实子进程测试、Windows 隔离安装升级与五平台 CI 分开记录；跳过项不计通过。CI 安装包冒烟不替代所有发行版、输入法、显示器和完整业务流程的真机验收。

English

User-visible changes and fixes

• Manage and repair profiles while Harness is stopped. Plugin listing, enabling, disabling, installation, checks and removal use the selected Harness version's official manager and protection rules where available. Newly installed plugins remain disabled until enabled; disabling retains dependencies. Older versions retain a compatibility path.
• Run first and diagnose failures. Normal startup avoids repeating profile copies and compatibility checks. Only evidence of missing dependencies permits one bounded repair and retry. A changed profile, release or stop request cancels stale recovery work.
• Preserve separate timeout and failure evidence. A timeout means readiness is unverified; it does not stop or restart a running Harness. A later real failure still receives a separate diagnostic record.
• Fix stale official packages shadowing Desktop modules. Desktop binds official modules from the selected release and backs up older official packages that shadow them, including incompatible settings providers. Third-party plugins and profile settings are preserved.
• Make offline repair controlled and recoverable. Repairs provide previews, backups, rechecks and recovery paths. Waiting service consumers are not all disabled as a substitute for finding the provider failure. Node, pnpm and Git use an explicit configured path first and bundled tools otherwise; the proposed system-environment priority was cancelled.
• Switch prepared versions directly. A completed preparation offers a switch-to-version action. Harness 0.1.7 compatibility and startup acceleration follow capabilities and declared build targets rather than a version allowlist.
• Clarify profiles and history. Snapshots and checkpoints show local-time timestamps in drawer details, with readable and source views. Plugin versions, repository links, problem markers and removal entries are included.
• Report settings failures. Random port 0 and related preference forwarding are fixed. Tool-path override scope is documented; log-level and OS startup-setting failures surface their reasons.

Offline tools and distribution materials

• Bundled Git includes its command line, SSH and Git LFS, but excludes the optional GCM browser-login helper and its dependencies. System and user Git configuration are not changed. Users needing another login helper can explicitly select their own configured Git.
• Runtime tools remain bundled with Nexus. Corresponding source for Git and related components accompanies installers as a separate release attachment and is not loaded during normal use. Redistributing binaries must also satisfy the applicable source-delivery conditions.
• Publication checks original-notice hashes, the source inventory, source attachments and installer provenance. Incomplete materials prevent publication.

Known limits and acceptance scope

• Nexus handles startup, readiness and offline repair; it does not guarantee capture of every third-party runtime exception. The historical session-manager JSON error was not reproduced with an isolated official Desktop Host: the relevant APIs returned HTTP 200 and valid JSON. This does not establish that the original error is fixed or that upstream is at fault.
• Official Desktop is enabled only where both upstream and Electron support it. A Nexus package for a platform does not imply that Harness provides Desktop there.
• Switching to an older Harness slot does not downgrade upstream session data formats. Keep a pre-upgrade data backup.
• Automated tests, real subprocess tests, isolated Windows installer upgrades and five-platform CI are reported separately. Skips are not passes. CI package smoke tests do not replace device acceptance for every distribution, IME, display or complete workflow.

Nexus Launcher v0.1.10

Nexus Launcher 0.1.10

中文

修复的问题

1. 检查没通过，就不会再打开报错网页。 以前 Harness 进程运行且已有 URL 时，工作台和托盘可能允许打开浏览器，即使界面同时显示“客户端未就绪”。现在工作台、托盘、通知跳转及自动打开统一要求本次客户端检查通过；执行打开动作前还会重新读取状态，防止旧按钮状态误放行。检查中、未验证、核心服务受阻时保留停止、诊断和修复入口，不把进程存在当作可用。

2. 从托盘启动也能知道结果。 Windows 使用原生托盘气泡提示正在启动、已就绪、失败或未验证，点击可回到工作台处理。通知按本次启动去重，旧进程的成功记录不能让新启动提前报喜；停止与取消也会结束对应提醒。托盘气泡已由用户在 Windows 真机验收。

3. 停止、取消和重启更一致。 Web 托盘重启复用工作台流程；启动检查中可取消，取消绑定当前启动任务，旧菜单不会取消新的任务。Desktop 工作台和托盘共用重启逻辑，停止失败不启动第二个实例；重启等待停止期间再点停止，会取消后续启动。

4. Desktop 报错也有明确处理方向。 Web 和 Desktop 共用启动错误分类，区分缺失依赖、配置损坏、接口不兼容和服务等待，保留官方错误并提供依赖检查、配置管理和日志入口。明确提示 Desktop 使用独立的 desktop 配置，不会因为某插件在等待服务就认定它有故障。

5. Windows 状态文件短暂占用不再立即判为启动失败。 Desktop 状态写入遇到短暂共享冲突时，最多约 0.5 秒有限重试，保留原子替换和旧状态，永久错误仍报告。

新增和改进的机制

1. 离线依赖修复：先预览，再确认。 维护页根据所选 Harness 的锁文件与本地包身份检查缺失链接，支持 pnpm 11 的缩短目录名。只补能验证名称和版本的缺失链接，不下载、不覆盖已有文件或损坏链接；执行前保存锁文件、相关清单和修复计划，执行后逐项记录并复检。过期预览必须重新检查，修复完成仍需启动对应模式验证。
2. 减少重复缓存等待，同时保留检查。 桌面运行时缓存检查改为最多 16 个文件系统请求并行，仍遍历全部条目、验证链接范围，损坏时仍重建。同机 8,909 项缓存的只读对比中，这一阶段从约 1.5–1.8 秒降至 0.5–0.7 秒，结果与原记录一致；不代表完整冷启动耗时或所有机器的提速幅度。
3. 能看见启动时间花在哪里。 Web 展示输入检查、兼容检查和创建进程阶段耗时；Desktop 展示准备阶段明细。结束后计时冻结，新启动重新计时，不把后续使用时间算作启动耗时。
4. 更新前可以先看具体变化。 更新确认窗口在版本号旁增加“查看更新内容”，打开对应版本的 GitHub 发布页。确认下载、进度、下载校验、稍后重启及确认安装的流程保留；隔离 Windows 更新测试覆盖中断后恢复及重启后的版本、文件摘要检查。

已知缺陷与兼容边界

• 上游 Desktop 插件市场的包管理问题仍未代修。 dshmarket 在官方 Desktop 内安装、更新或重启仍可能失败；本版没有伪造 PATH、服务或配置来源，也没有强制回退 Web，仍需上游修复。
• 依赖修复有明确范围。 只处理 Nexus 管理的 Harness 版本中可验证的本地缺失链接，外部源码、已有损坏链接、缺少包文件等情况可能需要其他修复。它不是一键重装所有依赖，也不证明所有插件启动成功。
• 启动检查不等于全面运行时监控。 未验证不等于已确认失败；检查通过不覆盖全部对话、工具和第三方插件功能。首次准备仍受磁盘、配置和插件数量影响。
• 系统通知可能被操作系统隐藏。 Windows 通知设置、勿扰模式等可能影响气泡展示，工作台和托盘状态仍保留检查结果。Windows 的用户验收不替代 macOS/Linux 通知的真机验收。
• 平台与离线原则不变。 官方 Desktop 仍面向 Windows x64、macOS Intel/Apple Silicon；Windows ARM64 和 Linux ARM64 提供 Web 模式。Linux ARM64 提供 AppImage、DEB、RPM，不保证每种信创发行版均完成真机验收。Nexus 自带运行时；下载 Harness 后及导入同系统同架构完整离线包后的准备不依赖网络，第三方插件下载仍需要联网。

English

Problems fixed

1. A pending or failed check no longer opens a broken page. Previously a running Harness process and URL could enable the workbench or tray browser action even while the client was unavailable. Workbench, tray, notification links and automatic opening now require a successful client check for the current run. Opening re-reads the latest status to reject stale enabled buttons. Stop, diagnosis and repair remain available while checking, unverified or blocked; a process alone is not readiness.

2. Tray launches report their outcome. Native Windows balloons show starting, ready, failed or unverified states and open the workbench when clicked. Results are deduplicated per launch, and success from an old run cannot announce a new launch as ready. Stop and cancellation end the corresponding feedback. A user has accepted the balloons on a real Windows machine.

3. More consistent stop, cancel and restart. Web tray restart uses the workbench flow. Startup checks can be cancelled, with cancellation bound to the displayed operation so stale menus cannot cancel new work. Desktop workbench and tray share restart behavior: a failed stop never starts another instance, and another Stop during restart cancels its pending launch.

4. Actionable Desktop startup errors. Web and Desktop share classification for missing dependencies, damaged configuration, incompatible interfaces and waiting services. Official details remain available with dependency inspection, profile management and log entry points. Guidance names the independent desktop profile and does not blame a plugin merely because it is waiting for a service.

5. Brief Windows state-file locks no longer immediately fail startup. Desktop state writes retry transient sharing conflicts for at most about 0.5 seconds, retaining atomic replacement and the prior state. Persistent errors are still reported.

New and improved mechanisms

1. Preview and confirm offline dependency repairs. Maintenance checks missing links against the selected Harness lockfile and local package identity, including pnpm 11 shortened directory names. It only restores missing links to verified packages, without downloading or replacing existing files or broken links. Before changes it records the lockfile, relevant manifests and plan; afterwards it journals and rechecks results. Stale previews require a new inspection. The affected mode still needs a startup check after repair.
2. Less cache waiting without skipping verification. Desktop runtime cache checks use at most 16 concurrent filesystem requests while inspecting every entry and link boundary and rebuilding damaged caches. A read-only comparison of 8,909 entries on the same machine reduced this stage from about 1.5–1.8 seconds to 0.5–0.7 seconds, with identical inventory results. This is not a total cold-start measurement or a guarantee for every machine.
3. See where startup time is spent. Web shows input checks, compatibility checks and process creation; Desktop shows preparation stages. Timings freeze on completion and reset for a new launch, excluding subsequent usage time.
4. Read changes before downloading an update. The update confirmation dialog adds View release notes beside the version, opening that version's GitHub page. Download consent, progress, validation, deferred restart and explicit installation remain in place. An isolated Windows update test covered interrupted-download recovery and post-restart version and file-hash checks.

Known issues and compatibility boundaries

• Upstream Desktop marketplace package management remains unresolved. Installing, updating or restarting through dshmarket inside official Desktop can still fail. This release does not spoof PATH, services or profile ownership, nor force a Web fallback; an upstream fix is still needed.
• Dependency repair has a defined scope. It restores verified missing links within Nexus-managed Harness versions. External sources, existing broken links and missing package files can require other recovery. It does not reinstall every dependency or prove every plugin starts.
• Startup checks are not comprehensive runtime monitoring. Unverified is not a confirmed failure; passing checks does not validate every conversation, tool or third-party plugin. First-run preparation still depends on storage, configuration and plugin count.
• The OS can suppress notifications. Windows notification settings or Do Not Disturb may hide balloons. Workbench and tray retain the status. User acceptance on Windows does not establish real-device notification acceptance on macOS or Linux.
• Platform scope and offline behavior are unchanged. Official Desktop remains available on Windows x64 and macOS Intel/Apple Silicon; Windows ARM64 and Linux ARM64 provide Web mode. Linux ARM64 offers AppImage, DEB and RPM without claiming real-device acceptance on every distribution. Nexus includes its runtimes; preparation after acquiring Harness or importing a full offline package on the same OS and architecture needs no network. Downloading third-party plugins still requires a connection.

下载与验证 / Downloads and verification

Windows x64/ARM64：EXE 或 ZIP；macOS Intel/Apple Silicon：DMG 或 ZIP；Linux ARM64：AppImage、DEB、RPM。ZIP 必须完整解压，不能只复制可执行文件；免安装不代表用户数据随目录移动。

Windows x64/ARM64: EXE or ZIP; macOS Intel/Apple Silicon: DMG or ZIP; Linux ARM64: AppImage, DEB or RPM. Extract ZIP packages completely; do not copy only the executable. Portable installation does not make user data portable.

以同一提交的五平台 Actions 结果、附件内的 _build.json 和 SHA256 清单确认构建来源与自动化检查范围。摘要签名不是操作系统代码签名；构建和安装包冒烟不等于所有系统、完整业务、输入法和自动更新的真机验收。本地测试中显式跳过的环境相关用例不计入通过数量。

Use the five-platform Actions results for the same commit, packaged _build.json files and SHA256 manifests to verify provenance and automated check scope. Manifest signing is not OS code signing. Builds and package smoke checks do not establish device acceptance for every OS, workflow, IME or automatic-update scenario. Environment-specific tests explicitly skipped locally are not counted as passed.

Nexus Launcher v0.1.9

Nexus Launcher 0.1.9

中文

修复的问题

1. 官方桌面窗口能正常打开，托盘操作与工作台一致。 修复 Windows 上进程已经启动但窗口不显示的问题；托盘启动、停止、打开网页和终端复用工作台流程，检查结果、修复提示与状态刷新保持一致。工作台补齐 Desktop 关闭和重启，停止失败时不会继续启动第二个实例。
2. 不再把“还在启动”误报为失败。 请求等待时间覆盖后台准备和兼容性检查；通信超时后先核对实际状态，避免重复启动或误弹插件修复。“可用，有警告”会列出相关可选插件与原因。
3. Desktop 启动报错会回到 Nexus。 官方客户端配置或插件加载失败时，启动器主动提示并展开诊断，同一次失败只提醒一次。即使进程已退出、结构化记录缺失或损坏，也读取官方错误报告并保留首个错误，帮助查找缺失服务的提供方，而不是把等待中的插件全部判为故障。
4. Web 检查通过后才自动打开网页。 修复先打开报错网页、随后才提示修复的体验；核心服务未就绪时在启动器中显示原因和诊断入口，不会自动停用插件。

新增和改进的机制

1. 减少 Web 和 Desktop 的重复启动准备。 对已验证的 Harness 0.1.6-alpha.2，正常 Web 启动直接观察本次正式进程的启动信号及实际网页客户端，不再先启动隔离实例再启动正式实例。旧记录不能让新进程提前成功；手动检查、配置/版本切换检查及不支持此接口的版本仍使用隔离检查。依赖复制采用有限并行，减少重复扫描和桌面运行时重复读取，保留完整性与链接检查。同机同配置单次 Web 对比从约 67 秒降至 10.4 秒；这不是重启系统后的冷缓存测试，也不是所有机器的速度承诺。
2. 桌面端也有启动检查。 检查实际官方客户端的加载结果，不以进程存在代替成功。检查不受支持或等待过久时显示“未验证”；失败时保留官方修复入口。检查只覆盖启动阶段，不承诺捕获运行中的全部业务错误。
3. 配置与终端操作范围更清楚。 Web 显示选中的配置档，Desktop 明确使用独立的 desktop 配置，二者插件设置不会自动同步。DSH 终端打开时列出绑定配置、工作目录、数据目录、Harness 来源及 Desktop 配置目录，说明 dsh 与 npm/pnpm 的目标区别；这是打开时的快照，切换配置后应重开终端。配置档展开后按插件清单、快照清单、已保存检查点排列。
4. 更新由用户确认后下载。 发现新版本只提示可更新；点击后先打开确认窗口，确认下载后显示进度，校验完成才提供“稍后重启”与“更新并重启”。下载完成不会直接安装；应用更新前请保存工作，更新会停止 Harness 并重启 Nexus。
5. 新装插件市场默认使用 dshmarket 1.52.0。 上游修正了官方 Desktop 配置识别及部分请求来源检查，减少误操作 Web 配置的情况。该版本仅作为首次安装默认值，不自动替换已有配置中的市场，也不代表下面列出的 Desktop 包管理问题已解决。

已知缺陷与兼容边界

• 官方 Desktop 内插件市场的安装、更新或重启仍可能失败。 dshmarket 1.52.0 虽识别 Desktop 配置，但包管理操作尚未完整接入官方 Desktop 提供的环境；升级市场不能保证消除 dsh/pnpm 或重启报错。Nexus 不伪造配置来源、不强行回退 Web，也不自动改写上游插件，等待上游修复。
• 第三方命令输出乱码未作为本版通用修复交付。 排查时在单台机器验证过输出解码修正，但这不在 Nexus 安装包内，插件更新可能覆盖该本地修改。已损坏的 Harness 依赖链接也不会仅因升级 Nexus 而自动恢复；本版不宣称解决所有依赖损坏。
• 启动检查不是完整运行时监控。 “未验证”不等于确认失败，启动通过也不代表每个会话、工具、插件功能都兼容。首次准备仍受磁盘、插件数量和配置影响。
• 平台范围不扩大到上游未支持的平台。 官方 Desktop 提供 Windows x64、macOS Intel/Apple Silicon；Windows ARM64 和 Linux ARM64 提供 Web 模式。Linux ARM64 提供 AppImage、DEB、RPM，但不等于所有麒麟、统信或其他发行版均经过真机验收。
• 离线原则不变。 Nexus 自带必需运行时；取得 Harness 后，桌面准备和同系统同架构的完整离线包导入不需要联网。第三方插件下载仍需要网络，配置/数据部分包不能替代完整离线包。

English

Problems fixed

1. Official Desktop opens visibly, and tray actions match the workbench. Fix Windows launches where the process started without a visible window. Tray start, stop, open-page and terminal actions share the workbench flow, including checks, recovery feedback and status refresh. The workbench adds Desktop Close and Restart; a failed stop never starts a second instance.
2. Waiting is no longer mistaken for failure. Request time budgets accommodate background preparation and compatibility checks. After a transport timeout, Nexus checks actual state before repeating a launch or suggesting plugin repair. “Ready with warnings” identifies the affected optional plugins and their reported reasons.
3. Desktop startup errors surface in Nexus. Configuration or plugin-loading failures bring the launcher forward and expand diagnostics, once per failed operation. Failure details survive process exit. Official error reports are read even if structured evidence is missing or malformed, preserving the first cause so users can investigate missing service providers instead of blaming every waiting plugin.
4. Web opens automatically only after client checks pass. Blocking failures stay in the launcher with their reason and diagnostic entry point, instead of opening a broken page before offering recovery. Nexus does not automatically disable plugins.

New and improved mechanisms

1. Less repeated preparation for Web and Desktop. For verified Harness 0.1.6-alpha.2, normal Web startup observes the actual managed process and browser client instead of starting an isolated probe and then launching again. Stale evidence cannot mark a new process ready. Manual checks, profile/version-switch checks and unsupported versions retain isolated checks. Bounded parallel dependency copying and fewer repeated scans/archive reads reduce preparation while retaining integrity and link checks. One same-machine, same-profile Web comparison improved from about 67 to 10.4 seconds; this was not a post-reboot cold-cache test or a guarantee for every machine.
2. Desktop has startup checks too. Nexus observes the actual official client rather than treating a running process as success. Unsupported checks or long waits remain “Unverified”, and official recovery remains available on failure. These checks cover startup, not every subsequent application error.
3. Clearer profile and terminal scope. Web shows the selected profile; Desktop uses its independent desktop profile, without automatically synchronizing plugin settings. The DSH terminal opening banner lists its bound profile, working directory, data home, Harness source and Desktop profile directory, and explains dsh versus npm/pnpm targeting. It is an opening snapshot; reopen the terminal after switching profiles. Expanded profiles list plugins, snapshots, then saved checkpoints.
4. Updates download only after confirmation. Finding a version only announces availability. Clicking Update opens a confirmation dialog; confirming starts the download with progress. Only a verified download offers Restart later or Update and restart. Download completion never installs automatically. Save work before applying an update: it stops Harness and restarts Nexus.
5. Fresh marketplace installations default to dshmarket 1.52.0. Upstream fixes official Desktop profile recognition and some request-origin checks, reducing accidental targeting of Web profiles. This is a first-install default, not an automatic replacement of existing installations, and it does not resolve the Desktop package-management limitation below.

Known issues and compatibility boundaries

• Marketplace install, update or restart inside official Desktop can still fail. Although dshmarket 1.52.0 recognizes the Desktop profile, its package operations do not fully use the environment provided by official Desktop. Upgrading the marketplace does not guarantee that dsh/pnpm or restart errors disappear. Nexus does not spoof profile ownership, force a Web fallback or automatically modify upstream plugins; an upstream fix is still needed.
• Third-party command-output encoding is not a general fix shipped in this release. A decoding adjustment was verified on one machine during investigation, but is not included in Nexus packages and can be overwritten by a plugin update. Existing damaged Harness dependency links likewise are not automatically restored just by upgrading Nexus; this release does not claim to repair every dependency failure.
• Startup checking is not comprehensive runtime monitoring. “Unverified” does not mean a confirmed failure, and passing startup does not validate every conversation, tool or plugin feature. First-run preparation still depends on storage, plugin count and configuration.
• Platform scope stays within upstream support. Official Desktop is available on Windows x64 and macOS Intel/Apple Silicon. Windows ARM64 and Linux ARM64 provide Web mode. Linux ARM64 offers AppImage, DEB and RPM, without claiming device acceptance on every Kylin, UOS or other distribution.
• The offline contract is unchanged. Required runtimes ship with Nexus. After acquiring Harness, Desktop preparation and full offline-package import on the same OS and architecture need no network. Third-party plugin downloads still require a connection; configuration/data-only packages cannot replace full offline packages.

下载与验证 / Downloads and verification

Windows x64/ARM64：EXE 或 ZIP；macOS Intel/Apple Silicon：DMG 或 ZIP；Linux ARM64：AppImage、DEB、RPM。ZIP 必须完整解压，不能只复制可执行文件；免安装不代表用户数据随目录移动。

Windows x64/ARM64: EXE or ZIP; macOS Intel/Apple Silicon: DMG or ZIP; Linux ARM64: AppImage, DEB or RPM. Extract ZIP packages completely; do not copy only the executable. Portable installation does not make user data portable.

以同一提交的五平台 Actions 结果、附件内的 _build.json 和 SHA256 清单确认构建来源与自动化检查范围。摘要签名不是操作系统代码签名；构建和安装包冒烟不等于所有系统、完整业务、输入法和自动更新的真机验收。本地测试中显式跳过的环境相关用例不计入通过数量。

Use the five-platform Actions results for the same commit, packaged _build.json files and SHA256 manifests to verify provenance and automated check scope. Manifest signing is not OS code signing. Builds and package smoke checks do not establish device acceptance for every OS, workflow, IME or automatic-update scenario. Environment-specific tests explicitly skipped locally are not counted as passed.

Nexus Launcher v0.1.8

Nexus Launcher

下载 / Downloads

Windows x64/ARM64：EXE 安装包或 ZIP 免安装包。macOS Intel/Apple Silicon：DMG 或 ZIP。Linux ARM64：AppImage、DEB、RPM（仅列入已通过原生构建和启动检查的附件）。无 32 位版本。

Windows x64/ARM64: EXE installer or portable ZIP. macOS Intel/Apple Silicon: DMG or ZIP. Linux ARM64: AppImage, DEB and RPM (include only artifacts that passed native build and launch checks). No 32-bit builds.

Windows ZIP 请完整解压并运行 Nexus Launcher.exe，不能单独复制 EXE。免安装不等于数据便携：用户配置与 Harness 数据仍保留在用户数据目录。

Extract the entire Windows ZIP and run Nexus Launcher.exe; do not copy the EXE alone. Portable means no installer is required, not that user configuration and Harness data move with the application folder.

包内含 Chromium、Rust Agent、Node/npm/pnpm，以及支持平台的官方 Desktop 离线运行时。取得 Harness 版本后，Desktop 准备与完整离线包导入均不需要联网。官方 Desktop 支持 Windows x64、macOS Intel／Apple Silicon；Windows ARM64 和 Linux ARM64 当前提供 Web 模式。兼容范围取 Harness 与 Electron 的交集。

Includes Chromium, Rust Agent, Node/npm/pnpm and the official Desktop offline runtime on supported platforms. After acquiring Harness, Desktop preparation and full offline-package import need no network. Official Desktop supports Windows x64 and macOS Intel/Apple Silicon; Windows ARM64 and Linux ARM64 currently provide Web mode. Supported targets are the intersection of Harness and Electron support.

本次变化（中文）

1. 直接使用 Harness 官方桌面端

   现在可以启动当前受管 Harness 版本自带的 Desktop，无需使用 Nexus 自制客户端。只有所选版本与当前平台支持时才显示桌面入口，避免出现无法使用的选项。

2. 工作台和托盘更清晰，配置切换更方便

   Web 与 Desktop 统一放在 Harness 区域，明确显示当前模式、运行状态和可用操作，并保留醒目的配置切换入口。托盘补齐桌面端启动、Web／Desktop 中止、配置与维护入口，同时区分“仅退出启动器”和“中止所有服务后退出”。

3. 启动失败后有明确的修复路径

   区分真正出错的插件、缺失服务和仍在等待的插件，根据明确证据提供修复建议。用户确认后可暂时禁用相关插件并重新检查、启动；插件包和数据保留，后续可以重新启用。

4. 启动结果更可信

   不再仅凭进程运行或网页可访问就显示启动成功，而是检查客户端插件和核心服务，并区分检查中、功能受限、启动失败和未验证。加载长期阻塞时也会持续提供状态；这些检查针对启动阶段，不代表所有会话、工具或运行中业务都已验证。

5. 减少重复文件，改善首次启动等待

   Nexus 与官方 Desktop 共用匹配版本的 Electron，桌面端依赖提前准备，重复启动可复用已校验的本地文件。准备界面显示阶段、耗时和取消入口，用户能够了解进度并中止等待；准备期间无需联网补装依赖。

6. 完整离线包更可靠，移动目录后更省心

   完整导出包含匹配的 Harness 和所需运行时，同系统、同架构导入后无需联网补装。修复便携目录移动后的旧路径引用，并保留 Unix 可执行权限与相对链接；仅配置／数据导出仍属于部分包，不能替代完整离线包。

7. 增加 Linux ARM64 下载，完善跨平台交付

   新增 AppImage、DEB、RPM，Windows 与 macOS 继续提供对应架构的安装包和压缩包。五个平台均通过 CI 与安装包检查；Windows ARM64 和 Linux ARM64 当前提供 Web Harness，官方 Desktop 仅在上游与 Electron 均支持时开放。安装包检查不代表已逐一验证所有 Linux 发行版和业务场景。

What changed (English)

1. Use the official Harness Desktop

   Launch the Desktop included in your selected managed Harness release instead of a Nexus-built replacement client. The Desktop option appears only when both the selected release and your platform support it.

2. Clearer workbench and tray controls, with easier profile switching

   Web and Desktop now share one Harness area with clear mode, status and available actions, while profile switching remains easy to find. The tray adds Desktop launch, separate Web/Desktop stop controls, profile and maintenance shortcuts, and distinct options to exit only the launcher or stop all services.

3. A practical recovery path when startup fails

   Nexus distinguishes failing plugins, missing services and plugins still waiting for dependencies, then recommends repairs based on observed evidence. With your confirmation, it can temporarily disable the relevant plugins and check and start again. Packages and data remain available, and plugins can be re-enabled later.

4. More reliable startup results

   A running process or accessible webpage no longer counts as successful startup on its own. Nexus checks client plugins and core services, showing checking, limited functionality, startup failure or unverified states, including when loading remains blocked. These checks cover startup, not every conversation, tool or operation during use.

5. Fewer duplicate files and less first-start preparation

   Nexus and official Desktop share a matching Electron runtime, with Desktop dependencies prepared in advance and verified local files reused on later launches. Preparation shows its stage, elapsed time and a cancel action, so you can follow progress or stop waiting. It does not download missing dependencies during preparation.

6. More dependable offline packages and portable directory moves

   Full exports include matching Harness files and required runtimes, allowing import on the same OS and architecture without downloading dependencies. This release fixes stale paths after moving a portable directory and preserves Unix executable permissions and relative links. Configuration/data-only exports remain partial packages and do not replace a full offline package.

7. Linux ARM64 downloads and broader platform delivery

   AppImage, DEB and RPM packages join the existing Windows and macOS installers and archives. All five targets passed CI and package checks. Windows ARM64 and Linux ARM64 currently offer Web Harness; official Desktop appears only where both upstream Harness and Electron support it. Package checks do not establish compatibility with every Linux distribution or business workflow.

验证 / Verification

以本次 _build.json、SHA256 清单和 Actions 结果确认来源及检查范围。清单签名不等于操作系统代码签名；自动化检查不等于完整业务、更新、输入法与跨平台真机验收。

Use this release's _build.json, SHA256 manifests and Actions results to establish provenance and check scope. Manifest signatures are separate from OS code signing. Automation does not establish complete workflow, update, IME or cross-platform device acceptance.

更新会重启 Nexus；运行中的 Harness 会被中止，请先保存工作。可手动下载完整包使用，无需通过自动更新。

Applying an update restarts Nexus and stops a running Harness; save work first. You may download a complete package manually without using automatic updates.

Nexus Launcher v0.1.7

Nexus Launcher

Electron 桌面包支持 Windows/macOS x64 和 ARM64；不再提供 32 位版本。
Windows 可选择 EXE 安装包或 ZIP 免安装包（x64 / ARM64）；ZIP 完整解压后运行 Nexus Launcher.exe，不需要执行安装程序。请保留整个解压目录，不能单独复制 EXE。
macOS 可选择 DMG 或 ZIP 应用包。latest 元数据用于自动更新。

免安装指程序无需安装；用户配置与 Harness 数据仍保存在现有用户数据目录，不会随 ZIP 自动迁移。免安装包也可以手动下载新版、解压到新目录，退出旧版 Launcher 后运行新版。

包内包含 Chromium、Rust Agent 和 Node/npm/pnpm，无须预装开发工具。
Harness 的首次在线依赖准备与桌面离线安装不同。

请以本次 _build.json、SHA256 清单及 Actions 结果确认来源、签名和验证状态。
自动化检查不等于完整业务、签名升级、输入法和跨平台真机验收。

Nexus Launcher v0.1.4

Nexus Launcher v0.1.4 将桌面宿主完整迁移至 Electron，支持 Windows 和 macOS 的 x64 / ARM64，不再提供 Tauri 或 32 位安装包。

• GitHub Release 的 v<version> tag 标识版本；启用自动更新时，启动检查一次，之后每两小时检查。
• 发现更新后后台下载，侧栏左下角显示进度；下载并校验完成后，点击“更新”重启并应用。
• 设置中可关闭自动更新，也可使用“检测更新”手动检查和下载。
• 下载被中断后，重新启动会再次检查最新发布版本；未完成或校验不符的旧文件不会用于安装。
• 补齐 Harness、兼容性探测和配置事务在请求中断、进程退出后的恢复与所有权处理。

本次为未签名 / macOS ad-hoc 的预发布验收包。Windows 使用 EXE，macOS 使用 DMG；ZIP 和 latest 元数据供自动更新使用。包内包含 Chromium、Rust Agent、Node/npm/pnpm。首次准备 Harness 的在线依赖不属于桌面离线安装。

来源与平台验证状态见各平台 _build.json、SHA256 清单和对应 GitHub Actions。自动化验证不等于完整业务、签名升级及所有平台的人工验收。

Nexus Launcher v0.1.3

Nexus Launcher 0.1.3 开发预发布。

本次更新

• 整理前端页面与 Agent API 职责，简化重复动作、错误处理和快照恢复事务。
• 收紧前后端状态类型，补充行为 A/B 对照与格式检查。
• Windows 每种架构合并为单个中英双语 EXE，保留 WebView2 离线安装器。

下载选择

• Windows x64：选择 dsh-nexus_0.1.3_windows_x64.exe。
• Windows x86：选择 dsh-nexus_0.1.3_windows_x86.exe。
• Windows ARM64：选择 dsh-nexus_0.1.3_windows_arm64.exe。
• macOS Intel：选择 dsh-nexus_0.1.3_macos_x64.dmg。
• macOS Apple Silicon：选择 dsh-nexus_0.1.3_macos_arm64.dmg。

每次只需下载匹配系统的一个安装包。Windows 每个架构只提供一个 EXE，运行后可选择简体中文或 English，不再按语言分开发包。Windows 包含 WebView2 离线安装器及 Node/npm/pnpm，体积大于单独的程序。Windows x86 内置 Node 22，其余内置 Node 24。macOS 最低版本为 13.5。

离线安装是发行要求：Windows 保持 offlineInstaller，不依赖安装时联网下载 WebView2。Nexus 自身可离线安装；Harness 的离线安装、恢复和运行需要预先准备对应离线材料，不能将空白机器上的首次在线获取依赖称为完全离线。

验证与限制

五个架构均通过编译、自动化回归、安装包资源哈希校验、Agent/CLI 通信及 GUI 进程启动检查。每个平台附同名前缀的 _SHA256SUMS.txt 和 _build.json，记录来源提交、构建编号、运行时和校验值。

CI 不代表完整 Harness 业务、升级、数据保留或用户交互真机验收。Windows 未商业签名；macOS 仅 ad-hoc 签名，未 Apple 公证。macOS 的 DSH 交互终端尚未实现。第三方许可材料已包含在安装包内，仍有 reviewRequired 项待核对。本版本不声明稳定版或各平台功能完全对等。