chore: sync 5 upstream commits (March 15)

[gabrielMalonso]

What Changed

Synced 5 upstream commits from upstream/main:

• Focus ring unification (fix(web): unify focus ring styles across sidebar and app pingdotgg/t3code#1079): Unified focus ring styles across sidebar and app components for consistency
• Node engine compatibility (fix: tighten node engine range for node:sqlite compat (#206) pingdotgg/t3code#1096): Tightened Node.js version range for better sqlite compatibility, added NodeSqliteClient fallback
• Scroll to bottom pill (feat(web): add scroll to bottom pill in chat view pingdotgg/t3code#619): Added scroll-to-bottom pill/button in chat view to improve UX when new messages appear
• Documentation fix (Fixed Typos in Agents.md pingdotgg/t3code#1120): Fixed typos in AGENTS.md
• Gitignore update (chore: add .idea/ to .gitignore pingdotgg/t3code#1077): Added .idea/ (IDE configuration) to .gitignore

Also created local upstream-sync skill for automated upstream monitoring and changelog management.

Why

Keeps the fork aligned with upstream improvements while maintaining fork-specific features (sub-threads, skills, Claude integration). The scroll-to-bottom pill and focus ring improvements enhance user experience, while the Node.js version tightening ensures better compatibility.

Checklist

• This PR is small and focused (5 cherry-picked commits + skill scaffolding)
• I explained what changed and why
• Changes are tested (cherry-picks applied cleanly with one moderate conflict resolved)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 982415409b

ℹ️ 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]

Use user-input response state for pending input panel

Pass the user-input in-flight IDs here instead of approval in-flight IDs. ComposerPendingUserInputPanel uses respondingRequestIds to disable options while thread.user-input.respond is pending, but this prop now receives respondingRequestIds (approval state), so user-input prompts stay interactive during submission and can trigger duplicate responses; additionally, an unrelated approval request can incorrectly mark a user-input prompt as responding.

Useful? React with 👍 / 👎.