fix: prefer content over parts in Gemini Interactions Turn parsing

Author: jpr5

src/gemini-interactions.ts

@@ -50,6 +50,7 @@ interface InteractionsContentBlock {
 
 interface InteractionsTurn {
   role: string;
+  content?: InteractionsContentBlock[];
   parts?: InteractionsContentBlock[];
 }
 
@@ -100,17 +101,18 @@ export function geminiInteractionsToCompletionRequest(
         // Turn[] format
         for (const turn of req.input as InteractionsTurn[]) {
           const role = turn.role === "model" ? "assistant" : turn.role;
-          if (!turn.parts || turn.parts.length === 0) {
+          const blocks = turn.content ?? turn.parts;
+          if (!blocks || blocks.length === 0) {
             if (role === "user" || role === "assistant") {
               messages.push({ role: role as "user" | "assistant", content: "" });
             }
             continue;
           }
 
           // Check for function_call or function_result parts
-          const funcCallParts = turn.parts.filter((p) => p.type === "function_call");
-          const funcResultParts = turn.parts.filter((p) => p.type === "function_result");
-          const textParts = turn.parts.filter((p) => p.type === "text");
+          const funcCallParts = blocks.filter((p) => p.type === "function_call");
+          const funcResultParts = blocks.filter((p) => p.type === "function_result");
+          const textParts = blocks.filter((p) => p.type === "text");
 
           if (funcCallParts.length > 0) {
             // Assistant tool call message