fix: Improve error message handling in tree and flatten commands

This commit modifies the error handling in the `tree_command` and `flatten_command` functions to print error messages without Rich markup parsing. The changes ensure that unexpected errors are displayed clearly, even when they contain markup-like characters. Additionally, a new test has been added to verify that exceptions with such characters are handled correctly.

Author: Shorzinator

src/contextcraft/main.py

@@ -176,7 +176,8 @@ def tree_command(
     except typer.Exit:
         raise
     except Exception as e:
-        console.print(f"[bold red]An unexpected error occurred during tree generation: {e}[/bold red]")
+        console.print("[bold red]An unexpected error occurred during tree generation: [/bold red]", end="")
+        console.print(str(e), markup=False)
         raise typer.Exit(code=1) from e
 
 
@@ -279,7 +280,8 @@ def flatten_command(
     except typer.Exit:
         raise
     except Exception as e:
-        console.print(f"[bold red]An unexpected error occurred during code flattening: {e}[/bold red]")
+        console.print("[bold red]An unexpected error occurred during code flattening: [/bold red]", end="")
+        console.print(str(e), markup=False)
         raise typer.Exit(code=1) from e
 
 

tests/test_main.py

@@ -436,3 +436,24 @@ def test_flatten_integration_with_config_excludes(tmp_path: Path):
     assert "# --- File: docs/index.md ---" not in content
     assert "print('ignored')" not in content  # Content from ignored.py
     assert "# Docs" not in content  # Content from docs/index.md
+
+
+# --- Test for exceptions with markup-like chars in the message ---
+
+
+class ProblematicError(Exception):
+    def __str__(self):
+        return "Error with [square brackets] and maybe a backslash \\!"
+
+
+@mock.patch("src.contextcraft.tools.flattener.flatten_code_logic", side_effect=ProblematicError())
+def test_flatten_command_handles_exception_with_markup_chars(mock_flatten_error, tmp_path: Path):
+    """Test flatten command handles exceptions with markup-like chars in the message."""
+    result = runner.invoke(app, ["flatten", str(tmp_path)])
+    assert result.exit_code == 1
+
+    # Verify the original error message is printed (now without markup parsing)
+    assert "Error with [square brackets] and maybe a backslash \\!" in result.stdout
+    # Check that no MarkupError occurred and the core message is there:
+    assert "An unexpected error occurred during code flattening:" in result.stdout
+    mock_flatten_error.assert_called_once()