fix(server): thread search finds phrases inside quotes and their comments#22553

Problem

Thread search can't find a phrase inside a quote or its comment (https://git.cafe/pingdotgg/t3code/issues/22304). A quote is stored in the message text as an [Assistant quote](t3-citation://v1/…) link, and URLSearchParams encodes the quote and comment inside it: what are you talking about is stored as what+are+you+talking+about. Thread search matches that stored text, both through the message index and the fallback scan, so phrases with spaces never match, and accented, CJK and apostrophe words in a quote never match through the index. Single words do, including words from the quote's hidden prefix and suffix selection context, so a thread can show up for a word its reader never saw in it.

Change

• When ProjectionStore projects a message, it now stores search_text on orchestration_v2_projection_messages: assistantCitationsToPlainText(text), the helper the queued-message and stash previews already use. A quote becomes its text plus Comment: …, without the link or its hidden context. The column is NULL when that equals the stored text, so plain messages aren't stored twice. Every message.updated upsert rewrites it, so edits keep it current.
• Migration 082 adds the column, recreates the message search triggers, and backfills existing history. The backfill pages through messages whose payload contains t3-citation://, 500 at a time by message_id, and writes search_text only where the readable text differs; the update trigger re-indexes each message it changes.
• The search triggers come from the shared createMessageSearchTriggers, which now indexes search_text once the column exists. Migrations 069 and 074 are unchanged and, running before 082, keep indexing the stored text; a later migration that recreates the triggers through the helper keeps quote indexing instead of reverting it. Migration 082 recreates them through a new recreateMessageSearchTriggers. rebuildMessageSearch (t3 doctor, migrate-dev-db) indexes the same text.
• Thread search matches COALESCE(search_text, text), the check for short words outside ASCII included, and builds the snippet from the same value, through one messageSearchText helper, on the same reader-worker query.
• Migration id: 082. Main ends at 080, and another open PR (#28751) also adds 081, so this one takes the next free id.

Scope and approval

Refs https://git.cafe/pingdotgg/t3code/issues/22304. This fixes its matching half. @EtanHey reported it, traced both halves and suggested a derived search-text column written at projection time; this builds that.

Snippets come from the matched text, so a quoted match also shows readable text instead of the encoded link.

Verification

Linux (Ubuntu 26.04), in apps/server:

• New ThreadSearch.test.ts cases project a quote with hidden prefix and suffix words, find its accented, CJK, apostrophe and short Cyrillic words through the index, and rebuild the index. Quote and comment phrases match and the hidden words don't. After a second message.updated drops the quote, the comment phrase stops matching.
• 082_ProjectionMessageSearchText.test.ts migrates up to id 081 (main's set, which ends at 080), inserts a quoted message, a plain one, an invalid citation link, a non-string text, an accented quote and 501 quoted rows to cross a page, then runs only 082 and checks search_text and the index. A second case recreates the triggers through recreateMessageSearchTriggers, as a later migration would, and checks that a new quote is still indexed as it reads.
• With main f12bb6229c's ThreadSearch.ts, the two new ThreadSearch cases fail (2 failed, 29 passed). On this branch, ThreadSearch, 082, 077, 069, Migrations, reconcileV2PreviewMigration, DatabaseMaintenance and ProjectionStore pass, 111 of 111.
• With the trigger helper forced back to the stored text, both 082 cases and the index case in ThreadSearch fail.
• vp run check:changed: format, lint, knip, typecheck and tests pass.

Real app, on every client: each run starts on main with an isolated state of test threads, where I selected a line of an agent reply (from the dev Replay provider), chose Cite, added the comment what are you talking about, moved the quote into a new thread with quiet silver lantern, and sent it. Then I stopped main and started this branch on the same state. It ran only the new search-text migration, which filled search_text for that quoted message. Searching for the comment finds nothing on main; after the upgrade it finds the quoting thread with a readable snippet.

Web (dev servers, Chromium):

A quote sent after the upgrade goes through the projection path and is found by its comment.

https://gist.githubusercontent.com/only21mil/9900a9292b7d0ac07e57580b0abdd405/raw/cb5ed48448bac8b79beee211fcf74e22cf06c5df/pr22553r3-branch-new-quote.png

Desktop (Linux Electron under Xvfb, vp run dev:desktop of main and of this branch):

Mobile (T3 Code Dev client on an Android 16 emulator and an iOS 26.5 simulator, against main's and this branch's dev servers):

Not checked:

• Desktop on macOS and Windows. They run the same server and web UI.
• Quoted-phrase and hidden-context searches in the app: the Replay provider gives every thread the same reply, so those words also match the replies there. The unit tests cover both.
• Migration time on a large database. The backfill test crosses one 500-row page.

Prior PRs: https://git.cafe/pingdotgg/t3code/pulls/22391 fixed the snippet only and was closed as a duplicate of this PR. No open or closed PR changes the matching. https://git.cafe/pingdotgg/t3code/pulls/16858 (open) edits the same query for qualifiers and may need a small rebase.

Generated with Claude Opus 5.5 in T3 Code Nightly

Fixes pingdotgg/t3code#22304