feat(conversation): add conversation list command

[lmjabreu]

Overview

Adds tdc conversation list so you can find a DM or group conversation by who's in it, its title, or whether it's a 1:1 or a group. There was no way to list conversations from the CLI before: conversation unread shows only unread, and conversation with <user> finds only your 1:1 with one person.

It reuses the existing plumbing rather than adding new infrastructure: the shared fetch (getAllConversations → getConversationsByState) and renderer (listConversationsWithUser → renderConversationList) were generalised, and conversation with now calls the renamed helpers with no behaviour change. Flag shapes follow the family: a value-enum flag per mutually-exclusive dimension (--kind, --state), like channel list --state and search --type, with active-by-default lists and archived as opt-in.

DM content search stays out of scope; it already works via tdc search --type messages / --conversation / --to and just needs better docs (separate change).

Usage

tdc conversation list                       # active DMs and groups, newest first
tdc conversation list --kind group          # only groups (3+ people)
tdc conversation list --participant "Jane"  # conversations including these users
tdc conversation list --name "release"      # title substring match
tdc conversation list --state archived --json

Flags: --workspace, --participant, --name, --kind <group|direct>, --state <active|all|archived> (default active), --snippet, --limit, --json / --ndjson / --full.

Test plan

• type-check, lint:check, check:skill-sync, and test (815 pass, 13 new) all green.
• Live read-only smoke test: kind / participant / name / state / limit filters return the expected rows (including a 117-person group); an unmatched --name prints the empty message; an ambiguous --participant surfaces a clean AMBIGUOUS_USER error.

For the maintainer

getConversations isn't server-paginated (same as getThreads / getChannels), so this is one fetch plus client-side --limit. Any server-side cap on conversation count for very large workspaces? Not a blocker; with --include-groups already relies on the same single-call behaviour.

[doistbot]

This PR adds tdc conversation list with kind, participant, name, state, and limit filters, nicely reusing the existing conversation fetch and render plumbing.

Few things worth tightening:

• Participant resolution misses removed users: --participant resolves against the active workspace roster only, so --state archived --participant "Former User" fails even when that archived conversation exists. Resolve participants with includeRemoved: true so archived DMs/groups are findable.
• Avoidable full-workspace user read in JSON mode: The list path always builds a workspace-wide user-name map via renderConversationList, even for --json/--ndjson without --full where those names are filtered out. Short-circuit machine-readable output before name expansion.
• Concurrency / fail-fast: getConversationsByState and resolveUserRefs are independent and could run concurrently with Promise.all, or resolveUserRefs could be moved first to fail fast on an ambiguous or invalid participant before fetching conversations.
• Type safety and defaults in shared helpers: kind and state on ConversationListOptions are typed as plain string rather than exported unions, and getConversationsByState() defaults state to 'all' (the most expensive option) — making state required and passing 'all' explicitly from with.ts would avoid a future footgun.

I also included a few optional follow-up notes in the details below.

Optional follow-up notes (2)

• [P3] src/commands/conversation/helpers.ts:25: kind and state are typed as plain strings here even though the command constrains them to a fixed set of values. That weakens the handler contract compared with nearby patterns like archiveFilter?: ArchiveFilter and forces list.ts to re-narrow them, where bad non-Commander inputs currently fall back to undefined/active instead of failing. Export shared unions for these fields and use them on ConversationListOptions so callers can't pass arbitrary strings.
• [P3] src/commands/conversation/helpers.ts:80: Giving getConversationsByState() a default of 'all' hides the most expensive behavior behind an omitted argument. Both current callers already know which state they want (list wants active, with --include-groups wants all), so making state required and passing 'all' explicitly from with.ts would keep that choice at the call site and avoid an easy future footgun where a new caller accidentally fetches archived conversations too.

_{Share Feedback • Review Logs}

[scottlovegrove]

Needs doistbot's feedback addressing before merging, but all good from my side.

[doist-release-bot]

🎉 This PR is included in version 1.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀