Repository navigation
feat(ui): result viewer wiring for session summaries #112
Description
Description
Wire the Agent Manager result viewer to the shipped summary surface: list sessions' summaries via VaultStore.list_items(kind=SESSION_SUMMARY), detail view via SessionSummarizer.peek, refresh via collect(force=True).
Why
The summaries exist and are cached but have no user-visible entry point; this is the UI half of Agent Manager #4.
Scope
- Backend routes for list/detail/refresh
- Frontend result-view wiring
- Tests
Activity
Svagtlys commentedon Sep 30, 2026
Scope addition (from #108 review):
peek()cannot report staleness —SessionSummarycarriescovered_seqbut not the transcript's currentseq_max, so the viewer's only freshness check today iscollect()(an LLM call). Include a cheap accessor in this issue's scope: e.g.EventStore.max_seq(session_id)or a peek variant returning(summary, seq_max), so the UI can render a stale badge without regeneration.Svagtlys commentedon Oct 19, 2026
Needs triage — parked with the UI batch (same blockers as #43–59). The summary surface it wires (
VaultStore.list_items(kind=SESSION_SUMMARY),peek,collect(force=True)) is shipped and the backend routes half is genuinely buildable, but: (1) frontend styling direction (#7) is undecided, (2) #109 (participant-authored summaries) changes what the detail view displays (authorship provenance) — wire the UI after #109 lands to avoid rework, (3) it is now also the tracked home of #56 (folded here as duplicate). Suggested decomposition when unblocked: backend routes issue (no blockers) + frontend viewer (blocked on #7).