Summary

This PR updates the WG Log Engine package from v2.0.0 to v2.2.0 and configures all log elements to use only local timezone format, removing UTC timestamps from log output.

Changes Made

Package Update

• Updated @wgtechlabs/log-engine from ^2.0.0 to 2.2.0 in package.json
• This provides access to enhanced format configuration options introduced in v2.2.0

Local Timezone Configuration

• Added LogEngine configuration in src/index.ts early in application startup
• Applied configuration before any LogEngine calls are made (before environment validation)
• Configured format settings to use only local timezone:

  LogEngine.configure({
      format: {
          includeIsoTimestamp: false,  // Removes UTC timestamps
          includeLocalTime: true       // Keeps local time format
      }
  });

Before vs After

Before (mixed UTC + local):

[2025-07-12T16:21:58.388Z][4:21PM][INFO]: Environment configuration validated successfully
[2025-07-12T16:21:58.402Z][4:21PM][WARN]: Rate limit exceeded during reply

After (local timezone only):

[4:21PM][INFO]: Environment configuration validated successfully
[4:21PM][WARN]: Rate limit exceeded during reply

Impact

• All LogEngine calls throughout the application now use consistent local timezone formatting
• Log output is cleaner and more readable with shorter timestamps
• Maintains all logging functionality while improving user experience
• No breaking changes to existing logging behavior

Testing

• ✅ Application builds successfully
• ✅ Environment validation shows local time format
• ✅ All log levels (debug, info, warn, error, log) use local format
• ✅ Configuration is applied consistently across all modules

This change addresses the requirement to update the WG Log Engine package and apply local timezone settings for all log elements.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.