- Introduced automatic overlay opacity and gradient based on layer ID in BackgroundLayer component.
- Added disabled state to BackgroundUploader, preventing actions when disabled.
- Updated component CSS editor to handle disabled state, preventing changes when disabled.
- Modified Header and Layout components to manage background inheritance from the page layer.
- Improved Sidebar and Card components to respect background inheritance and layering.
- Refactored theme management to include default accent color and normalization functions.
- Enhanced AppearanceTab to manage accent color changes with debouncing and validation.
- Added UI feedback for inherited background layers in AppearanceTab.
- Added translation support for various text elements using `useTranslation`.
- Created default personality and emoji configurations to streamline setup.
- Updated step titles and descriptions to use translated strings.
- Improved validation messages to be translatable.
- Refactored loading and success/error messages for better user feedback.
- Enhanced UI structure for better readability and maintainability.
- Updated Japanese translations in config.json, core.json, prompts.json, and startup.json for improved clarity and accuracy.
- Added new Korean locale files for config.json, core.json, prompts.json, and startup.json to support Korean language users.
- Enhanced Chinese translations in core.json and startup.json to include missing resource not found messages and WebUI related texts.
r-dev already has [dependency-groups] with dev deps including pytest
and pytest-asyncio. Our branch had a different structure causing a
duplicate key error when merged. Align with r-dev's format.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Remove get_bot_account("qq") fallback from all 4 sender paths
(plan L108/L208/L449: unknown platform = no account, never substitute QQ)
- Sender paths now error immediately if platform bot account is not configured
- Add detailed comments on filter_bot legacy fallback explaining why
global user_id match is needed (plan contingency L528 insufficient for
platform-tagged legacy rows like telegram+qq_account)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
