v0.3.2 - Rich Console Color Scheme & Output Improvements (2025-12-22)¶
What Changed?¶
This release improves the user experience by standardizing Rich Console color markup across all example scripts and CLI utilities. The create_run_summary.py script now validates output files early to avoid unnecessary data processing, displays messages with consistent color coding (cyan for info, green for success, red for errors, yellow for warnings), and shows user-friendly relative paths in all output. A comprehensive color scheme guide has been added to CLAUDE.md for developers.
What's New¶
Early File Validation in create_run_summary.py¶
What it does:
The script now checks if the output run_summary.toml file already exists at the very beginning of execution, before loading and analyzing data. This prevents unnecessary processing when the file already exists.
How to use it: Simply run the script as before. If the output file already exists, you'll see an error message with a helpful deletion command:
uv run create_run_summary.py ./20251221_run126
If run_summary.toml exists, you'll see:
Error: examples/20251221_run126/run_summary.toml already exists
Please delete the existing file and run again:
rm examples/20251221_run126/run_summary.toml
Unified Rich Console Color Scheme¶
What it does: All example scripts and CLI utilities now use a consistent color markup system:
- [cyan] for information and progress messages
- [green] for success and completion messages
- [red] for errors and failures
- [yellow] for warnings and cautions
How to use it: The colors are automatically displayed when running scripts. Colors appear in stderr (logs) while data output remains in stdout for clean shell redirection.
Installation¶
Quick Start¶
# Get the release
git checkout vX.Y.Z
# Setup
task env:setup
# Run CLI
uv run kazunoko --help
What's Different from the Last Version?¶
✅ Added¶
- Rich Console color markup standardization across all example scripts
- Early output file existence validation in
create_run_summary.py - Rich Console Color Scheme documentation section in CLAUDE.md
- User-friendly error messages with deletion instructions
🔧 Changed¶
- Moved output file validation to the beginning of
create_run_summary.pyexecution for efficiency - Changed verbose output from stdout to stderr for better log separation
- All messages in
create_run_summary.pynow use Rich color markup for consistency
🐛 Fixed¶
create_run_summary.pyno longer overwrites existingrun_summary.tomlfiles
Is It Safe to Upgrade?¶
Backward Compatible: Yes
- All existing APIs and CLI commands remain unchanged
- Color output is optional and won't affect script automation (only visible in terminal)
- Early file validation prevents accidental overwrites without changing any existing successful workflows
Tests Passed¶
- ✅ All commits passed Commitizen checks
- ✅ Version bump successful (0.3.1 → 0.3.2)
- ✅ Code follows project style guidelines and color scheme standards
Release Details¶
- Date: 2025-12-22
- Version: v0.3.2
- Files Changed: 3 (create_run_summary.py, CLAUDE.md, pyproject.toml)
- Commits:
4d4c6c7docs: add Rich Console Color Scheme section to CLAUDE.mda1733festyle: unify Rich console color markup across all messages in create_run_summary.pye0d9baerefactor: move output file check to early validation and add color to error message2f947d7fix: add existing file check to create_run_summary.py
Next Steps¶
- Continue standardizing color markup across all CLI commands in
src/kazunoko/cli.py - Consider adding more output format options (e.g., ANSI color configuration)
- Expand unit tests for example scripts and Rich Console output