Greptile Summary

This PR fixes demand prompt themes ignoring the color=false / NO_COLOR settings by adding an early-return to get_theme() that falls back to a fully unstyled theme whenever console::colors_enabled_stderr() is false. A new no_color_theme() helper explicitly clears every color-bearing field on Theme::new() to work around residual ANSI specs in demand's nominal no-color constructor.

• get_theme() now gates colored-theme selection behind console::colors_enabled_stderr(), which is already driven by Settings::get() applying color, NO_COLOR, and CLICOLOR to the console state.
• no_color_theme() exhaustively resets all 20 style fields (including focused_button, blurred_button, cursor_style, and the breadcrumb slots) plus force_style = false on Theme::new().
• A regression test asserts that every cleared field reports no fg/bg color after the call.

Confidence Score: 5/5

The change is narrowly scoped to theme selection; the worst outcome of a regression is unstyled or over-styled prompt output, not data loss or a crash.

Settings::get() already calls console::set_colors_enabled_stderr() before get_theme() checks that flag, so the color state is always up to date when the guard runs. no_color_theme() clears every style field the PR description identifies as problematic, and the test asserts all of them.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "test(ui): cover unstyled prompt theme fi..." | Re-trigger Greptile}