Problem
The current Dashboard does not expose all artifact families supported by the Runtime. In the current UI, the sidebar shows:
- Home
- Handoff
- Memory
- Experience & Skills
- Usage
However, there is no dedicated Dashboard entry for Topic Memory, Profile, or Prompt configuration. This makes backend capabilities difficult to discover and prevents users from inspecting or managing artifacts that are already supported by the Server/API.
The attached user screenshot shows the current artifact navigation state.
Expected behavior
The Dashboard should provide a discoverable view for every supported artifact family, or clearly explain when a family is API-only. At minimum, the UI should expose or link to:
- Memory
- Topic Memory
- Experience
- Skill
- Handoff
- Profile
- Prompt configuration
- Usage/diagnostics
Topic Memory should show active topics, revisions/publications, source lineage, and processing status. Prompt configuration should show auto/custom mode, effective instructions, and the configured scope.
Acceptance criteria
- Dashboard navigation reflects the artifact families advertised by the Server capabilities/API.
- Topic Memory is inspectable without requiring direct API calls or SQLite access.
- Profile and Prompt configuration have either dedicated views or explicit, documented API-only status.
- Empty states and disabled capabilities are represented clearly instead of silently omitting the artifact.
Problem
The current Dashboard does not expose all artifact families supported by the Runtime. In the current UI, the sidebar shows:
However, there is no dedicated Dashboard entry for Topic Memory, Profile, or Prompt configuration. This makes backend capabilities difficult to discover and prevents users from inspecting or managing artifacts that are already supported by the Server/API.
The attached user screenshot shows the current artifact navigation state.
Expected behavior
The Dashboard should provide a discoverable view for every supported artifact family, or clearly explain when a family is API-only. At minimum, the UI should expose or link to:
Topic Memory should show active topics, revisions/publications, source lineage, and processing status. Prompt configuration should show auto/custom mode, effective instructions, and the configured scope.
Acceptance criteria