feat(web): command palette search matches thread IDs

[saphid]

What Changed

The command palette (⌘K) now matches threads by their ID. Pasting a thread ID from "Copy thread ID" into the palette search surfaces that thread directly, which previously returned nothing unless the ID happened to appear in the title, branch, or message content.

Scope: web client only (apps/web command palette). Mobile's thread search screens, the server-side content search (searchThreads), and wire contracts are unchanged. Desktop inherits the change through its bundled web UI.

Why

Thread IDs are already a first-class user-facing handle (the thread action menu exposes "Copy thread ID"), and support workflows revolve around pasting an ID to find a thread. The palette's buildThreadActionItems builds its search haystack from title, PR relations, project title, branch, and content snippets, but never the ID, so an exact ID query missed every thread.

The fix is one line plus a test: add thread.id to the search terms, last so pasted IDs never outrank title matches for shared substrings. No upstream issue or Ideas discussion exists for this; this PR body carries the motivation.

Verification

• New test surfaces threads when the query is their ID, without outranking title matches in apps/web/src/components/CommandPalette.logic.test.ts: builds two threads where one matches by ID and the other by a title that embeds that ID, queries with an uppercase, whitespace-padded ID, and asserts both surface with the title match ranked first.
• pnpm exec vp test run apps/web/src/components/CommandPalette.logic.test.ts: 29 passed, 0 failed.
• pnpm run typecheck in apps/web: passed (0 errors).

No screenshots: this changes which results a query returns, not any layout or styling. A live client capture pass was attempted in an isolated environment but the fresh-install web client could not establish its connection on either this branch or the merge-base, so evidence is the focused test above.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (skipped: no visual/layout change; see Verification)

Implementation used enablers/xlarge (GLM) in T3 Code. Independent review used GPT 6 Astra (high) via CLIProxyAPI (the configured Fable 5.1 reviewer was unavailable at the gateway; its one test-coverage suggestion is applied in 415f4a5).

Summary by CodeRabbit

• New Features

  • Thread IDs can now be searched in the command palette.
  • Title matches continue to rank ahead of matches found by thread ID.

• Tests

  • Added coverage confirming that searching by a thread ID surfaces the corresponding thread actions.

[macroscopeapp]

Approvability

Verdict: Approved at 415f4a5

Macroscope's review found this PR approvable — The PR adds thread IDs to the existing command-palette search terms with no changes to schemas, workflows, or production defaults. Its small, isolated runtime change is covered by a focused ranking and matching test.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 42b6c0b8-fe45-4fd6-81ee-0878736658d0

📥 Commits

Reviewing files that changed from the base of the PR and between d8c8733 and 415f4a5.

📒 Files selected for processing (1)

• apps/web/src/components/CommandPalette.logic.test.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

Thread action items now include thread IDs in their search terms. Tests verify ID-based matching and preserve title-match ordering.

Changes

Thread ID command palette search

Layer / File(s)	Summary
Add thread ID search terms and validation apps/web/src/components/CommandPalette.logic.ts, apps/web/src/components/CommandPalette.logic.test.ts	buildThreadActionItems adds each thread ID as the final search term. The test verifies case- and whitespace-insensitive ID matching and title-match ordering.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to 415f4

Thread IDs are searchable in the web command palette with title-first ordering preserved. No merge-blocking risk was identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description clearly explains what changed, why it changed, scope, verification results, and why screenshots are not applicable. The checklist is substantially complete.
Title check	✅ Passed	The title is concise, specific, and accurately identifies the main change: command palette searches now match thread IDs.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[saphid]

On the docstring-coverage warning: this repo's convention is no per-function docstrings; intent lives in the test name and the code comment on the searchTerms ordering. Leaving as-is to match upstream style.