Would a minimal, read-only GUI front-end for qmd collections be useful to anyone?

Hi — first of all, qmd is a fantastic tool. The hybrid BM25 + vector + rerank pipeline with everything local is exactly what I (and apparently a lot of agents) needed.

I'd like to gauge interest in something before building it, and this seemed like the right place to ask.

The idea: a minimal, read-only GUI front-end on top of a qmd index

qmd is CLI/MCP-first, which is perfect for agents, but for day-to-day human use the interaction is: run a query in the terminal, read snippets, then open the file elsewhere. #547 ("Do you mind if I tauri this?") touched on this but didn't go anywhere, so I wanted to ask openly:

Would a minimal "document browser" for qmd collections be useful to anyone? Sketch:

• Browse collections and files that are in the index
• Open a markdown file with proper rendering (headings, code blocks, etc.)
• Search (hybrid BM25 + vector) with highlighted hits and jump-to-match in the rendered document
• Maybe: recently-changed view (what's new in the collection since last visit)

Constraints I'd hold myself to:

• qmd stays the engine — no reimplementation of indexing or search; the GUI would talk to qmd (CLI subprocess, SDK if available, or MCP), and the index remains fully compatible
• Read-only, minimal, fast; Tauri or similar lightweight shell
• Open source

So two questions:

1. Would this be useful to you, or is CLI + MCP genuinely all anyone needs?
2. If I build it, what's the recommended integration path — is there a stable SDK/API beyond the CLI surface, or is shelling out to the CLI / speaking MCP the intended way for third-party tools to consume qmd?

Not announcing anything — genuinely asking whether this is worth building before I spend the time. Silent-lurkers: if you'd use this, a on this issue helps.