Summary
Make the outcome of resolved items visible and traceable. Today a resolved (done/dropped) item just moves to the collapsible "Resolved" section showing its final body — there's no easy way to see which run resolved it or what changed.
Proposal
For a resolved item, surface: the run that resolved it, what happened, and links to the evidence.
- Research (done): the findings that were integrated + the research run that did it (session log, KB files touched / diffs, the commit).
- Wishlist (done): what was delivered + the dreaming run/commit.
Mechanism options (decide in design)
- App-side only: show the commit that flipped
status: (git log for the file) + a link to the session log around that timestamp / the commit's diff.
- Session-side (scout-plugin) richer metadata: when a session resolves an item, write resolution metadata to the item (e.g.
resolved_by: <run-id>, a short "delivered/findings" summary) that the app renders directly.
Notes
- Cross-repo (app display + possibly session-written metadata). Pairs with the "Do now" issue (a focused run is the cleanest run↔item link).
Part of the Wishlist/Research tabs backlog (follows #40).
Summary
Make the outcome of resolved items visible and traceable. Today a resolved (done/dropped) item just moves to the collapsible "Resolved" section showing its final body — there's no easy way to see which run resolved it or what changed.
Proposal
For a resolved item, surface: the run that resolved it, what happened, and links to the evidence.
Mechanism options (decide in design)
status:(git log for the file) + a link to the session log around that timestamp / the commit's diff.resolved_by: <run-id>, a short "delivered/findings" summary) that the app renders directly.Notes
Part of the Wishlist/Research tabs backlog (follows #40).