chore: sync upstream main

[tarik02]

What Changed

• Merged 39 upstream-only commits through pingdotgg/t3code@1a003e383.
• Adopted upstream changes for the default sidebar, project settings, usage dashboards, thread environment selection, browser history, and mobile thread controls.
• Preserved fork goals, provider launch environment handling, progressive thread history, release channels, and protocol extensions across the changed code.
• Moved progressive thread history controls to General > Experimental after upstream removed the Beta settings page. The legacy sidebar keeps middle-click archive.

Why

Actualizes the fork to current upstream while keeping fork-specific behavior where the same settings, server, and UI code changed.

UI Changes

This includes upstream UI changes and the settings/sidebar integration described above. Screenshots were not captured because browser verification was not requested.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c0325fdf20

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

Resolve usage homes from provider instances

When a Codex or Claude instance uses an instance-specific homePath, CODEX_HOME, or CLAUDE_CONFIG_DIR, its sessions are written outside the legacy homes resolved here. Since this reads only settings.providers.codex and settings.providers.claudeAgent and ignores settings.providerInstances and their environments, the Usage page silently omits activity from additional work/personal instances; enumerate the effective transcript homes of the configured instances instead.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Report transcript read failures as partial coverage

If a transcript directory exists but a subtree is unreadable, or a listed JSONL file disappears or cannot be opened, the reader swallows the error and returns no files/records, yet this unconditionally reports the source as ok. In those permission and transient-I/O scenarios the dashboard presents an incomplete total as authoritative rather than using the already-defined partial/failed statuses; preserve an error signal from the walk/read and reflect it in the source status.

Useful? React with 👍 / 👎.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	10.5 KiB	10.5 KiB	+27 B (+0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	4.8 KiB	4.8 KiB	+24 B (+0.5%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.7 KiB	5.7 KiB	+3 B (+0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	50.3 KiB	50.3 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	10.5 KiB	10.5 KiB	+29 B (+0.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	4.8 KiB	4.8 KiB	+9 B (+0.2%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.7 KiB	5.7 KiB	+20 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	51.1 KiB	51.1 KiB	+44 B (+0.1%)	66.4 KiB	✅
Claude	Live turn messages	9	10	+1 (+11.1%)	21	✅

Baseline: 2cdcc31 · PR result: c0325fd · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 76.2 KiB
• Claude decoded thread snapshot: 76.6 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.