[log] Enhanced debug logging for launcher.go

[github-actions]

Summary

Added strategic debug logging to internal/launcher/launcher.go to improve troubleshooting capabilities for backend server connection management.

Changes Made

Enhanced the existing logLauncher debug logger with 9 new logging calls at critical control flow points:

Connection Management

• GetOrLaunch: Added logging when connection not found in cache and needs to be created
• GetOrLaunch: Added logging after retrieving server config with type information
• GetOrLaunch: Added logging when starting connection goroutine
• GetOrLaunch: Added logging when startup timeout occurs

Session Management

• GetOrLaunchForSession: Added logging when checking session pool
• GetOrLaunchForSession: Improved clarity of "creating new connection" message

Lifecycle Operations

• ServerIDs: Added logging to show retrieved server IDs and count
• Close: Added logging at launcher closure start with connection counts
• Close: Added logging when launcher successfully closed

Design Decisions

1. Reused existing logger: The file already had logLauncher = logger.New("launcher:launcher") - reused it rather than creating a duplicate
2. No side effects: All logging arguments use existing variables without computation
3. Strategic placement: Focused on key decision points, state changes, and error conditions
4. Meaningful context: Each log message includes relevant parameters (serverID, sessionID, timeouts, counts)

Testing Notes

All new logging statements:

• Follow the pkg:filename naming convention
• Use structured format with key=value pairs for easy parsing
• Provide debugging context without duplicating user-facing messages
• Work with the existing DEBUG environment variable filtering

Enable with: DEBUG=launcher:* ./awmg --config config.toml

Quality Checklist

• Exactly 1 file modified (focused, single-file PR)
• No test files modified
• Reused existing logger (no duplicate logger declarations)
• Logger naming follows pkg:filename convention
• Logger arguments don't compute anything or cause side effects
• Logging messages are meaningful and helpful
• No duplicate logging with existing logs
• Import statements properly formatted (no changes needed)

AI generated by Go Logger Enhancement