[Task][RFC]: Complete the Desktop execution frontend journeys

[huangruiteng]

Outcome / 目标

完成 Desktop 双执行入口的用户旅程。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.

Canonical design: RFC. Roadmap: S1/S4/S5/S12, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.

Current boundary

Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.

Desktop, attached-session integration and managed runtime components are shipped in parts. Current App/session work is active; source-level support is not a clean-install or packaged runtime acceptance result.

Work remaining

• Complete connection, runtime/model readiness, useful execution, correction, stop and recovery for the explicitly supported attached and managed profiles.
• Use existing configuration and session owners; present effective provider/model, actual activity and actionable unsupported/unavailable states.

Ownership and ongoing work

#4114 owns bounded computer use and must not expand this task into unrestricted desktop automation. Reuse #5130/#5139 and the session-mode, App conversation and manager trackers; no parallel frontend rewrite.

Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.

Acceptance

• A clean release-package installation reaches a useful result and independent CLI readback on the advertised profile.
• Restart/update/rollback, stale binding and unavailable credentials/runtime assets preserve commitments without starting another executor.
• Default/off paths and explicit user model choices remain intact; each host/OS claim has its own evidence.
• Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.

Starting points and delivery boundary

• apps/desktop/loopx-control-plane
• apps/presentation/dashboard
• docs/integrations/runtime-connector-catalog.md

Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.