List outbound threads — EVERY reply is a row (record vs. attention: the lanes are attention routes, not storage routes). Filters compose:

• status: one board-parity status.
• priority_only: P0 rows (priority flag + reason + Slack-ping ref).
• aging: >24h since the prospect's last message and the ball is still in our court (new_reply / draft_ready / approved).
• needs_review: reply required — the prospect spoke last on an open thread (not answered, not no_action / call_booked, not Not Interested).
• follow_up: we spoke last on an open thread and it's been quiet 3+ days (the row's follow_up says 3d / 7d / 1mo).
• seat / campaign: exact match.
• q: free-text contact search (name / email / company / campaign / profile URL, case-insensitive substring) — composes with the rest; the tab sends it alone to search ALL statuses and lanes.
• lane: gtm | recruiting — the EFFECTIVE lane (stored pin from triage/operator, else the recruiting_campaigns derivation); omitted = both lanes.
• owed: threads with an OPEN deliverable commitment ("Waiting on us", WO-F) — any lifecycle status, most-overdue first.

Default sort is the needs-review order: newest prospect activity first. Each row carries its latest draft, lead context, tag, and slack_ping_ref.