docs(i18n): add fr/de/zh-TW/hi/tr/it/pl/ar README translations

[Hmbown]

Summary

Add README translations for the languages the TUI already ships (and a few we were missing):

• README.fr.md (Français)
• README.de.md (Deutsch)
• README.zh-TW.md (繁體中文)
• README.hi.md (हिन्दी)
• README.tr.md (Türkçe)
• README.it.md (Italiano)
• README.pl.md (Polski)
• README.ar.md (العربية; Markdown only, no HTML dir attributes)
• README.ca.md (Català; remaining shipped TUI pack)

The English README language line and every existing translation now link the old set first, then the new ones. Source stamps are regenerated to sha256:4fc19c5f9596. Both lists in scripts/check-readme-translations.py include the new files, and docs/LOCALIZATION.md / docs/LOCALIZATION.id.md / the public-surface Shift+Tab contract list were updated to match.

Closes #5451

Verification

python3 scripts/check-readme-translations.py
README translation check OK — 18 translations in sync with README.md (sha256:4fc19c5f9596)

Also ran bash scripts/check-readme-locales.sh — PASS (18 linked locale READMEs, no orphans).

Did not run cargo (docs-only change; lane instruction).

Not verified

Native-speaker review of each new language. The new rows in docs/LOCALIZATION.md are marked awaiting that review.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude finished @Hmbown's task in 3m 26s —— View job

---

Review complete ✅

• Gather context (PR diff, changed files)
• Review new README translations (fr/de/zh-TW/hi/tr/it/pl/ar/ca)
• Review supporting script/docs changes (scripts/check-readme-translations.py, docs/LOCALIZATION*.md, public-surface contract test)
• Verify RTL/Arabic handling and locale consistency
• Post final review

Summary

Docs-only PR, cleanly scoped. This is against codewhale-config/codewhale-protocol/workspace code, so priorities 1–2 (correctness bugs, provider/route safety) from the review checklist don't apply here — no Rust or routing logic touched.

Checks performed (via file inspection, since script execution required approval I didn't have in this run):

• All 9 new files (README.fr.md, .de.md, .zh-TW.md, .hi.md, .tr.md, .it.md, .pl.md, .ar.md, .ca.md) carry the matching sha256:4fc19c5f9596 source stamp.
• ## section counts match README.md (7) in every new and existing translation.
• Fenced bash command blocks (npm install -g codewhale, the codewhale auth set … usage block) are byte-identical/untranslated across all 18 translations, including the literal DeepSeek-V4-Pro-0813 / deepseek-v4-pro provider strings — good, no drift in code samples.
• Language-switcher line in each of the 19 README files (README.md + 18 translations) correctly self-excludes and links the other 18 — verified this for README.ar.md and README.zh-TW.md in full, spot-checked link counts elsewhere.
• README.ar.md is Markdown-only with no HTML dir="rtl" attributes, as called out in the PR description and docs/LOCALIZATION.md:140; matches the existing pattern for the other translations (no other README uses dir either).
• docs/LOCALIZATION.md / docs/LOCALIZATION.id.md new rows are correctly placed only under the "README locales" table, not the TUI-pack or website tables — important since crates/tui/locales/ has no tr, it, pl, or ar packs. The "shipped" status here is per the doc's own scope note (shipped-as-standalone-README, distinct from TUI pack parity), so this isn't a contradiction, just worth knowing these four are README-only additions, not TUI locale packs.
• scripts/check-readme-translations.py: both TRANSLATIONS and LANGUAGE_LINKS lists updated identically with the 9 new files — no lockstep mismatch risk between the two lists.
• web/lib/public-surface-contract.test.ts: the new Shift+Tab assertions were added for all 9 new files, keeping the Shift+Tab-mentions-in-every-README contract intact.

Not independently re-verified: I was not able to execute python3 scripts/check-readme-translations.py or bash scripts/check-readme-locales.sh in this sandbox (command execution required approval unavailable here), so I relied on manual file/regex inspection instead of the PR's own stated verification output. Everything I could check by hand matches what the PR description claims.

No correctness, safety, or reuse issues found. Nice attention to detail keeping the two check-readme-translations.py lists and the contract test in sync — that's the kind of spot where drift usually creeps in.