Ask for custom-word translation language

[pirajoke]

Summary

• ask learners which language custom words should be translated into before accepting an import
• persist this preference separately from the study language, interface language, and native language
• apply the selection to text, photo, PDF, voice, practice, and Mini App custom-word lists
• add migration 0022 and clear the preference during privacy erasure
• localize the flow across all eight supported interface languages

Verification

• RED: 7 regression tests failed for the intended behavior (4 failures, 2 errors)
• GREEN: custom vocabulary suite 22/22 passed
• affected suites: 166 passed (3 skipped)
• full suite: 1046 passed (3 skipped)
• migration upgrade/downgrade round trip passed
• Python compileall and JavaScript syntax check passed
• git diff --check passed

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-09T09:42:59.782558Z	43a90a7	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 43a90a7bb2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Shorten the Alembic revision identifier

On the repository's PostgreSQL 16 path, Alembic stores revision identifiers in its default alembic_version.version_num VARCHAR(32) column, but this identifier is 43 characters long. After executing the migration, Alembic will fail when recording the new revision with a value too long error, rolling back the transaction and preventing every PostgreSQL deployment from advancing to this release; use an identifier no longer than 32 characters.

Useful? React with 👍 / 👎.