Implement proper async/await handling in test-logging-formats.js

[phrazzld]

Summary

Update the test script to use proper promise handling best practices to avoid potential unhandled promise rejection warnings.

Current Implementation

// test-logging-formats.js line 97
testLoggingFormats().catch(console.error);

Issues

• Uses .catch() without proper await handling
• May cause unhandled promise rejection warnings in newer Node.js versions
• Script could exit before promise resolves in some environments

Recommended Solution

(async () => {
  try {
    await testLoggingFormats();
  } catch (error) {
    console.error('Test execution failed:', error);
    process.exit(1);
  }
})();

Alternative Solutions

• Use top-level await if Node.js version supports it
• Add explicit void to indicate intentional fire-and-forget: void testLoggingFormats().catch(console.error);

Tasks

• Replace current promise handling with proper async/await pattern
• Add proper error handling and exit codes
• Test script execution in different Node.js environments
• Verify no unhandled promise rejection warnings

Benefits

• Cleaner, more predictable script execution
• Better error handling and reporting
• Compliance with modern JavaScript best practices
• Elimination of potential Node.js warnings

Acceptance Criteria

• Script uses proper async/await pattern
• No unhandled promise rejection warnings
• Clear error messages and appropriate exit codes
• Compatible with supported Node.js versions

Priority

Low - code quality improvement with minimal functional impact

Labels

Technical debt, code quality, Node.js best practices