Guide terminal-required setup and channel configuration instead of leaving dead ends

Problem

The Windows Hub setup experience can still lead users to terminal-only steps for chat-channel configuration and other Gateway configuration. The product should complete the step in-app when possible, or provide an explicit guided handoff rather than leaving a user or agent to infer commands.

Desired outcome

A first-time user can understand every remaining terminal requirement, perform it safely, and return to a verified ready state.

Definition of done

• Inventory first-run and channel-setup paths that require terminal input.
• Add a guided in-app path, or a terminal handoff containing the exact command, why it is needed, expected result, and return-to-app verification.
• Distinguish Gateway connected from ready for mobile/channel use in the completion state.
• Add functional/UI coverage for the handoff and return path.

Related

• #843 tracks the broader goal that first-time users reach a working node without manual steps; this issue narrows the terminal/channel handoff seam.
• The PCMag report observed that Telegram setup still required opening a terminal and pasting a command: https://www.pcmag.com/opinions/microsoft-thinks-openclaw-is-the-future-of-windows-my-testing-says-otherwise

Start by inventorying the Windows Hub first-run and channel-setup paths that currently require terminal input, then inspect the completion state that reports Gateway connectivity. Add a guided in-app flow or an explicit terminal handoff with the command, purpose, expected result, and return verification; done includes distinguishing Gateway connected from channel-ready and adding functional/UI coverage for both paths.