Draft: Feat/user profile

What is the profile command in a Corpus Client? A "corpus client" is usually a tool or interface used to query, manage, or interact with a large body of data (the corpus)—such as medical records, documents, or a knowledge base.

Adding a profile command (e.g., typing /profile in a CLI or chat interface, or calling a client.get_profile() method) generally serves a few core purposes:

Context Retrieval: It fetches the details of the currently authenticated user, patient, or system entity.

State Verification: It allows the user to quickly check their current settings, roles, or permissions before running complex queries against the corpus.

Personalization: If the client is an AI or query agent, knowing the "profile" helps tailor the search results to that specific user's domain.

Why this MR and What is the Use? The Goal (Why): Previously, the client might have only been able to send queries and get raw data back. This MR bridges a gap by adding identity and context management directly into the client interface.

The Use (Value): It vastly improves the developer and user experience. Instead of having to log into a separate dashboard or make manual API calls to check user details, someone can simply run the profile command right where they are already working.

closes issue #4 (closed)