fix: add null check for messageService and improve ZodError type safety

Author: 0xbbjoker

src/environment.ts

@@ -29,8 +29,8 @@ export async function validateTelegramConfig(
     return telegramEnvSchema.parse(config);
   } catch (error) {
     if (error instanceof z.ZodError) {
-      const errorMessages = (error as any).errors
-        .map((err: any) => `${err.path.join('.')}: ${err.message}`)
+      const errorMessages = error.issues
+        .map((err) => `${err.path.join('.')}: ${err.message}`)
         .join('\n');
       console.warn(`Telegram configuration validation failed:\n${errorMessages}`);
     }

src/messageManager.ts

@@ -706,7 +706,13 @@ export class MessageManager {
 
       // Call the message handler directly instead of emitting events
       // This provides a clearer, more traceable flow for message processing
-      await this.runtime.messageService!.handleMessage(this.runtime, memory, callback);
+      if (!this.runtime.messageService) {
+        logger.error('Message service is not available');
+        throw new Error(
+          'Message service is not initialized. Ensure the message service is properly configured.'
+        );
+      }
+      await this.runtime.messageService.handleMessage(this.runtime, memory, callback);
     } catch (error) {
       logger.error(
         {