F5: `target_locales` ships empty — init plan should prompt or be explicit

[ChauCM]

Surfaced by a pilot test (Claude Code Opus 4.7 against examples/after/, 2026-05-24). Full feedback: dialect-feed.md.

Problem

The init plan template has the phrase Target locales: (none configured yet) baked in. The plan still ran end-to-end without target locales, but Phase 2.3 (translate) had nothing to do until the reporter edited dialect.yaml themselves.

Options

• (A) dialect init --with-locales es,de,ja flag
• (B) Prompt during init: "what locales do you ship in?"
• (C) Document explicitly in the plan: "Before Phase 2.3, edit dialect.yaml's target_locales — Phase 2.3 will write one file per locale you list."

Reporter votes (C) — lowest-effort and chat-first-friendly.

Acceptance

• The init plan explicitly tells the agent (or dev) that target_locales must be populated before Phase 2.3 runs.
• Either (A) or (B) is implemented for explicit control, or (C) is implemented and (A)/(B) are out-of-scope.