fix(i18n): detectBrowser assigns _locale directly, bypassing setter (post-init loadPath)

[ErickXavier]

i18n() browser detection sets _i18n._locale = browserLang directly (src/index.js ~519) instead of via the setter (i18n.js:97 → _loadLocale + _notifyI18n).

For the documented config-before-init ordering this is fine (init's blocking load runs afterward). But if NoJS.i18n({...}) is called after init() under loadPath, the detected locale's bundle is never fetched and watchers never fire → t() returns fallbackLocale/raw keys with no re-render.

Decide: either route detection through the setter, or explicitly document/enforce config-before-init. Surfaced by post-release review of v1.16.0. Severity: low (edge/altitude; may be wontfix).

[ErickXavier]

Fixed in PR #304 → #310. NoJS.i18n({loadPath,...}) called after the CDN auto-init now works: a post-init guard at the end of i18n() loads the resolved locale bundle (_loadI18nForLocale, deduped by cache) and notifies watchers; inline locales notify synchronously. The persisted-restore early return was restructured (localeRestored flag) so the guard runs on every path while persisted locale still wins over detectBrowser. Pre-init behavior unchanged. 4 new unit tests cover post-init loadPath, inline locales, pre-init no-op, and persisted-restore. Verification: Jest 2225/2225 (42 suites); e2e 1563 passed / 0 failed across chromium+firefox+webkit at --repeat-each=3; gzip 44,046 B. Merged to main in PR #310 (78a646c). Ships in the next release (v1.20.1).