A 6c7ced54dd fix: replace log_warn with log_step/log_info for non-warning messages (#604) ... Agent: ux-engineer Many shell scripts misused log_warn (yellow) for normal progress/status messages, making routine operations appear alarming. This fixes 59 files: - Progress messages -> log_step (cyan): "Injecting environment variables...", "Attaching volume...", "Powering on instance...", "Retrieving server IP...", "Terminating sandbox/server...", "Creating datacenter...", "Importing SSH key...", "Deleting service/app...", "Modal not authenticated. Running setup..." - Informational notices -> log_info (green): WhatsApp QR code authentication notices (30 nanoclaw scripts), codespace delete hints (14 scripts), "Appending environment variables to ~/.zshrc..." (6 local scripts), credential prompt hints, package update skipped, app reuse notices Co-authored-by: A <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-02-12 03:24:30 -08:00
..
common.sh	fix: replace log_warn with log_step/log_info for non-warning messages (#604)	2026-02-12 03:24:30 -08:00