refactor(ui): consolidate output architecture with rich library and unified output_manager imports

[Copilot]

📥 Pull Request

✨ Description of new changes

Replace questionary.print() and prompt_toolkit.print_formatted_text() with rich.console.Console across all CLI output paths. Consolidates all output-related modules (fab_ui.py, fab_logger.py) into a single fab_output_manager.py facade with a consistent import alias across the entire codebase.

Output architecture consolidation

• src/fabric_cli/utils/fab_output_manager.py — Single OutputManager singleton facade that controls stdout, stderr, and debug log file output. All 107 source files now use one consistent import: from fabric_cli.utils import fab_output_manager as output_manager. Old aliases (fab_logger, fab_ui, utils_ui) are eliminated.
• src/fabric_cli/utils/console.py — Centralized Console instances with shared theme and reusable helpers (print_success, print_error, print_warning, print_info, print_error_panel, print_table, print_file_written)
• Module-level convenience functions (set_output_format(), set_mode(), print_output_format(), log_warning(), etc.) delegate to the singleton so call sites remain concise

Core changes

• src/fabric_cli/main.py — Single output_manager import replaces the previous triple import (fab_logger, fab_ui, output_manager function). Removed rich.traceback install in debug mode.
• src/fabric_cli/core/fab_interactive.py — Consolidated to single output_manager import, uses output_manager.set_mode() convenience function
• src/fabric_cli/commands/desc/fab_describe.py — Fixed broken imports that referenced deleted fab_logger and fab_ui modules

Color scheme

success=green, warning=yellow, error=red, info=cyan, fabric=#49C5B1, muted=grey62

Error output example

Before:

x get: [NotFound] Workspace not found

After:

╭──────────────────── ✘ Error ────────────────────╮
│ get: [NotFound] Workspace not found              │
╰──────────────────────────────────────────────────╯

Test changes

• tests/conftest.py — mock_questionary_print now patches OutputManager._safe_print instead of questionary.print
• tests/test_core/test_fab_interactive.py — Mock paths updated from utils_ui/fab_logger to output_manager
• tests/test_core/test_fab_context.py — Mock paths updated from fab_logger to output_manager
• tests/test_utils/test_fab_ui.py / test_fab_version_check.py — Assertions updated from mock inspection to capsys capture where appropriate
• tests/test_utils/test_console.py (new) — 19 tests covering all console helpers

Dependencies

• rich>=13.7.0 added to pyproject.toml and requirements-dev.txt

Original prompt

You are working in the fabric-CLI Python repository.

Your goal is to improve the CLI user experience using the Python rich library while keeping the behavior of the CLI unchanged.

Focus on the following areas:

1. Console UX Improvements

Enhance all CLI output using rich:
• Replace plain print statements with rich.console.Console.
• Use appropriate rich components where they improve clarity:
• Panel for summaries and important messages
• Table for structured outputs
• Syntax for code snippets
• Progress for long-running operations
• Status spinners for API calls or network operations
• Traceback for improved error stack traces
• Use consistent colors:
• success → green
• warnings → yellow
• errors → red
• informational → cyan or blue

Create a centralized console utility module if one does not exist (for example fabric_cli/utils/console.py) so the entire CLI uses the same Console instance.

2. Error Handling Improvements

Improve error messages so they are more helpful to users.
• Catch expected errors and display clear, actionable messages
• Use rich.panel.Panel for error summaries
• Display helpful suggestions when possible
• Use rich.traceback.install() for better stack traces in debug mode

Example improvements:

Instead of:

Error: request failed

Prefer something like:

❌ Request failed

Reason:
Authentication token expired

Suggested action:
Run fabric login and try again.

3. Logging Improvements

Improve logging output for both console and file logging.

Requirements:
• Keep the existing file log rotation configuration unchanged
• Introduce structured logging where helpful
• Console logs should use rich.logging.RichHandler
• File logs should remain plain text (for machine readability)

If useful, introduce a central logging configuration module.

Console logs should include:
• timestamp
• log level
• clear message formatting

4. CLI Feedback for Long Operations

Where operations take noticeable time (network calls, deployments, etc.):
• Add rich.progress.Progress
• Add rich.status.Status spinner while waiting

Example:

⏳ Fetching workspace list...
✔ Workspaces retrieved

5. Improve File Output UX

When the CLI writes files:
• Clearly inform the user where the file was written
• Use colored messages
• If the file already exists, display a warning before overwriting

Example:

✔ Configuration file written

Path:
~/fabric/config.yaml

6. Maintain Backwards Compatibility

Do not break existing commands or CLI arguments.

Changes should focus on:
• presentation
• usability
• logging
• error clarity

Avoid introducing breaking changes.

7. Code Quality

Follow repository standards:
• Keep functions small and readable
• Avoid duplicating logic
• Add type hints where missing
• Use existing project formatting (Black etc.)

8. Screenshots in the PR

In the Pull Request:
• Include before vs after screenshots showing:
• improved error messages
• rich formatted tables
• progress indicators
• improved logs

Place screenshots in the PR description to demonstrate the UX improvements.

9. Keep Dependencies Minimal

Only introduce rich as a new dependency if not already present. Avoid adding additional third-party libraries unless clearly justified.

⸻

If helpful, you may also introduce small reusable helpers such as:
• print_success()
• print_error()
• print_warning()
• print_table()

to standardize CLI output across the repository.

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[ayeshurun]

@copilot I don't want trace back, remove

[Copilot]

Removed the rich traceback install block (lines 34-38) in commit 09d5b34.

[ayeshurun]

@copilot In all files, make sure to import only once the output
Manager and modify all occurrences to use it.

[Copilot]

Done in 09d5b34. All 107 source files now use a single import: from fabric_cli.utils import fab_output_manager as output_manager. Duplicate imports within files (e.g. as fab_logger + as fab_ui) are consolidated. Also fixed fab_describe.py which was still referencing the deleted fab_logger and fab_ui modules.

[ayeshurun]

@copilot Like here - it should be output manager and not utils_ui

[Copilot]

Fixed in 09d5b34. This line is now from fabric_cli.utils import fab_output_manager as output_manager and the duplicate import was removed.

[ayeshurun]

@copilot Should be output_manager and not logger, here an all other occurrences

[Copilot]

Fixed in 09d5b34. All as fab_logger aliases replaced with as output_manager across the entire codebase. Added set_output_format() and set_mode() module-level convenience functions so the singleton doesn't need to be accessed directly.