Greptile Summary

This PR fixes a stale dropdown display bug where the language selector showed "English" after a page refresh even though the correct non-English locale was loaded and applied to the UI. The root cause is that I18nManager initializes this.locale to "en" and then fires an async setLocale() call from its constructor; any render that executes before that promise resolves captures "en" from i18n.getLocale(). The .value binding on <select> set the DOM value imperatively during that first render, locking in English before the subscriber-triggered re-render could correct it.

Changes:

• Removes .value=${currentLocale} from the <select> element.
• Adds ?selected=${loc === currentLocale} to each <option>, which is Lit's idiomatic boolean-attribute binding and is re-evaluated on every re-render. When the async locale load completes, notify() fires, the parent re-renders via I18nController, and the correct option is marked selected.
• The fix is minimal (2 lines changed, 1 file) and aligns with standard Lit best practices for driving <select> state from reactive/async data.

Confidence Score: 5/5

• This PR is safe to merge — the change is minimal, targeted, and uses the correct Lit idiom for reactive select state.
• The fix is a two-line change that replaces an imperative .value binding with the idiomatic ?selected boolean-attribute pattern. The root cause described in the PR description matches exactly what the I18nManager source shows: locale starts as "en" and is updated asynchronously, so any render before the async load completes captures the wrong value. The ?selected binding is re-evaluated on every re-render, which correctly picks up the locale once the subscriber-triggered re-render fires. No regressions or edge cases were identified.
• No files require special attention.

_{Last reviewed commit: 84833d5}