[deep-report] Apply console.Format* helpers to top high-traffic bare stderr calls in pkg/cli #31044

Problem

The Repository Quality Improvement Report (#31022) found 685 bare fmt.Fprintln(os.Stderr, ...) / fmt.Fprintf(os.Stderr, ...) calls in pkg/cli that bypass the project's console.Format* formatting layer. Users see plain unstyled output where the rest of the CLI shows emoji prefixes and color.

Suggested Fix (top-3 high-impact, single PR)

1. pkg/cli/compile_file_operations.go:74 — fmt.Fprintln(os.Stderr, err.Error()) → console.FormatErrorMessage(err.Error()). This runs on every per-file compile error; visible to every contributor.
2. pkg/cli/compile_file_operations.go:174 — fmt.Fprintln(os.Stderr, "Watching for file changes") → console.FormatProgressMessage(...) or FormatInfoMessage.
3. pkg/cli/add_interactive_engine.go:77 — fmt.Fprintf(os.Stderr, "Using coding agent: %s\n", ...) → console.FormatInfoMessage(...). Currently inconsistent with the formatted FormatInfoMessage at line 83 in the same function.

Leave the remaining 682 sites for follow-up work; this scoped PR establishes the pattern.

Suggested Agent

copilot-swe-agent — straightforward search-and-replace with import addition.

Estimated Effort

< 1 hour.

Source

Repository Quality Improvement Report — CLI Output Consistency (2026-05-08).

Generated by DeepReport - Intelligence Gathering Agent · ● 18.1M · ◷

• expires on May 10, 2026, 3:20 PM UTC