API keys follow the active organization, and Russian gains LLM routing

The console's API key list and new keys are scoped to the organization you are working in, and Russian requests can now route the LLM stage.

Keys created from the console are stamped with the active organization when one is selected, and the key list shows that organization's keys. Keys created without an active organization stay organization-unscoped and, like keys created before this change, are visible in all of their owner's organizations. API callers authenticating with OAuth tokens see all of their keys, unchanged.

Russian, previously transcription-only, is accepted on the LLM stage: selection rides the English board's ranking (the models themselves are multilingual, and no language parameter is forwarded upstream). Russian text-to-speech stays refused with unsupported_language - no vetted Russian voices exist.

Usage and activity views remain user-scoped for now.