Summary

Make mobile-device pairing easy to discover from the Control UI's primary navigation and Quick Settings.

Problem to solve

The pairing flow added in #94672 is currently available only inside the Devices card on the Nodes page. That card sits below the longer execution-approval and binding controls, so users can reasonably search Settings and the main UI without finding it.

Proposed solution

• Add a subtle phone action to the persistent lower-left sidebar footer.
• Add a clear Mobile app row to Quick Settings.
• Open the same app-level QR setup dialog from the sidebar, Quick Settings, and existing Nodes action.
• Keep pending pairing-request feedback live while the dialog is open.

Alternatives considered

• Move the existing Devices card higher on Nodes: improves one page but remains undiscoverable from the main UI and Settings.
• Add only a Settings link: better searchability, but pairing is an infrequent global action that also benefits from a persistent, compact shortcut.

Impact

Affected: operators connecting the iOS app or another mobile client.

Severity: medium usability issue; the supported flow exists but is difficult to locate.

Frequency: every first-time mobile setup.

Consequence: users assume web pairing is unsupported or require documentation/support to find the Nodes card.

Evidence/examples

The original feature is #94672. Current source and rendered-UI inspection confirm the only trigger is inside the Devices card on Nodes, below unrelated controls.

Additional information

The action still requires administrator access and uses the existing device.pair.setupCode Gateway method.