[ON_HOLD] Vercel SDK migration V4 -> V5

[andresgutgon]

What?

Yesterday I started applying blindly the codemods linked in the Migration guide and I realized this is going to change things in our

1. Gateway api
2. Our client sdks

I'm trying a different approach here to just change the translation layer between latitude and Vercel SDK without affecting what users send to our servers if possible

TODO

• Fix responseMessages in both legacy and new stream manager. Same as the format. Reuse.
• FORMAT correctly messages in streaming. Instead of content.output use content.result and instead of content.input use content.args old names to keep compatibility.

Things that changed (And affect us)

I'll try to gather here a list of things that we need to change

• Use providerOptions instead of providerMetadata for input we already were doing this for input.
• reasoning part has be renamed to text I think this one affect us even is for their UI sdk
• Use @api-sdk/rsc instead of ai/rsc
• stream reasoning event renamed to reasoning-delta
• maxTokens parameter has been renamed to maxOutputTokens we need to keep supporting maxTokens so users with existing prompts using this prop don't have to change it. I'll do a test for this.
• usage tokens renaming We need to handle this. Now Vercel SDK returns totalTokens when the steps finish.
• tool definition parameters now are called inputsSchema
• File parts changes
• Tool Property Changes: args/result → input/output
• Step Control: maxSteps → stopWhen Check if we PASS maxSteps to vercel SDK
• temperature default removal. We need to decide if Latitude add a default temperature.
• Review changes in Amazon Bedrock and others at the end of migration guide

[andresgutgon]

Apparently is possible to pass reasoning using Vercel SDK v4. We'll put these changes on hold for now.