fix(server): import transcripts with oversized tool records

[Yash-Singh1]

What Changed

• Updated transcript scanning and provider adapters to handle oversized tool records during imports.
• Simplified related MCP, settlement, VCS, sidebar, and mobile outbox handling and removed obsolete tests and UI state.
• Preserved attachment upload blocking until uploads are ready while continuing to allow offline queuing.

Why

Transcript imports could fail when tool records exceeded the previous assumptions about record size. This change makes imports resilient to oversized records while removing stale queued-message behavior and keeping mobile task submission state consistent.

UI Changes

• Removed queued-message indicators from mobile thread lists.
• Updated mobile composer actions and labels to distinguish connected sends from offline queued tasks.

Screenshots are not included because the primary fix is server-side and the UI adjustments remove obsolete state rather than introduce a new visual flow.

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the production transcript-import path substantially: oversized files become eligible, raw I/O limits increase to 4 GiB, and a new streaming parser and record-selection layer governs what is retained. The new runtime complexity and default import-policy change warrant human review.

Not approved because:

• Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[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	13.6 KiB	13.6 KiB	−50 B (−0.4%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.5 KiB	−48 B (−0.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.1 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.1 KiB	7.1 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+5 B (+0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b0c923 · PR result: ce68b7c · 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: 113.9 KiB
• Claude decoded thread snapshot: 114.6 KiB

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

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.