scribe stores the language per USER, in its database - `PATCH /api/me`,
whose docstring says "the language choice follows the user, not the
browser". chrome's is a cookie, which is browser-local and therefore
strictly weaker for that case.
Adopting the shell would otherwise have quietly swapped a preference that
follows you to another machine for one that does not, and left two
switchers on the page disagreeing about the same setting.
`language_switcher=False` makes the shell stand down. Only the language
control: the theme toggle is unaffected, which the test pins, because
scribe's theme IS chrome's - the same localStorage key and the same three
values, so that one is a straight swap.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>