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>
This commit is contained in:
A 2026-02-12 03:24:30 -08:00 committed by GitHub
parent a550aecb22
commit 6c7ced54dd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
59 changed files with 69 additions and 69 deletions

View file

@ -61,7 +61,7 @@ echo ""
# 7. Start opencode interactively
log_step "Starting opencode..."
log_warn "To delete codespace later, run: gh codespace delete --codespace $CODESPACE --force"
log_info "To delete codespace later, run: gh codespace delete --codespace $CODESPACE --force"
echo ""
sleep 1