Show loops in per-agent track (like subagents)

[sebbo2002]

Loops currently have little UI presence — they're only accessible via CLI (paseo loop run/ls/inspect/logs/stop) and WebSocket RPC. Since loops behave like subagents (they create worker and verifier agents iteratively), they should appear in the per-agent track above the composer, just like the existing subagent track.

Tapping a loop row should open a detail panel where users can see the loop status, iteration history, and open the worker/verifier agents. A stop button should be available in both the track row and the detail panel.

Match loops to agents by cwd: loop.cwd === agent.cwd (both are absolute resolved paths). No triggeredByAgentId exists today since loops are CLI-triggered, not agent-triggered (no MCP tool exists for loops, this might be a long term improvement).

Further Ideas

• MCP tool for loops — currently agents cannot trigger loops directly, they use the paseo cli via paseo-loop skill. Adding this in the future would enable triggeredByAgentId association instead of cwd matching.
• Loop creation UI — allow creating loops directly in the UI
• Per-iteration drill-down — detail panel links out to worker/verifier agent panels for deep inspection rather than embedding them.