Release Notes for routatic-proxy v0.4.10

This release focuses on refining scenario routing logic to improve model selection accuracy and reduce unnecessary traffic to complex models. Key changes include narrowing scenario keywords to prevent false positives and enhancing test coverage for critical routing paths.

Breaking Changes

• Narrowed scenario keywords: Removed over-broad keywords like "error", "debug", "build", and "bash" from complex scenario detection. This change may affect routing behavior for messages containing these terms, requiring users to adjust their prompt patterns if they previously relied on these keywords for complex routing.

New Features

• Improved scenario detection accuracy: Enhanced keyword filtering in complex scenario detection to prevent false positives while maintaining routing for true architectural work.

Bug Fixes

• Fixed false positive routing: Resolved issue where routine coding tasks containing common technical terms were being incorrectly routed to complex models (#111).

Improvements

• Enhanced test coverage: Added new test cases for scenario routing edge cases and improved existing tests for reliability.

Documentation

• Updated README: Added documentation about scenario keyword usage and routing behavior changes.

Chores

• Refactored routing logic: Improved code structure for better maintainability and performance.