feat(desktop): onboard experimental direct peer hosts

[M4n5ter]

English

Summary

Add the Desktop vertical slice for the experimental direct-peer Runtime Host transport:

• manage the remote peer listener through the existing SSH management channel;
• keep SSH as the recovery path and create a separate disabled Direct profile;
• expose bounded status, routes, and coordination-peer configuration in Desktop;
• ship and verify the native peer client and Rust notices in Desktop artifacts.

This PR is stacked on #3919. Refs #3842.

Verification

• npm run build
• npm run lint
• npm run format:check
• npm --workspace @maka/desktop run typecheck
• Runtime Host suite: 1,255 passed, 9 skipped
• CLI suite: 514 passed
• Desktop suite: 1,559 passed
• release policy, packaged-resource, ASF header, Astryx inventory, Cargo notice, and Clippy checks
• Desktop E2E against a managed Linux Host: enable the peer listener, add and activate the separate Direct profile, open an existing remote Session, admit a Turn through Direct, restore SSH, and remove the experimental profile

简体中文

概要

为实验性的 Runtime Host direct-peer transport 补齐 Desktop 端到端切片：

• 通过现有 SSH 管理通道管理远端 peer listener；
• 保留 SSH 恢复路径，并创建独立且默认停用的 Direct profile；
• 在 Desktop 中展示有界状态、路径与 coordination peer 配置；
• 在 Desktop 产物中打包并验证 native peer client 与 Rust notices。

本 PR stack 在 #3919 之上。关联 #3842。

验证

• npm run build
• npm run lint
• npm run format:check
• npm --workspace @maka/desktop run typecheck
• Runtime Host 测试：1,255 通过，9 跳过
• CLI 测试：514 通过
• Desktop 测试：1,559 通过
• release policy、packaged-resource、ASF header、Astryx inventory、Cargo notice 与 Clippy 检查
• 在受管 Linux Host 上完成 Desktop E2E：启用 peer listener、添加并激活独立 Direct profile、打开既有远程 Session、通过 Direct 准入一个 Turn，随后恢复 SSH 并移除实验性 profile

UI evidence / 界面证据

Managed Host status and Direct peer controls / 受管 Host 状态与 Direct peer 控制：

SSH recovery profile preserved beside the experimental Direct profile / SSH 恢复 profile 与实验性 Direct profile 并存：

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex implemented, tested, and documented the change under the contributor's direction. The contributor remains responsible for final review and merge.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No