fix(integrations): address round-2 review

- airtable: coerce upsert typecast as string-aware boolean (string "false" no longer truthy)
- microsoft-excel: format_range surfaces precise partial-state error when fill PATCH fails after font (no atomic font+fill endpoint in Graph)

Author: waleedlatif1

apps/sim/blocks/blocks/airtable.ts

@@ -379,7 +379,7 @@ Return ONLY the valid JSON array of record ID strings - no explanations, no mark
               ...baseParams,
               records: parsedRecords,
               fieldsToMergeOn: parsedFieldsToMergeOn,
-              ...(typecast != null ? { typecast: Boolean(typecast) } : {}),
+              ...(typecast != null ? { typecast: typecast === true || typecast === 'true' } : {}),
             }
           case 'delete':
             return { ...baseParams, recordIds: parsedRecordIds }

apps/sim/tools/microsoft_excel/format_range.ts

@@ -189,7 +189,13 @@ export const formatRangeTool: ToolConfig<
         if (!fillResp.ok) {
           const errorText = await fillResp.text().catch(() => '')
           const detail = parseGraphErrorMessage(fillResp.status, fillResp.statusText, errorText)
-          throw new Error(`Failed to apply fill color: ${detail}`)
+          // Graph has no single endpoint to set font and fill together, so they are
+          // two PATCHes. The font already succeeded here; surface that explicitly so
+          // the partial state is clear. Formatting is idempotent — re-running with only
+          // the fill color safely finishes the operation.
+          throw new Error(
+            `Font formatting was applied, but the fill color update failed: ${detail}. Re-run with only the fill color to finish.`
+          )
         }
         fillApplied = true
       }