Files
Michael Neale 6abd561c6a desktop: show where relay-mesh inference runs in the activity panel
Buzz shared compute agents gave no indication of where their inference
actually executes. Add a small indicator to the Activity panel header,
e.g. 'Shared compute · Qwen3 8B · 3 nodes', with a full-sentence tooltip.

- New read-only mesh_availability Tauri command exposing the existing
  member-verified, freshness-filtered MeshAvailability (serve targets +
  models) that discovery already computes for routing. Stubbed for
  non-mesh builds.
- meshInferenceLocation.ts derives the label from availability + the
  agent's model ref: distinct node counting (deviceId/endpointId, so one
  node serving two models counts once) and Rust-parity @main-revision
  model matching. Explicit / auto-routed / no-live-nodes states.
- useMeshInferenceLocation polls availability (60s vs the 45s relay
  heartbeat) only when the agent's provider is relay-mesh; returns null
  for non-mesh agents and while availability is unknown, so the header
  renders nothing rather than a guess.
- E2E mock bridge answers mesh_availability with the matching shape.
2026-07-21 14:11:13 +10:00
..