Enable viewing, browsing, searching, updating LLM Wiki / Knowledge from web UI

[trisweb]

The support for the LLM wiki via skill and agent is great, however I'm craving the ability to browse and explore the data in this knowledge base more easily. Right now I sync it to Obsidian to do this, which works well, but would be convenient to have it right next to where it's being used. It doesn't need to be as full-featured as Obsidian, but the basics of browsing, search, and edit would be good.

[nesquena-hermes]

Thanks @trisweb — this is a reasonable ask, and the Obsidian-sync workaround is a useful data point on what users actually want from in-WebUI knowledge browsing.

A few notes on the surface area:

1. The KB plumbing is upstream, not WebUI. The LLM Wiki is implemented as a Hermes skill (llm-wiki) plus an agent-side knowledge-ingest flow — the actual storage lives under the agent's profile, not the WebUI's state directory. Browsing / searching it from the WebUI requires either (a) a new /api/wiki/* endpoint family that proxies to the agent's knowledge store, or (b) shipping a workspace-style file browser scoped to the wiki's markdown directory.

2. There's adjacent shape already. The Workspace panel can already preview markdown files — if your LLM Wiki lives under a registered workspace, you can browse its files with the existing btnWorkspacePanelToggle surface. Not the full "explore the knowledge base" experience you're describing, but a useful interim if you point a workspace at the wiki root.

3. The search piece is the harder part. The skill itself supports semantic and link-graph queries; surfacing those in the WebUI needs a dedicated panel (sidebar item like Memory/Kanban) plus a /api/wiki/search backend. That's a real feature, not a thin shim.

Labeling enhancement and assigning to Milestone 3 — Platform expansion since this needs new backend API surface alongside the WebUI panel. If you want to scope down to a "just preview LLM Wiki files via the Workspace panel" first slice, that's tractable in M2.

Useful next step would be: which of {browse, search, edit, real-time sync with Obsidian} is the most-painful gap for your use? That narrows the v1 scope.

[trisweb]

Makes sense, yes. The workspace tool is a reasonable workaround for now.

For a first version, a simple browser would be useful and a good slice of the wider functionality, giving us a place to expand abilities around the wiki over time. I think it's useful to have this represented as a top concept, however, perhaps combined with memories and knowledge in general (especially since that page is very related in concept, but very lightweight in current abilities).