P0: Workbench must display and control the broker-selected Mac binding

[100yenadmin]

P0 problem

Workbench already lets an authenticated user select a customer/VM for pairing, but it does not consume or display a durable broker-selected Mac-control device/grant binding. When one connector identity is active in multiple customer scopes, the app cannot truthfully say which route is connected.

Parent: #686
Broker authority producer: electricsheephq/electric-sheep-website-dashboard-6158a244#661
Runtime enforcement: electricsheephq/electric-sheep-website-dashboard-6158a244#660

Scope

• Extend the existing customer/Mac target selector; do not create a separate competing picker.
• Load the broker-validated selected binding for the authenticated desktop session.
• Auto-display exactly one valid binding; require a visible authorized choice when the broker reports multiple_active_customer_grants.
• Support choose, switch, clear, and revoke with explicit confirmation and customer/VM-readable labels.
• Clear stale readiness/tool state whenever session, selected customer, binding version, grant, VM, or account changes.
• Keep local capability posture, broker binding, network/ACL authority, runtime health, and live tool proof visibly distinct.

Acceptance criteria

• Fixtures cover one valid scope, two active customer scopes, switch, clear, revoke, stale/expired binding, wrong account, offline, ACL denial, and session change.
• The app never chooses a cross-customer route by newest timestamp.
• Ambiguity remains not ready and names the next user action without exposing customer IDs, grants, private network identity, connector material, or raw diagnostics.
• Existing pairing, Port team chat capability propagation #602 customer/VM target visibility, CUA-primary/Peekaboo-fallback, TCC, stop/revoke, kill switch, audit, and Matt behavior remain intact.
• Installed-app proof verifies the visible selected connection and sign-in/account transition behavior.

Proof boundary

Source/PR and installed-app UI proof do not establish agent-tool consumption, live VM-to-Mac control, public distribution, or customer readiness.

[coderabbitai]

🔗 Related PRs

#391 - Restore beta3 Mac pairing baseline [merged]
#403 - fix: recover Mac control installed app states [merged]
#417 - Fix Mac pairing reconnect session gate [merged]
#668 - feat(workbench): guide pristine Mac network recovery [merged]
#669 - fix(mac): broker pristine-Mac network enrollment [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!