Improved fog node visibility and transparency on the client

[philippzagar]

Problem

SpeziLLM implements a fog layer to dynamically discover fog nodes within the local network that host LLM execution environments. It then dispatches LLM inference requests to these nodes and streams the responses back to the SpeziLLM client, such as an iPhone.
The discovery and selection of fog nodes happens rather seamlessly as the SpeziLLM client app uses mDNS to discover the existing resources in the network and then connects to an arbitrary one.

However, at the same time, there is limited observability / transparency into how fog discovery and selection are performed. Currently, this process operates in a pretty much black-box manner, with either successful inference dispatches or an error.

Solution

In order to improve the transparency into the fog node discovery and selection, SpeziLLM should provide information about the currently connected node, the connection status, and the ability to switch the connection to other nodes.
As SpeziLLM mostly uses a conversational interface (chat-based) from SpeziChat for interacting with the model's responses, one might need to improve the flexibility of the the SpeziChat ChatView in order to enable these visibility features.
An easy observability implementation without adjusting the ChatView can be done by using the Views toolbar in order to provide users with buttons that trigger the respective observability Views as sheets or other form of display.

To enhance transparency in fog node discovery and selection, SpeziLLM should display details about the currently connected node, the connection status, and provide the ability to switch connections between nodes. Since SpeziLLM primarily uses the chat-based interface from SpeziChat for interacting with model responses, the ChatView may need to be made more flexible to incorporate these visibility features. Alternatively, a simpler observability implementation could use the Views toolbar to add buttons that trigger the relevant observability Views as sheets or other display mechanisms.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines