fix(filters): use eq for --name so run/trace list name filtering works

[Palash Shah (Palashio)]

Problem

langsmith run list --name <x> (and trace list --name <x>, which shares the same filter flags) returns HTTP 400 for any value:

querying runs: POST .../api/v1/runs/query: 400 Bad Request
{"detail":"Comparison comparator=<Comparator.SEARCH: 'search'> attribute='name' value='...' multi=False not accepted."}

internal/cmd/filters.go built the clause as search(name, %q), but the backend runs/query validator does not accept the SEARCH comparator on the name attribute — only eq. So the --name filter is completely non-functional. It also contradicts the flag's own help, which documents it as exact match.

Fix

One-line comparator change: emit eq(name, %q) instead of search(name, %q). eq is both what the backend accepts and what the flag already promises. Value interpolation (%q quoting) is unchanged. Updated the two tests that asserted the old search(name, …) output.

Verification

• go build ./... + go test ./internal/cmd/ pass.
• Built the binary and ran it against a live project:
  • before: run list --name ChatAnthropicWithOpenAIFallback → HTTP 400
  • after: returns the matching runs, all named exactly ChatAnthropicWithOpenAIFallback (exact match, no 400)

🤖 Generated with Claude Code