[log] log: add debug logging to health monitor

[github-actions]

Summary

Adds 6 meaningful debug log calls to internal/launcher/health_monitor.go using the existing logHealth logger (launcher:health namespace).

Changes

File modified: internal/launcher/health_monitor.go

Function	Added logging
NewHealthMonitor	Log creation with configured interval and max restart failures constant
Stop	Log when stop is initiated (before blocking on doneCh)
run	Log goroutine startup with interval
checkAll	Log total server count each health check cycle
checkAll	Log when a recovered server's failure counter is reset (server came back healthy)
handleErrorState	Log when max restart failures reached and restart is silently skipped

Why These Additions?

The health monitor is a critical background component that manages server recovery. Without debug logging, it's difficult to answer questions like:

• When was the health monitor created and with what interval?
• Is the goroutine actually running?
• How many servers are being checked each cycle?
• Did a server recover and when?
• Why is a failed server not being restarted (max failures reached)?

Quality Checklist

• Exactly 1 file modified
• No test files modified
• Reuses existing logHealth logger (no new declaration needed)
• Logger naming follows pkg:filename convention (launcher:health)
• No side effects in log arguments
• Logging messages are meaningful and helpful
• No duplicate logging with existing logs
• 6 focused logging calls (within 3-7 guideline)

Generated by Go Logger Enhancement · ● 8.4M · ◷

[Copilot]

Pull request overview

Adds debug-level logging to the launcher health monitor to improve observability during periodic health checks and server auto-restart behavior.

Changes:

• Log health monitor creation with configured interval and restart-failure threshold.
• Add debug logs around lifecycle events (stop initiation, goroutine start).
• Add debug logs during health-check cycles (server count, recovery/reset, skip-restart at max failures).

Show a summary per file

File	Description
internal/launcher/health_monitor.go	Adds launcher:health debug logs for monitor lifecycle and health-check activity.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Copilot]

The failures >= maxConsecutiveRestartFailures branch is documented as “stay silent” and the PR description says the restart is “silently skipped”, but this adds a debug log that will fire on every health-check tick for a permanently-failed server (potential log spam when DEBUG enables launcher:health). Consider removing this log, or only logging once at the moment the threshold is reached (and keep the comment/PR description consistent).