Merge upstream v0.0.46-nightly.20261009.2886

[mohan6623]

Claude Code resolved the conflicts in this merge of upstream v0.0.46-nightly.20261009.2886. Typecheck passed.

Merging this PR builds and publishes the update.

Claude's summary

The merge is resolved and staged, not committed. All conflict markers are gone, ensure:electron ran, and vpr typecheck passes after one fix.

Conflicts

1. apps/web/src/components/chat/ChatComposer.tsx, the prompt row's right padding.
   • The fork reserves room for the action buttons with three fixed sizes (pr-12, pr-20, pr-28). That width also decides when a long prompt moves the actions to their own row below it.
   • Upstream (fix(web): collapsed composer reserves room for wide send actions pingdotgg/t3code#17016) replaced the fixed sizes with the measured width of the actions plus 1rem, so wide buttons like the compact-before-send chip fit. It only measured while the composer is resting.
   • Combined: the fork's row ref, layout classes and pb-10 action row stay. Upstream's measurement moved earlier and now runs in both fork layouts (resting, or controls in the strip below the composer).
   • The measured width plus 16px now drives both the right padding (inline style instead of pr-*) and the action-row check. The fork's fixed sizes only cover the first frame, before the first measurement.
2. packages/provider-cursor/src/server/driver.test.ts, imports. Upstream moved this test out of apps/server and switched to import * as HttpClient from "effect/http/HttpClient". I kept that and added HttpClientResponse the same way, because the fork's Cursor usage test needs it.

Fix outside the conflicts: typecheck failed in apps/web/src/components/chat/ComposerUsageStrip.tsx. Upstream removed getDriverOption from providerDriverMeta, so the fork's usage strip now uses providerClients.get(driver)?.label, as other upstream code does.

Other checks

• The lockfile merged without conflict; I ran vp install anyway.
• vp test run src/server/driver.test.ts in packages/provider-cursor: 2 tests pass.
• ChatComposer.tsx and ComposerUsageStrip.tsx have no unit tests, so I couldn't run any for the web change. The composer layout change is untested; checking it means opening the composer in the app.

Two untracked files, claude-summary.md and conflicted-files.txt, were already in the repo root. I left them alone.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.