[1.0] Connect run views and deduplicated per-run live output

[AndreRatzenberger]

The dashboard needs to show actual execution records, and streams keyed only by agent name can mix parallel runs or duplicate history when views reopen.

Scope

• Wire a run list and details to the authorized history API using Context.task_id/run identity.
• Show agent, status, input/output references, timing and permitted errors for the selected run.
• Key logs/stream output by run and merge history/live data with stable identities instead of appending duplicate history.

Acceptance criteria

• Two simultaneous runs of one agent remain distinguishable in details, logs and live output.
• Reopening a view or reloading the browser does not duplicate already-shown history.
• Empty historical coverage and loading failures are honest UI states; supported interactions are keyboard accessible.

Boundaries

Network reconnect reconciliation and lifecycle buttons have separate tickets that build on this view.

References

• Parent topic: 🎉 [FEATURE] [1.0] UI Rework #374.
• Implementation dependencies: [1.0] Authenticate WebSockets and enforce per-recipient visibility #431, [1.0] Persist run history in SQLite independently of the dashboard #443.
• src/flock/frontend/src/components/details/RunStatusTab.tsx
• src/flock/frontend/src/components/details/LiveOutputTab.tsx
• src/flock/frontend/src/store/streamStore.ts