Sidebar detail rows: structured Work/Tasks/Agents inspection (restored from #2694)

[Hmbown]

Restored from deleted issue #2694 because @aboimpinto had explicitly offered to take a focused pass. The old milestone-specific framing is intentionally removed here; this issue preserves the community-owned slice and the useful design direction.

Preserved contributor intent

@aboimpinto asked to take a focused pass and suggested splitting the work into two safer slices:

• first extract a structured sidebar/work display model;
• then add row-level detail popovers on top of that model.

That direction is valuable because it keeps lifecycle semantics out of sidebar.rs and makes the sidebar render a projection rather than infer workflow state directly.

Maintainer note

The original thread also noted that #2854 may already cover part of the row hover/popover behavior. Before opening implementation work, please inspect current crates/tui/src/tui/sidebar.rs, crates/tui/src/tui/app.rs, and existing sidebar tests so this becomes either:

• a narrow follow-up that fills real gaps; or
• a closure with evidence if the shipped implementation already satisfies the issue.

Acceptance target

Keep the compact Work/Tasks/Agents sidebar, but make truncated rows inspectable through structured, redacted detail metadata without moving workflow lifecycle policy into the rendering layer.

[Hmbown]

@aboimpinto I’m sorry: I was doing public issue cleanup to pull back broad Hunter-authored roadmap items and went overboard. The original #2694 was deleted even though you had taken the time to claim it and leave a strong design note.

I restored the useful thread here so your intent is not lost. I’m also treating your related command-boundary work in #2888 as priority 0.8.54 integration material, because it is exactly the kind of focused contributor work we want to preserve and build from.

[aboimpinto]

Thanks, Hunter. I appreciate you restoring this and for the support around the focused contributor work.

I’ll keep #2889 parked until the command-boundary refactor stack I started a few days ago is finished and stable (#2791 / #2870 / #2888). After that I’ll pick this up as an investigation-first pass: inspect the current sidebar/app code and tests, compare the shipped popover model against this acceptance target, and then either propose a narrow follow-up PR for real gaps or comment back with closure evidence if the current implementation already satisfies it.

We’ll do the best we can to keep this focused: preserve the compact Work / Tasks / Agents sidebar, keep workflow lifecycle policy out of rendering, and use structured, redacted row detail metadata for inspectable truncated rows.

Paulo Aboim Pinto