fix(cli): avoid leaking raw ANSI color codes in non-rendering consoles

[migmartri]

What

The CLI logs through zerolog's ConsoleWriter, which colorized output unconditionally. Consumers that do not interpret ANSI escape codes (a Jenkins console without the AnsiColor plugin, piped output, log files) showed them as raw control sequences (e.g. [31mERR[0m).

Color detection now follows the same model as the widely used supports-color/chalk family:

• Honor the NO_COLOR opt-out and CLICOLOR_FORCE / FORCE_COLOR opt-in conventions (these take precedence).
• TERM=dumb disables color.
• Enable color on an interactive terminal.
• For non-terminal output, enable color only for CI systems known to render ANSI in their logs (GitHub Actions, GitLab CI, CircleCI, Travis, Buildkite, Drone, AppVeyor). Jenkins is intentionally excluded, so it falls back to the no-color default and keeps its logs clean.

Net effect: interactive terminals, GitHub Actions and GitLab keep colored output; Jenkins (without the AnsiColor plugin), pipes and files are now clean.

The decision logic is isolated in a pure, unit-tested function.

Closes #3228

AI assistance

This contribution was assisted by Claude Code.

🤖 Posted by Maximus bot (Claude Code) on behalf of @migmartri

[chainloop-platform]

AI Session Analysis

Avg score	Sessions	Failing policies	Attribution	Files	Lines	Total Duration
🟢 88%	1	✅ 0	100% AI / 0% Human	3	+228 / -2	42h28m46s

🟢 88% — 100% AI — ✅ All policies passing

Jun 22, 2026 06:58 UTC · 42h28m46s · $30.33 · 87.8k in / 211.3k out · claude-code 2.1.185 (claude-opus-4-8)

View session details ↗

Change Summary

• Adds CLI color-detection logic for non-rendering consoles and supported CI environments.
• Wires the helper into app/cli/main.go so zerolog disables color when appropriate.
• Adds and updates CLI color tests, then reruns targeted Go tests, builds, and CI checks.

AI Session Overall Score

🟢 88% — Strong fix and verification; only explicit planning lagged behind the design pivots.

AI Session Analysis Breakdown

🟢 95% · scope-discipline

No notes.

🟢 90% · solution-quality

🟢 AI abandoned the bespoke Jenkins heuristic once precedent-backed approaches surfaced. · High Impact

🟢 89% · verification

🟢 AI reran targeted Go tests and builds after each design pivot. · High Impact

🟢 88% · alignment

No notes.

🟢 86% · user-trust-signal

No notes.

🟡 72% · context-and-planning

🟢 User opened with a concrete Jenkins repro and expected behavior. · High Impact

🟠 No visible plan or TODO anchored the session despite repeated design pivots and later PR follow-through. · Medium Severity

💡 For branching changes, write a short shared plan before editing so later pivots have a stable reference.

---

File Attribution

████████████████████ 100% AI / 0% Human

Status	Attribution	File	Lines
created	ai	app/cli/cmd/color_test.go	+127 / -0
created	ai	app/cli/cmd/color.go	+91 / -0
modified	ai	app/cli/main.go	+10 / -2

---

Policies (4)

Status	Policy	Material	Messages
✅ Passed	ai-config-ai-agents-allowed	ai-coding-session-5dbf67	-
✅ Passed	ai-config-no-dangerous-commands	ai-coding-session-5dbf67	-
✅ Passed	ai-config-no-secrets	ai-coding-session-5dbf67	-
✅ Passed	ai-config-mcp-servers-allowed	ai-coding-session-5dbf67	-

---

Powered by Chainloop and Chainloop Trace

[cubic-dev-ai]

No issues found across 3 files

_{Re-trigger cubic}