Generate prototypes based on WIP spec with pending decisions

[olaservo]

Context

Generate prototypes based on WIP spec with pending decisions.

Note: main purpose is to help with firming up specs, so the code itself may be replaced after spec refinement.

Original spec PR: #945

Implementation PRs (Stacked)

PR	Branch	Description	Status
#1027	v1.5/main	Core package + CLI, WEB, TUI implementations (v1 parity)	Merged
#1023	v2/core/inspector-core	Core package (reusable MCP logic, no React)	Draft
#1022	v2/ui/mantine	Full Mantine UI with MCP SDK integration	Merged
#1011	v2/ui/features	Client features UX (inline queue, testing profiles)	Merged

Related

• spec: Add client features UX patterns (sampling/elicitation) #1011 - Client features UX spec (inline queue, tree view, testing profiles)
• Inspector V2 Data Spec #983 - Data spec discussion (storage implementation)
• Evaluate SDK middleware for history/tracing #1024 - Evaluate SDK middleware for history/tracing

Merge Order

1. spec: Add client features UX patterns (sampling/elicitation) #1011 (spec) - Client features UX patterns
2. feat(core): add @modelcontextprotocol/inspector-core package #1023 (core) - Inspector core package
3. feat(client): add Mantine UI with MCP SDK integration #1022 (UI) - Mantine UI
4. Client features PR (implements spec: Add client features UX patterns (sampling/elicitation) #1011 patterns)

[cliffhall]

I commented on #1022 that I would like to decouple the decision of InspectorClient vs inspector-core approaches to the logic and state management from the actual UI implementation.

To that end, it might be a good idea to take a stab at building the components in isolation, and not integrated with the SDK.

We might want to look into StoryBook. It'd be cool to craft components with zero concern about the protocol and application logic being there and working order plus a particular server running.