iOS Localize Copy

Treat every localized string as a runtime contract.

1. Establish scope and locale truth

• Classify the request as an edit, a review, or localized App Store metadata (whatsNew, fastlane release_notes.txt, or screenshot caption copy). Keep metadata out of scope unless the user requests it; never edit stale metadata, and name it in the handoff as a separate task.
• Inspect Xcode knownRegions, every relevant .xcstrings catalog, and App Store metadata locale directories or configuration, and record each locale set. Resolve mismatches from project evidence before translating; where evidence does not resolve a mismatch, ask the user to classify the locale before translating.
• Inspect repository guidance, the current diff, and existing localization validators. Preserve unrelated work.
• Audit before editing: load each catalog as JSON and report keys against locales, the state counts (translated, new, needs_review), and the exact missing-key list for each locale.

Complete when every discovered locale is classified as supported or excluded with evidence, the permitted files are explicit, and the audit table exists.

2. Build the copy inventory

• Derive the target keys from the request and current diff.
• Trace each key or source literal to its call sites. Read the surrounding UI, comments, tests, and screenshots needed to identify audience, action, feature terminology, length constraints, plural rules, and tone.
• For every target, record the catalog's declared source-language value, key, visible context, placeholders, URLs, Markdown link targets, and intentional whitespace.