[Bug] Regression: New hotkey split ignores existing "Container" mode setting

[oblominsk]

Issue #276 implemented separate hotkeys for Word vs. Sentence/Container, which is a great feature. However, the implementation introduces a regression for users who previously configured "Container" as their default mode.

The Conflict:

Before #276: Users could set a permanent default mode (Word / Sentence / Container). If I chose "Container", the extension remembered and used it.
After #276: The new hotkey logic defaults Word translation to pair with Sentence, ignoring the user's existing "Container" preference.
Impact:

Users with "Sentence" setting → No visible change.
Users with "Container" setting → Configuration reset. Their workflow is broken without consent.
Expected Behavior:
The new hotkey split should inherit the existing saved preference:

If defaultMode === 'Container' → Word hotkey should pair with Container.
If defaultMode === 'Sentence' → Word hotkey should pair with Sentence.
Why this matters:
This is a backward compatibility issue. Loyal users who configured the tool for their workflow now have to reconfigure it manually. The new logic should respect the old setting, not override it.

Please fix this conflict to preserve user preferences.

[nkoji21]

@oblominsk
I can't reproduce it like in the video. Is the problem still happening?

Screen.Recording.2026-03-11.at.23.25.43_minify.mp4