[dev-shahed]

Problem

Dokan Lite reported (getdokan/dokan#3453) that some settings strings can't be translated:

1. "Change" (Appearance → Store image field): hardcoded in WpMediaUpload. Dokan's .pot has the string, but only from its own bundles, so translating it had no effect here.
2. "Upload Image" (Vendor Onboarding): default btnText prop, not in the .pot at all.
3. Rich text editor toolbar (Bold, Italic, Link, Undo…): hardcoded title attributes.

Fix

Wrap them in __( '…', 'dokan-lite' ) from @wordpress/i18n (already an externalised peer dependency).

• WpMediaUpload.tsx: Upload Image, Add Images, Change, Select Images, Add, Remove
• rich-text-editor.tsx: all toolbar button titles + the two URL prompts
• WpMedia.ts: media frame title/button "Select"
• file-view.tsx: Remove aria-label

Literal __() calls with the dokan-lite domain are what wp i18n make-pot extracts from Dokan's compiled assets/js/plugin-ui.js, and Dokan already loads dokan-lite script translations for the dokan-plugin-ui handle.

Not changed

• Toolbar <option> labels (Paragraph, Heading 1, Sans Serif…): their text is also their value, so translating them would break the formatting handlers. Needs a value/label split.
• DataViews strings use the 'default' text domain, which Dokan doesn't load for this script. Left for a follow-up.

Verification

• npm run typecheck and npm run lint pass.
• Not yet verified: compiled output + makepot extraction in Dokan. After merge, Dokan needs its package-lock.json bumped to the new commit.

🤖 Generated with Claude Code

[dev-shahed]

Closing: this hardcodes the dokan-lite text domain, which doesn't belong in the general toolkit. Fixing on the Dokan side instead (build-time transform in dokan-lite).