[DOCS] Translations still encode the old settings.json precedence order (follow-up to #131)

[luongnv89]

Summary

PR #131 (Closes #130) corrected the settings.json precedence chain order in the English docs, but the same incorrect order still lives in the translated copies. After #131 merges, the English source and the translations will disagree on a factual point.

Correct order, per official docs and now the English files:

Managed → CLI args → Local → Project → User (lowest)

The translations still encode the old, wrong order where User sits above Project/Local.

Affected files

02-memory/README.md — five-level precedence table (rows 3/4/5)

Lang	File	Current (wrong)	Should be
vi	vi/02-memory/README.md:313-315	3=user, 4=project, 5(lowest)=local	3=local, 4=project, 5(lowest)=user
ja	ja/02-memory/README.md:305-307	3=user, 4=project, 5(lowest)=local	3=local, 4=project, 5(lowest)=user
uk	uk/02-memory/README.md:304-306	3=user, 4=project, 5(lowest)=local	3=local, 4=project, 5(lowest)=user
zh	zh/02-memory/README.md	table absent — zh is an older/shorter version that lacks the five-level settings table and the v2.1.119 /config note entirely	needs the full section ported

02-memory/README.md — v2.1.119 /config persistence note

Lang	File	Current (wrong)	Should be
ja	ja/02-memory/README.md:317	プロジェクト／ローカル／ポリシー (project/local/policy)	ポリシー／ローカル／プロジェクト (policy/local/project)
vi / uk	—	note appears absent in these files	port the corrected note if/when the section is synced

10-cli/README.md — v2.1.119 /config persistence note

Lang	File	Current (wrong)	Should be
ja	ja/10-cli/README.md:252	（project → local → policy → user）	（policy → local → project → user）
vi / uk / zh	—	/config persistence note appears absent	port the corrected note if/when 10-cli is synced

Acceptance criteria

• ja, vi, uk 02-memory/README.md precedence tables show local(3) → project(4) → user(5, lowest)
• ja /config notes in both 02-memory/README.md and 10-cli/README.md use the policy → local → project → user phrasing
• zh/02-memory/README.md settings section is brought up to date with the English source (or tracked under the broader i18n-sync effort)
• No other regressions vs. the current English source files

Context

• Source of truth: PR fix(memory): correct settings.json precedence chain order #131 / issue docs: settings.json precedence chain order is incorrect #130, verified against https://code.claude.com/docs/en/settings
• Related: [FEATURE] Improve i18n infrastructure for scalable multi-language support #63 (i18n infrastructure)
• This is the kind of follow-up the existing translation-sync workflow handles (cf. fix(i18n): re-point translations to code-review-specialist rename #128, fix(i18n): correct logo paths in translated root-level files #124) — filing it so the precedence fix doesn't get lost.