sync upstream main

[tarik02]

What Changed

• merged 3 commits from pingdotgg/t3code:main through 9dd425b2234c062b4767583e42d4b2c1aabab15d
• added conversation-content thread search across server, web, and mobile
• included the marketing Vercel deployment fix and the upstream user/maintainer documentation split
• preserved fork-specific goals, settings, and context-menu documentation

Why

Keep the fork aligned with the latest upstream changes while retaining fork-specific behavior.

UI Changes

No fork-specific UI changes. This PR inherits upstream UI changes.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model: gpt-5.6-sol
Harness: T3 Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 356acb9879

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid scanning every message on each search

When a user searches an environment with a large thread history, this leading-wildcard LIKE performs a full scan of projection_thread_messages; the window function must rank the entire matching set before the outer LIMIT 50 can apply. Both clients issue a new query after only 200 ms of typing, and the server uses a synchronous single SQLite connection, so these scans can stall unrelated projection and WebSocket work. Use an indexed search strategy such as FTS, or otherwise actually bound the scanned input rather than only the response.

AGENTS.md reference: AGENTS.md:L17-L19

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Match pnpm's actual native-preview directory names

On the cached pnpm installs this script is intended to repair, the virtual-store path is @typescript+native-preview@<version>/node_modules/@typescript/native-preview/lib/...; the glob instead expects hyphens after both native-preview segments. It therefore matches no backup files, so prepare still reaches effect-tsgo patch with all stale backups present and eventually fails at the documented 101-backup threshold.

Useful? React with 👍 / 👎.