statuslisted

# Checking the current stage **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. Run `<cue>/status [KEY]`. **When it prints the `━━━` block, reproduce that block in your reply, inside a fenced code block, unchanged and complete.** That instruction is the whole skill, and it is the one that gets skipped. The script's output goes to a *tool result*, which the interface collapses to the first few lines — so a user who ran `/cue-dev:status` and got a two-sentence summary from you never saw the track, the task counts, or the isolation warning. They asked for the report, not for your reading of it. The block does not translate. Every line in it is a label and a value — stage names, file paths, SHAs, commands — so paste it as it stands even when the record language is not English. **Only the `━━━` block is relayed.** When the script cannot answer it hands the question to `<cue>/gate` instead, and gate prints no block — it prints `blocked` and `now` lines, which are written to be *acted on*, not pasted. Say what they mean, in the user's language, i