initlisted

# Preparing a repository **Speak the repository's language.** The first script this skill runs — `<cue>/gate`, or `<cue>/init-check` — prints a `language` line. **Everything you say to the user goes in that language, starting with your first sentence**: the questions you ask, not only the record you write at the end. This skill body is English because it is the plugin's source, not because it is your output. Template headings, commit markers, `outcome.md` status tokens, paths and code stay exactly as written. **`AskUserQuestion` is not an exception. `question`, `header` and `description` are written in the repository's language, like everything else you say.** A menu is a thing the user reads in order to decide, and a menu they cannot read is not a menu. **What does not translate is a `label` that is a value.** A KEY, a branch name, a base ref, `self-review`, `independent-review` — those go on to be passed to a script or written into a record, and the answer comes back to you as the label string. Translate one and what it names stops existing. A label that is only prose — "leave it for now" — is written in the repository's language like the rest of the menu. **One known cost, so that it is not read as a defect when it appears.** On Windows the harness's own rendering of these four fields can corrupt non-ASCII text: a real session showed a Korean user menus with mangled syllables in them, in the words for "merge" and "complete", while every line of ordinary prose in the sa